You can now use an MCP Server to connect Unbounce to Claude Code, Claude Desktop, or ChatGPT Desktop, and build, publish, and manage landing pages right from the conversation.
You describe what you want in plain language, "build a webinar registration page," "add a second variant with a shorter headline," "split traffic 80/20", and the assistant builds, sets up A/B tests, and publishes real pages in your account. You get the speed of AI for the repetitive setup, while you stay firmly in control of what actually goes live.
Getting Connected
Your AI assistant can't touch your Unbounce account until you connect it and sign in. Connecting is a one-time setup per assistant, and you can do it in whichever assistant you already use. There's nothing to prepare ahead of time: any Unbounce account works, and a sign-in prompt appears during setup. Pick your assistant below.
▶Claude Desktop
- Open Customize → Plugins.
- Click Add, choose to Add marketplace.
- Choose Add from a repository.
- In the URL (Select a repository) field enter: "unbounce/agent-plugins". Note: as you type, matching repositories will appear in a drop down.
- Select unbounce/agent-plugins from the drop down then click Sync. Note: ensure Sync automatically is toggled on - this keeps you up to date.
- Plugins → Personal → agent-plugins should now be showing an Unbounce mcp tile.
- Click on the tile to go to Unbounce mcp and then click Install.
- Click Manage (was Install prior).
- Click the Connectors tab (next to Skills).
- Click the unbounce connector's Install.
- The Add custom connector dialog shows. Don't change anything. Click Add.
- Click the unbounce connector's Connect (was Install prior).
- You will be taken to the Unbounce login page in your browser. Log in with your Unbounce account credentials and authorize access. You will then be returned to Claude Desktop. Note: if you are already logged into your Unbounce account and have authorized access in the past, this step is skipped (auto authorize).
You are now set up. If you hit any issues, see Troubleshooting below.
▶Claude (web, claude.ai)
The flow is identical to Claude Desktop: claude.ai has the same Plugins area with the same Add marketplace → Add from a repository steps, so follow the Claude Desktop instructions there. And because plugins are tied to your Claude account, installing in claude.ai also installs it in Claude Desktop (and vice versa) - do it once on either surface.
▶Claude Code (CLI)
-
In a terminal, add the marketplace:
claude plugin marketplace add unbounce/agent-plugins
-
Install the plugin:
claude plugin install unbounce-mcp@unbounce
- Check the install:
claude plugin listshould show unbounce-mcp. - Start Claude Code:
claude - Run the
/mcpslash command. - Under Built-in MCPs choose plugin:unbounce-mcp:unbounce.
- Choose Authenticate.
- You will be taken to the Unbounce login page in your browser. Log in with your Unbounce account credentials and authorize access. You will then be returned to Claude Code. Note: if you are already logged into your Unbounce account and have authorized access in the past, this step is skipped (auto authorize).
- Verify:
/mcpshows plugin:unbounce-mcp:unbounce as connected, and typing/unbounce-mcp:lists the Unbounce skills.
You are now set up. If you hit any issues, see Troubleshooting below.
▶ChatGPT Desktop
- Select Plugins (left panel).
- Click Add (top right hand corner).
- Select Add a marketplace from the dropdown and a dialog pops up.
- Type "unbounce/agent-plugins" in the Source text box.
- Click Add marketplace. You will be returned to Plugins.
- Under the Personal tab there is now an Unbounce section. Click on the Unbounce plugin.
- Click Install.
- You will be taken to the Unbounce login page in your browser. Log in with your Unbounce account credentials and authorize access. You will then be returned to ChatGPT Desktop. Note: if you are already logged into your Unbounce account and have authorized access in the past, this step is skipped (auto authorize).
- Start a new chat and click the + to reveal a dropdown.
- Scroll to find Unbounce under Plugins. This adds it to your chat.
You are now ready to go! If you hit any issues, see Troubleshooting below.
▶Codex CLI
-
In a terminal, add the marketplace:
codex plugin marketplace add unbounce/agent-plugins
-
Install the plugin:
codex plugin add unbounce-mcp@unbounce
- Start Codex:
codex - Sign in to Unbounce when prompted (the first time an Unbounce tool runs). You will be taken to the Unbounce login page in your browser. Log in with your Unbounce account credentials and authorize access. Note: if you are already logged into your Unbounce account and have authorized access in the past, this step is skipped (auto authorize).
- Verify: run the
/mcpslash command - unbounce should be listed in its MCP servers.
You are now ready to go! If you hit any issues, see Troubleshooting below.
▶ChatGPT (web)
Not supported yet. The ChatGPT web app can only install plugins from OpenAI's official Plugin Directory, and it has no option to add a marketplace like the desktop app does. Unbounce is applying for a Plugin Directory listing; once that's live, web install will work directly from the directory. In the meantime, install via ChatGPT Desktop or the Codex CLI.
Whichever assistant you use, two things are true once you've signed in:
- The assistant acts as you. It works through your own Unbounce login and respects your existing role and permissions. It can't see or do anything you couldn't do yourself.
- You choose where it builds. Your account can contain several clients. Tell the assistant which one to work in, or ask it to list your accounts and clients so you can pick.
▶Troubleshooting
A quick way to check everything is working, on any platform: ask the assistant "what version of Unbounce MCP am I using and what tools do I have access to?" It should report a version and list the Unbounce tools.
Claude says the connector "needs authorization" even though it's connected. After a successful install, Claude sometimes claims the Unbounce connector isn't connected yet and asks you to authorize it, even when your Connectors settings show it as Connected. This is Claude misreading the connector's state in that chat, not a real problem: it hasn't loaded the tools yet, and once nudged it connects fine. Don't re-authenticate - just tell it it's wrong and to try anyway:
The Unbounce connector shows as Connected in my connector settings. Load its tools and try again.
It should load the tools and carry on. If it still refuses, start a new chat and ask your question again there.
Sign-in fails or loops. Make sure you approved the Unbounce sign-in in the browser with the account you meant to use, then disconnect and reconnect the unbounce connector to retry.
The connector button is greyed out and won't connect. If your Claude account is administered by your company, user-added connectors and plugins may be blocked by org policy. A Claude org admin must approve the Unbounce connector; there's no user-side workaround. Personal (non-managed) accounts are unaffected.
unbounce-mcp@unbounce not found (Claude Code). Re-run claude plugin marketplace add unbounce/agent-plugins and check that https://github.com/unbounce/agent-plugins is reachable in your browser.
The tools work but the skills don't appear. Re-sync the marketplace; in Claude Code, run /reload-plugins.
Your first page
Always specify the client you're working in. It's the scope for pages, assets, and page groups, and getting it wrong means creating or editing a page in the wrong place. Describe the page you want: the purpose of your landing page, audience, and call to action. The assistant designs the page, creates it in the client you chose, and leaves it unpublished so you can review it before anything goes live.
What You Can Do
You direct the work in plain language; the assistant handles the build. Ask for changes the same way you asked for the page "make the CTA button blue," "shorten the form," "add a countdown timer."
Build and edit pages
- From a description: ask for a landing page and the assistant generates the layout, copy, and styling to match your brief. No coding required.
- Editing: ask for any change to an existing MCP server page - a headline, a section, a colour - and the assistant makes those changes/edits for you.
- Images and assets: the assistant can upload images to your account and use assets already there.
Create variants and run A/B tests
- Add variants: create a second or third variant of any page to test different headlines, layouts, or offers. This can be done by either creating a fresh copy or copying from an existing variant as a starting point.
- Control the traffic split: choose a fixed weighted split (50/50, 80/20), turn on Smart Traffic to send each visitor to the variant most likely to convert them, or route all traffic to a single variant.
- Manage the test: rename variants, promote one to champion, or pull a variant out of the test.
- Edit every variant at once: apply the same change across all of a page's variants in one request, rather than repeating yourself.
Publish and set up the URL
- Publishing: nothing is live until you ask for it. When you're ready, tell the assistant to publish your page.
- Page URL and domain: set the page's slug, or move it to another of the domains set up for your client.
- SEO and social: set the page title, meta description, favicon, and the Open Graph tags that control how the page looks when shared.
- Redirects and page groups: point an old URL at a new page, and organize pages into groups.
Track results
- Conversion goals: define what counts as a conversion on the page.
- Page statistics: ask for a page's visitor and conversion numbers.
How It Works Day to Day
A few behaviours are worth understanding, because they shape how the assistant works with you.
- Changes stage as drafts. Content, variant, and traffic changes don't affect your live page until it's published. This is deliberate, allowing you to edit safely, but it does mean the publish step is yours to ask for. The one exception is changing a page's URL, which takes effect immediately.
- Pages built with the assistant are managed with the assistant. A page or variant created through the MCP can't be opened and edited in the Unbounce builder. All further changes go through the assistant. You ask for them, or you supply updated content. Plan for this before you start: if a page needs hands-on visual editing later, build it in the Unbounce builder instead.
- Classic builder pages work the other way round. Pages built by hand in the classic Unbounce editor can't be edited or exported through the assistant. They can be copied into MCP managed pages for editing with your AI assistant.
- Deleting is reversible. Deleting a page moves it to trash, and you can restore it from the Unbounce app. It isn't a permanent destruction.
- The assistant doesn't see your page visually. It works from the page's content, not a rendered screenshot. To see the page, ask your AI assistant to create a preview or use the Unbounce preview.
A few things are still done in the Unbounce app rather than through the assistant: building popups and sticky bars, taking payments (use an external payment processor linked from your page), domain management, and permanently deleting an asset.
PII & Compliance: Using Unbounce MCP Server
▶Read the compliance details
This guide covers your compliance responsibilities when connecting Claude or ChatGPT to Unbounce via the MCP server.
Overview
When you connect Claude or ChatGPT to Unbounce via MCP, your AI assistant will access your landing pages, lead data, and account information. This section explains what data is accessed, what you're responsible for, and how to ensure compliance with privacy laws like GDPR and CCPA.
Key point: The MCP Server does NOT provide access to individual lead data or PII. Lead data has been removed from MCP to ensure compliance with CCPA, GDPR, and other privacy regulations. You can use MCP safely with visitors from any jurisdiction.
What Data Will Claude or ChatGPT Access?
Landing Page Data
- Page HTML, CSS, and copy
- Page design elements
- Images and media
- A/B test variants
Account & Performance Data
- Landing page names and metadata
- A/B test results (conversion rates, lead volume, traffic source)
- Page groups and organizational structure
- Account information (limited to what the authenticated user can access)
What MCP Does NOT Access
- Individual lead data (names, emails, phone numbers, form submissions)
- Visitor personally identifiable information (PII)
- IP addresses or visitor identifiers
Your Compliance Responsibilities
Because MCP does not process lead data, you have no additional compliance burden when using MCP with visitors from any jurisdiction, including:
- California (CCPA)
- EU/UK (GDPR)
- Other regulated jurisdictions
You can use MCP the same way you use the rest of Unbounce, with no new privacy policy updates or consent mechanisms required specifically for MCP.
Frequently Asked Questions
▶Can I use MCP if I have California visitors?
Yes. MCP does not access individual lead data, so CCPA compliance requirements do not apply to MCP usage.
▶Can I use MCP if I have EU/UK visitors?
Yes. MCP does not access individual lead data, so GDPR compliance requirements do not apply to MCP usage.
▶What lead data can Claude or ChatGPT access?
None. MCP provides aggregate lead volume reporting only (the number of leads collected). Individual lead details are not accessible through MCP.
▶ Do I need to update my privacy policy for MCP?
No. Because MCP does not access lead data, you do not need to add any disclosures about MCP to your privacy policy. MCP operates on the same compliance basis as the core Unbounce platform.
▶Is Unbounce responsible for notifying my customers or ensuring compliance?
No. You are the data controller. You are responsible for:
- Notifying your own customers
- Obtaining consent
- Complying with privacy laws
- Managing data subject requests
Unbounce provides the tool; you are responsible for using it lawfully.
▶ What happens if I want to access lead data in the future?
A future mechanism for lead data access may be available post-launch. It will be your responsibility to comply and implement relevant controls.
▶Can I use the MCP server if I'm not sure about my compliance obligations?
We recommend consulting with your legal or privacy team before connecting the MCP server, especially if you:
- Collect data from EU/UK visitors
- Collect data from California or other regulated US states
- Are in a regulated industry (healthcare, finance, etc.)
- Are unsure about your privacy laws
Better to clarify now than face regulatory action later.
▶How does responsibility work when you connect an AI assistant?
Think of it like three parties, each covering their own piece:
You (the account holder)
You control how you collect, use, and protect your customers' data — so things like your privacy policy, getting proper consent, and honoring deletion requests are yours to manage, just like they are today without AI in the mix.
Your AI provider (Anthropic, OpenAI, etc.)
They're responsible for how they process and protect data once it reaches their systems — that's covered under their Data Processing Agreement.
Unbounce
We're responsible for keeping our platform and connections secure, per our Terms of Service.
In short: connecting an AI assistant doesn't change who owns compliance — it's the same as any other tool you plug into your stack. You're still steering; we and your AI provider are responsible for our own parts of the pipeline.
Checklist: Before You Connect the MCP Server
I understand that MCP does not access individual lead data
I understand that lead volume reporting is aggregate only (no PII)
I understand that I can use MCP with visitors from any jurisdiction
I understand that I am responsible for compliance; Unbounce is not
Need Help?
- Unbounce Support: Contact support for questions about how to connect the MCP server
Additional Resources