The Model Context Protocol (MCP) lets Claude Desktop, Claude Code, VS Code, Cursor, and any other MCP-compatible AI client connect directly to your WordPress site and use your AI assistants’ tools. Instead of a flat list of 100+ tools, each assistant gets its own scoped MCP server — so Claude only sees the tools relevant to what it is doing.
What MCP Unlocks
- Use your assistants from your development environment — query, create, and edit WordPress content without leaving Claude Code, VS Code, or Cursor.
- Scoped tool sets — each assistant exposes only its declared tools, keeping context windows focused. The Content Writer exposes writing tools; the SEO Optimizer exposes SEO tools.
- Two transport modes — STDIO for local development (zero config), HTTP for remote servers and shared team access.
- Marketplace agents included — every agent you purchase automatically gets its own MCP server and credentials emailed on purchase.
Requirements
- Agent Builder 2.3.1 or later
- Agentic MCP companion plugin (free — install from the marketplace)
- WordPress 6.4+ with Application Passwords enabled
- An MCP-compatible client: Claude Desktop, Claude Code, VS Code (with MCP extension), or Cursor
Step 1 — Install the Agentic MCP Companion Plugin
The Agentic MCP companion plugin vendors the wordpress/mcp-adapter package. Agent Builder detects it automatically and creates per-agent MCP servers the moment it is activated.
- Download Agentic MCP from the marketplace.
- Go to Plugins → Add New → Upload Plugin and upload the zip.
- Activate it. Return to Agentic → Settings → MCP to confirm the green MCP Active status badge.
Step 2 — Review the MCP Tab
Go to Agentic → Settings → MCP. A connection table lists every installed assistant with its HTTP endpoint, STDIO command, and server ID.
Step 3 — Connect Your MCP Client
Option A — STDIO (Local / Recommended for Development)
STDIO runs WP-CLI as a local subprocess. No network authentication is needed — permissions come from the --user flag.
Run this command to get a ready-to-paste JSON block for any assistant:
wp agent mcp-connect content-writerExample output:
{
"mcpServers": {
"content-writer": {
"command": "wp",
"args": [
"--path=/var/www/your-site/public",
"mcp-adapter",
"serve",
"--server=agentic-content-writer",
"--user=admin"
]
}
}
}Claude Desktop (macOS): paste into ~/Library/Application Support/Claude/claude_desktop_config.json.
Claude Desktop (Windows): paste into %APPDATA%\Claude\claude_desktop_config.json.
VS Code / Cursor: add to your MCP servers config in settings.
Option B — HTTP (Remote / Team Access)
HTTP transport works over the WordPress REST API and requires an Application Password.
- Go to Users → Profile → Application Passwords.
- Enter a name (e.g. Claude Desktop) and click Add New Application Password.
- Copy the generated password — it is shown only once.
- Run:
wp agent mcp-connect content-writer --transport=http
Example output:
{
"mcpServers": {
"content-writer": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
"env": {
"WP_API_URL": "https://your-site.com/wp-json/agentic/content-writer/mcp",
"WP_API_USERNAME": "your-username",
"WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
}
}
}
}Replace the three env values with your site URL, username, and the Application Password you just generated. The endpoint URL for each assistant is shown in the MCP tab.
Purchased Marketplace Agents
When you purchase a premium agent, you receive a second email alongside your download link: MCP Connection Credentials. It contains a dedicated WordPress username, an Application Password pre-scoped to that agent’s MCP server, and the ready-to-paste HTTP JSON config.
The Application Password is shown only once in this email. If you lose it, generate a new one from Users → Profile → Application Passwords on your site.
Security Model
| Transport | Authentication | Write tool access |
|---|---|---|
| STDIO | WP-CLI --user flag | Depends on user role (admin = full access) |
| HTTP (admin account) | Application Password | Yes, if user has manage_options |
| HTTP (purchased agent user) | Application Password | Read tools only (agentic_mcp_client role) |
The agentic_mcp_client role is automatically assigned to accounts created on agent purchase. It has read-level capabilities only. To enable write tools, promote the user to Editor or Administrator on your site.
MCP Server IDs
Every installed assistant gets a server in the format agentic-{slug}:
| Assistant | Server ID | REST endpoint path |
|---|---|---|
| Content Writer | agentic-content-writer | /wp-json/agentic/content-writer/mcp |
| SEO Optimizer | agentic-seo-optimizer | /wp-json/agentic/seo-optimizer/mcp |
| Security Monitor | agentic-security-monitor | /wp-json/agentic/security-monitor/mcp |
| Backup Manager | agentic-backup-manager | /wp-json/agentic/backup-manager/mcp |
| Content Refresher | agentic-content-refresher | /wp-json/agentic/content-refresher/mcp |
| Onboarding Assistant | agentic-onboarding-assistant | /wp-json/agentic/onboarding-assistant/mcp |
Custom or marketplace agents follow the same pattern. Check Agentic → Settings → MCP for your full list.
Troubleshooting
MCP tab shows “MCP Adapter Not Installed”
The Agentic MCP companion plugin is not active. Download and upload it via Plugins → Add New → Upload Plugin, then activate it.
STDIO: “command not found: wp”
WP-CLI is not on your PATH. Use the full path to the WP-CLI binary in args[0], e.g. /usr/local/bin/wp.
HTTP: 401 Unauthorized
Verify the Application Password is correct (no extra spaces). Ensure Application Passwords is enabled and the username matches exactly.
HTTP: 403 on write tools
The authenticating user has the agentic_mcp_client role which only allows read tools. Promote the user to Editor or Administrator for full write access, or use your admin account’s Application Password instead.
Assistant not listed in my MCP client
Each assistant must be added individually. Run wp agent mcp-connect {slug} for each one and add each resulting JSON block under a distinct key in your mcpServers config.