Connecting a client
Your AI client connects in to your site over MCP. The plugin never calls out to any AI provider, so there is no model API key to add and nothing extra to pay for. There are two ways to connect.
The two ways to connect
Section titled “The two ways to connect”Approve the agent once in the browser. Paste your site’s MCP endpoint into your client, approve the connection, and the agent acts as your own account. There is no secret to store.
Point a dedicated low-privilege user at the endpoint. Create the agent user the Connection tab offers, generate an Application Password for it, and connect with that. A guided screen builds the client config and checks the endpoint for you.
Clients that connect today
Section titled “Clients that connect today”Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, and Gemini CLI all work
today, some directly and some through the open-source mcp-remote bridge.
- Desktop AI apps: Claude Desktop.
- AI code editors and IDEs: Claude Code, Cursor, VS Code, and Windsurf.
- Command line: Gemini CLI.
- AI agent frameworks: any MCP-compatible framework can call your enabled abilities as tools.
The bridge, for clients that cannot connect directly
Section titled “The bridge, for clients that cannot connect directly”Clients that cannot open a remote MCP connection on their own use the
open-source mcp-remote or @automattic/mcp-wordpress-remote bridge. It runs on
your own machine and talks only to your site and your local AI client. Neither
bridge is bundled with the plugin or run by it: you install and run it yourself.
Not supported yet known limitation
Section titled “Not supported yet ”The hosted ChatGPT app and the Gemini app are not supported yet. They expect a streamable HTTP or SSE remote connector that the underlying MCP Adapter does not serve natively yet. The clients listed above all work today.
Next steps
Section titled “Next steps”- Troubleshooting: OAuth discovery, Windows clients, local sites.
- Governance concepts: what the connected agent can and cannot do.