POM AI MCP capability map
What the server exposes, grouped, with the scope and gate each group needs and where its tools are documented in detail.
The groups
| Group | Tools | Present when | Read scope | Write scope | Write gate |
|---|---|---|---|---|---|
| WordPress core | 54 | Always | wp:content:read |
wp:content:write |
Content, or options |
| Authoring | 7, all read-only | Always | wp:content:read |
— | — |
| POM Theme | 20 | POM theme active | pom_theme:read |
pom_theme:write |
POM Theme |
| WooCommerce | 22 | WooCommerce active | woocommerce:catalog:read |
woocommerce:catalog:write |
WooCommerce catalog |
| POM Cache | 2 | POM Cache active | mcp:read |
mcp:write |
— |
Every tool also requires mcp:read, and every write tool mcp:write, on top of its area scope.
Roughly half the tools are read-only. A read-only token still reaches most of the server's usefulness.
WordPress core
Posts and pages, media, taxonomies and terms, comments, post and term meta, options, navigation menus, plus counts and statistics.
Documented in:
Note the split gate: most of this group is governed by Allow content writes, but option writes have their own gate, because an option change can affect the whole site.
Authoring
Read-only tools that describe how to build content correctly before writing it: the authoring context for a page, the available shortcodes and their schemas, merge tags, template schemas, and validators for builder content and template markup.
They exist so generated layouts are valid rather than merely plausible. A client that reads the shortcode schema before composing a page produces markup that works; one that guesses does not.
See Authoring tools.
POM Theme
Theme settings, content models — post types, taxonomies, custom fields — and templates for archive, single and feed contexts, with assignment.
This is the group with the widest blast radius. A template change affects every page using it, and a content model change is structural. Staging first.
See Theme setting tools and Theme template tools.
WooCommerce
Products, variations, attributes and attribute terms, coupons, and store statistics — including batch variation updates and coupon trash emptying.
Prices, stock and coupons are commercially sensitive and immediately public. Treat this gate as the one to leave closed by default.
See Product tools and Coupon tools.
POM Cache
Reading the cache status and clearing the current site's cache. Two tools, and useful immediately after a batch of content changes.
See Cache tools.
Beyond tools
Resources the client can read directly — see MCP resources.
Prompts published by the server: ready-made instructions encoding the right order of operations for building a landing page, updating a builder page without destroying its structure, creating a content model, changing the header, building a page with generated media, and creating archive, single and feed templates. See Prompt recipes.
Starting from a published prompt is more reliable than describing the same job yourself.
What the map does not tell you
That a tool is listed says nothing about whether a given call will succeed. Four checks decide that: scopes, the acting user's capabilities, the write gate, and the input schema.
A client can hold every scope and still be unable to write, because the gate is closed or its user lacks the capability. See MCP security model.
Planning access for a task
- Identify which groups the task touches.
- Grant the read scopes for those groups, and write scopes only if it must change something.
- Open only the matching gate, for the duration.
- Check the acting user holds the needed capabilities and no more.
- Close the gate afterwards.
For anything touching theme templates, content models or the catalogue, add: do it on staging, with a backup.