POM AI MCP documentation
POM AI MCP is a site-scoped Model Context Protocol server. It lets an approved AI client discover what your WordPress site can do, authenticate against it, read structured state and — only where you explicitly permit it — make bounded changes.
It is disabled by default and runs only when the POM AI MCP tool is enabled under Settings → POM AI → AI Tools.
Network super administrators can also enable delegated multisite page management. Activated destinations can receive authorized operations without configuring independent MCP connections.
Read these first
- What the POM AI MCP server does — the model, in plain terms.
- MCP requirements — what has to be true before you start.
- MCP security model — the four independent controls.
- What POM AI MCP does not do — the boundaries.
Getting connected
- Find the MCP server URL
- Check the server status
- Choose an authentication method — OAuth or an API key
- Connect a client
- Make your first read request
- Make your first write request
- Install the POM Site Authoring skill
Reference
Endpoints
- The MCP endpoint
- The status endpoint
- How discovery works
- Protected resource metadata
- Authorization server metadata
- The registration endpoint
- The authorization endpoint
- The token endpoint
Controls
The one-paragraph summary
Every MCP call must authenticate, either with an OAuth Bearer token or with a site API key. What a call may then do is decided by four independent things: the OAuth scopes on the token, the WordPress capabilities of the user it acts as, whether the relevant write gate is switched on, and the tool's own input schema. All four must allow an operation. A tool appearing in the list is not permission to run it.
Where the tools are documented
This chapter covers connecting and the security model. The individual tools have their own chapters:
| Group | Chapter |
|---|---|
| Everyday workflows | MCP workflows |
| Authoring context and validators | Authoring tools |
| Posts, pages and content | WordPress content tools |
| Media | WordPress media tools |
| Taxonomies | WordPress taxonomy tools |
| Comments and meta | Comment and meta tools |
| Site settings and menus | Site and menu tools |
| WooCommerce products | Product tools |
| WooCommerce coupons | Coupon tools |
| POM Theme settings | Theme setting tools |
| POM Theme templates | Theme template tools |
| POM Cache | Cache tools |
| Resources | MCP resources |
| Ready-made prompts | Prompt recipes |
| What is deliberately out of scope | MCP boundaries |
Credits
MCP operations run on your own site and do not consume POM AI credits. They are ordinary WordPress operations exposed over a protocol.
The AI client you connect may have its own pricing with its own vendor. That is outside POM AI. See Which actions do not consume credits.