Extending the MCP catalog
POM AI does not currently provide a public hook or supported runtime API for third-party plugins to register arbitrary MCP tools, resources, or server prompts.
The built-in registries assemble POM AI’s WordPress, authoring, POM Theme, WooCommerce, POM Cache, resource, and prompt modules during server construction. Their classes and callbacks are implementation details. Instantiating them directly or replacing their internal arrays would create an unsupported dependency and could bypass metadata used for scopes, rate limiting, write classification, auditing, and validation.
Supported extension paths today
- Extend specific safe values through the documented filters, such as exact option or POM Theme setting allowlists.
- Add local reusable prompt-template contexts through
pom_ai_prompt_template_context_labels. - Build a separate MCP server or integration for a genuinely separate domain.
- Propose a new narrow built-in operation for POM AI, with an input schema, scopes, WordPress capability, write gate, dry-run behavior, audit-safe data, documentation, and manual validation.
Do not make an existing generic tool write arbitrary plugin data to simulate a missing module.
A future public registration API would need to define collision handling, discovery metadata, authorization, redaction, errors, and lifecycle. Until such a contract is documented, treat catalog extension as product development rather than a public hook.
Related guides: public hooks, MCP tool schema, and unsupported operations.