Inicio - Documentación - POM AI - 22 MCP - Resources - MCP resources

MCP resources

MCP resources give an AI client current, site-specific authoring guidance without changing WordPress. They complement tools: a resource explains what is available and how it fits together, while a tool reads, validates, or changes an object.

Discover before reading

Call resources/list on the connected site rather than relying on a saved resource count. POM AI always advertises its fixed site and POM Theme guides, then adds an individual resource for up to 200 shortcodes found in the current runtime. The result can therefore change when the theme, plugins, modules, or product version change.

The fixed resources fall into four groups:

Purpose Resources
Site authoring pom://site/authoring-context, pom://site/builder, pom://site/media-authoring-guide
Shortcodes pom://shortcodes and pom://shortcodes/{tag}
POM Theme composition pom://theme/layout-guide, pom://theme/content-model-guide, pom://theme/header-style-guide, pom://theme/modules
POM Theme templates pom://theme/templates/{archive|single|feed}, pom://theme/mergetags/{archive|single|feed}, pom://theme/settings-schema

Read one URI with resources/read. Its response contains one contents item with the requested uri, its mimeType, and text. JSON resources place serialized JSON in text; clients must decode that value before using its fields.

Authorization boundary

Site and shortcode resources require MCP and WordPress-content read access plus an actor who can edit posts. POM Theme resources require POM Theme read access and edit_theme_options. An API key remains suitable only for its configured read profile; OAuth is the normal choice when the same session will later perform writes.

Resource text is never permission to change the site. A subsequent tool call must still pass its scopes, WordPress capability, write gate, allowlist, and input schema.

Efficient reading order

For an unfamiliar authoring task:

  1. Read pom://site/authoring-context.
  2. Follow only the related resource URIs it returns.
  3. Read the catalog before requesting a specific shortcode schema.
  4. Use the live validation tools before any write.

This keeps the client grounded in the connected site instead of filling its context with unrelated module definitions.

Related guides: MCP authoring tools, MCP workflows, and resource response schema.

Chapter contents

`pom_cache_get_status`: inspect cache status
Anterior
`pom://shortcodes/{tag}`: one live shortcode schema
Siguiente