MCP Bridge

This page shows you how to connect your AI client to your site, then ask it to build pages or change them.

With the MCP Bridge, the AI app you already use, such as claude.ai, ChatGPT, Claude Code or Cursor, works on your site from its own window. It creates pages, builds a whole site, writes the styles, adds images to the media library and changes any page you name. It builds with the same blocks and styles as the chat in the editor.

New to MCP?

It's the open standard AI apps use to connect to other tools: the Model Context Protocol. You connect your site once, then you talk to your AI as usual.

Before you start

• WordPress 6.9 or later, and an active Unblock license.
• An Administrator account. Developers can open MCP to other roles with the unblock/ai/mcp/can_use filter.
• The MCP Adapter, the official WordPress plugin for MCP. The MCP tab installs it in one click.

Connect your AI client

You do this once per client.

1. Open the MCP tab

In the editor, open the Unblock AI sidebar and pick the MCP tab.

If the site doesn't have the MCP Adapter yet, the tab shows one step: click Install MCP Adapter. If your account can't install plugins, the tab links to the plugin's page instead: ask an administrator to install it.

2. Pick your client

Open the Client list and pick yours. Type a few letters to find it. For a client the list doesn't name, pick Other client.

The tab also picks how the client connects. Keep its choice: with OAuth, there's nothing to copy but your site's address.

3. Add your site to the client

Click the button under Connection, then follow the line under it:

Client	What you do
claude.ai, Claude Desktop	Click Add to Claude, or paste the URL in Customize > Connectors > Add custom connector
ChatGPT	Paste the URL in Plugins > + > Add custom MCP server
Grok	Paste the URL in Connectors > New Connector > Custom
Claude Code	Run the copied command in a terminal, then type /mcp in Claude Code to sign in
Cursor	Click Add to Cursor
Other clients	Paste the copied configuration in the file the line names

A Claude connector belongs to your Claude account: add it once on claude.ai, and it works in Claude Desktop and the mobile apps too.

Common mistake

Replacing your client's configuration file with the copied one. If the file already lists servers, add the new entry next to them, inside the same mcpServers (or servers) object.

4. Approve it on your site

The first time the client signs in, your site opens a page that names the client and the account it will act as. Keep Full access so it can build, or pick Read only for a client you only ask questions. Then click Approve.

The note above the buttons tells you how far you can trust the client. When it says the client's name isn't verified, or that the client runs on your computer, approve it only if you just added it yourself.

To check the connection, ask your client: "What pages does my site have?"

Other ways to connect

OAuth needs HTTPS and pretty permalinks. claude.ai, ChatGPT and Grok also need a site they can reach from the internet. When OAuth can't work, the tab picks another way:

• WP-CLI, on a site on your computer: the client starts WP-CLI, signed in as your user. There's nothing to approve.
• Password, otherwise: click Generate password. WordPress creates an application password, and the tab puts it in the configuration you copy. It shows only once, and Unblock never stores it. You find it, and can revoke it, in Users > Profile > Application Passwords.

If the connection fails

When something blocks a connection, the tab shows a warning. Fix it and reload the editor: the tab checks again. The usual ones:

• No HTTPS. OAuth and application passwords need it, unless WP_ENVIRONMENT_TYPE is set to local in wp-config.php.
• Plain permalinks. Pick any other structure in Settings > Permalinks.
• A site on your computer. claude.ai, ChatGPT and Grok connect from their own servers and can't reach it. Use a desktop or terminal client with WP-CLI.
• The REST API is closed to visitors. A security plugin may block it: allow the unblock/v1/oauth and mcp/unblock routes.
• The server drops the Authorization header. On Apache, add this line to your .htaccess file: SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1.
• The MCP Adapter is older than 0.7.0. Update it.

Build with your client

Once connected, ask your client in plain words, as you would ask a developer who knows the site. It reads the site first, then works.

Create a page

Build our About page in our site styles: our story, the four people of the team with their photos from the media library, and a contact button. Keep it as a draft.

The client creates the page as a draft unless you ask it to publish, and builds it with Unblock blocks and styles. Open it from Pages to review it, then publish it yourself.

What it builds is made of real blocks. Keep editing the page in the editor, by hand or with the chat.

Build a whole site

For a whole site, give your client a method with the agent skills. It plans the site with you, sets the design system, builds each page, then audits the result. Start with Plan your project.

Change a page

On the Home page, replace the three feature cards with a four-step timeline. Keep the hero and the colors as they are.

The client changes the page you name. On a published page, it asks you first.

Watch out

• A published page or a template changes for your visitors at once, so the client asks you first: without your agreement, the change is refused. For a bigger change, it offers a draft copy that you preview, then puts it live when you say so, or a session in your editor (see below).
• The styles are the site's. What the client writes in them applies at once to every page using them. It tells you before changing styles your live page uses. On a draft copy, they wait with the copy until you apply it.
• The styles have no WordPress revision. WordPress keeps a revision of the page, not of its CSS. The History records both and undoes them.
• A page another user has open in the editor is refused, since their next save would undo the change.
• If you have the page open in the editor, a notice tells you an AI tool changed it. Click Reload before you go on: saving would overwrite the client's changes.

Edit a page live in your editor

For detailed work on one page, let the client work in your open editor tab instead. You watch each change land, and nothing is saved until you click Save.

1. Open the page in the editor, or a template in the Site Editor.
2. In the MCP tab, open Work on this page and click Start a session.
3. Click Copy the sentence, paste it in your client, and add your request.

Use my Unblock editor session 3f2a…c91e. Call unblock-get-instructions first.

While the session runs, a green dot shows on the Unblock AI button. Click Stop when you're done.

Common mistake

Reloading the editor during a session. The session ends with the tab: start a new one and give the new sentence to your client.

Manage your clients

Connected clients, at the bottom of the MCP tab, lists the clients you approved, with their access and when they were last used. Click the cross next to one to disconnect it. To change a client's access, disconnect it and connect it again.

A client stays connected as long as you use it at least once every 30 days. Changing your WordPress password disconnects all of them.

To turn MCP off for the whole site, open the Unblock modal from the editor toolbar, go to the Settings panel, Editor tab, and uncheck MCP sessions under AI. Despite its name, it stops every client, not only sessions.

Build from a Figma design

Your client can use several MCP servers at once. Add the Figma MCP server next to your site, and the unblock-from-figma agent skill rebuilds a Figma design as Unblock sections, its variables as design tokens.

Figma limits its server by plan: a Starter plan, or a View or Collab seat, gets 6 calls a month. That's enough to try it, not to build a site.

Next steps

• Agent skills: plan, build and audit a whole site with your client
• Plan your project: the brief before the first page
• MCP Tools: every tool, its rights, the configurations and how the bridge works, for developers