How it works
the architecture in 30 seconds

WordPress for Cowork is one plugin on your WordPress site, plus a connection you add in Claude. Nothing runs on our servers in the request path — your content stays on your host.

The two halves

• The plugin (wordpress-for-cowork.zip) installs on your WordPress site like any other plugin. On activation it deploys a small must-use plugin that exposes an MCP endpoint at your-domain.com/wp-json/coworkmcp/v1/mcp, and it turns your site into the place where Claude signs in and gets approved.
• The connector in Claude. You add that address under Customize → Connectors, sign in to your own site, and press Allow. From then on Claude knows more than 100 tools for your site — pages, posts, media, comments, menus, themes, WooCommerce, users, SEO, backups, diagnostics.

The flow

1. You ask Claude for something in plain English.
2. Claude picks the right tools and calls your site’s endpoint over HTTPS, from Anthropic’s servers, using the access your site issued when you approved it.
3. Your site checks that access on every request, does the work with WordPress’s own functions, and answers.
4. Claude shows you the result. For anything destructive it asks first and offers a backup.

What that means in practice

• Your WordPress password is only ever typed into your own site. Claude never sees it, and neither do we.
• The connection address never changes, so updating the plugin never breaks the connection.
• Each website you connect is its own connector, and every tool is labelled with the site it belongs to.
• If it will not connect, Cowork → Run the check in wp-admin tests every step from your site’s side.