Docs · Connecting Claude
Claude surface map
Every AgenticWP site exposes a single MCP endpoint — but the surface you connect from changes what Claude can actually do. Here's the difference between Chat, Code, and Cowork at a glance.
Chat
claude.ai in your browser
Best for editors and operators who want to talk to their site in plain English. Reads + writes content via MCP; cannot run code on your machine.
Code
Claude in your terminal
Best for developers. Adds WP-CLI, file-system access, and theme/plugin builds on top of MCP. The fullest surface.
Cowork
Claude in the Mac/Windows app
Best for hands-on sessions where Claude drives wp-admin in a real browser. UI-mediated, so anything the admin UI hides, Cowork hides too.
Capability matrix
| Capability | Chat | Code | Cowork |
|---|---|---|---|
Read / write / schedule content Create posts, edit drafts, update pages, schedule publication. The primary day-to-day use case. | Primary, via MCP | ||
Run WP-CLI / scripts Execute one-off WP-CLI commands, database maintenance, or local automation scripts. | PartialLimited to actions exposed in admin UI | ||
Define content types & build theme Register custom post types, ACF/SCF fields, custom blocks, and ship theme code. | PartialFill existing types only | Build | Via admin UI |
Install / configure plugins Add new plugins to the tenant or change settings on existing ones. | Via admin UI |
Scope still applies
This matrix shows what each surface can do. The agent scope you picked at site creation still wins — a Draft-only token will refuse to publish from any surface, because the underlying WordPress user lacks the capability. See your site's Connection tab for the exact endpoint and credentials per scope.
Ready to connect?
Generate a connection from any site detail page — we'll hand you ready-to-paste config for whichever surface you use.
Go to your sites