Claude Desktop reaches the site through a local bridge, @automattic/mcp-wordpress-remote, that runs on your computer, holds the site address and the Application Password, and talks to the plugin’s MCP endpoint for you. The plugin prints the block you need, with one address to correct in 2.10.3; you paste it into Claude Desktop’s configuration file and restart the app.
Before you start
- An Application Password for the WordPress user the assistant will act as.
- The Assistant connection module turned on in WP Visibility → Settings → Modules, with Autopilot on and Assistant changes set to Hold for my review if you want SEO writes such as titles, descriptions, redirects and settings to wait for you. The draft, import and IndexNow tools are not held.
- Node.js 22 or newer on the computer running Claude Desktop, which the bridge’s README lists as a requirement (checked September 27, 2026). The bridge starts with
npx, which comes with Node.
1. Print the block
On the site, from WP-CLI, with the assistant’s username:
wp visibility mcp-config --user=seo-agentIt prints a mcpServers entry with your site and username filled in. In version 2.10.3 the printed WP_API_URL is the site’s home address, such as https://your-site.com/. Change it to the endpoint address, https://your-site.com/wp-json/wp-visibility/mcp, which the command also prints on its last line. The finished entry looks like this:
{
"mcpServers": {
"your-site-com": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
"env": {
"WP_API_URL": "https://your-site.com/wp-json/wp-visibility/mcp",
"WP_API_USERNAME": "seo-agent",
"WP_API_PASSWORD": "<application password>"
}
}
}
}WP_API_URL must be the full endpoint address the command prints on its last line, which usually ends in /wp-json/wp-visibility/mcp. Given only a domain such as https://your-site.com/, the bridge assumes an older WordPress MCP plugin and looks for a route this plugin does not provide. The bridge’s README documents that fallback.
If you do not have WP-CLI, write the block by hand from the example: the endpoint address, the username, and the password from the previous doc.
2. Add it to Claude Desktop
Open Settings from the Claude app menu (not the settings inside the chat window), then Developer → Edit Config. That opens claude_desktop_config.json (on macOS under ~/Library/Application Support/Claude/, on Windows under %APPDATA%\Claude\), as the MCP guide to Claude Desktop describes (checked September 27, 2026). Paste the block. If the file already has a mcpServers object, add your site as another entry inside it rather than a second object. Replace <application password> with the real one, save, and quit and reopen Claude Desktop.
Keep this file private. It now contains a login to your site.
3. Check it
Start a new conversation. In the message box, click + (Add files, connectors, and more), point to Connectors and choose Manage connectors, then select your site’s entry (named like your-site-com) to see its tools, as the same MCP guide shows. Ask for a read first. The plugin’s tools find posts by ID, so use the ID of a real post:
What are the SEO title and meta description of post 123?
Then ask for one change:
Propose a better meta description for that post.
With Hold for my review selected, the tool returns a proposal ID and the post itself is unchanged. Open WP Visibility → Review queue and the proposal is there with its diff. If it is not, this doc finds out why.
Several sites in one Claude
Run mcp-config on each site and put each block in the same mcpServers object, with its own name. Each site appears as its own server with its own tools, so name the site in your request.
Why not the custom connector form
Claude’s Add custom connector form takes a server URL and, optionally, OAuth client details. The plugin’s endpoint authenticates with a WordPress Application Password, which that form has no field for, so the bridge is the supported route for Claude Desktop today. Checked September 27, 2026 against Anthropic’s connector documentation, updated August 11, 2026.