MCPWP supports Claude's connector sign-in: add your site as a connector, sign in with OAuth, and Claude can operate your WordPress — content, pages, Elementor, SEO, media — with every change checked and big ones waiting for your approval. Works in Claude, Claude Cowork and Claude Code.
Upload and activate MCPWP on the WordPress site you want Claude to operate.
In Claude: Settings → Connectors → Add custom connector → paste your site's MCPWP URL.
Claude opens your site's sign-in page. Log in as your WordPress user and approve the access scope. No keys to copy.
“Look at my site and tell me what you can do.” Claude inspects before it ever edits.
A — Connector sign-in (recommended). In Claude or Claude Cowork, add a custom connector with your site URL. Claude handles the rest with OAuth — sign in, approve, done. Revoke access anytime from your WordPress admin.
Connector URL: https://your-site.com/wp-json/mcpwp/v1/mcp
B — API key (Claude Code, developers). Create a role-scoped key in WP Admin → MCPWP, then add:
"mcpwp": {
"url": "https://your-site.com/wp-json/mcpwp/v1/mcp",
"headers": { "X-API-Key": "mcpwp_your_scoped_key" }
}Yes — Cowork uses remote connectors, which is exactly what MCPWP provides. Add the connector once and Cowork sessions can operate your site under the same approval rules.
Yes. MCPWP validates every Elementor change before it saves — wrong widget settings get flagged or fixed instead of silently breaking your layout.
Yes when the access scope allows it. Start with drafts; destructive or bulk operations create an approval request you confirm first.
Revoke the connector's token or the API key in WP Admin → MCPWP. Access ends immediately; the activity log keeps the full history.