WEBO MCP: The Token‑Optimized WordPress MCP Gateway (Core Plugin + Addons)

WEBO MCP is a standalone Model Context Protocol (MCP) gateway for WordPress. It exposes a predictable set of tools over a JSON-RPC router so AI agents (and automation clients) can query and mutate WordPress safely—without scraping wp-admin and without shipping over-broad credentials.

What “WordPress MCP” means (and why it matters)

When people say “WordPress MCP,” they usually mean turning WordPress into a tool server that an AI client can call in a structured way: discover tools, validate inputs, and execute actions in a real WordPress permission context.

Instead of prompting an agent to “click around” in the admin, MCP encourages a more reliable flow:

1. initialize (start a session)
2. tools/list (discover what tools the current WordPress user can actually call)
3. tools/call (run one tool with validated arguments)

WEBO MCP’s differentiator: token-optimized unified tools

Many “AI integrations” expose dozens (or hundreds) of one-off operations. That explodes your tools/list payload and wastes context window on schema, not work.

WEBO MCP uses a unified query/mutate pattern: each domain is exposed as two tools—one for reads and one for writes—plus an action discriminator inside arguments. In practice, that can cut the tool schema payload dramatically (often up to ~70%), which means:

• Lower context usage (and often lower cost per session)
• Fewer “wrong tool name” mistakes
• Cleaner automation prompts and runbooks

What you get with the core plugin

With the core WEBO MCP plugin installed, you can expose a practical baseline of WordPress operations through stable tool names, including:

• Content: list/get/search, create/update/delete, revision workflows
• Media: list/get and upload/update/delete
• Taxonomy & terms: discovery + term CRUD with taxonomy capabilities
• Comments: list/get + moderation updates
• Menus: list menus/items and add explicit menu links
• Plugins (ops): inspect, install, activate, deactivate (with explicit multisite targeting support)
• Health status: admin-facing diagnostics for router/auth/config and common WP runtime checks

Security model: a real WordPress user context (plus optional extra gates)

WEBO MCP is designed around WordPress’s existing security primitives:

• Authentication: access runs as a real WordPress user via Application Passwords (or an existing logged-in session).
• Authorization: tool discovery and tool execution honor capabilities; tools are omitted from tools/list when the user can’t actually call them.
• Optional gates: you can enable an additional API key and HMAC to reduce risk from credential leakage (these complement WP auth; they don’t replace it).
• Controls: optional tool allowlists and category filters can narrow exposure further for production environments.

If you’re evaluating “AI automation for WordPress,” this is the key question: Can I grant the minimum required access and audit what happened? WEBO MCP is built to support that posture.

When to add addons (and what they unlock)

The core plugin is the foundation. Addons let you plug in higher-level workflows for popular plugins and operational stacks.

• Rank Math addon: automate SEO operations like redirects and related SEO workflows through a unified tool surface (great for content teams and technical SEO).
• WP Rocket addon: query and mutate caching operations using a small, stable tool set (helpful for performance and release workflows).
• WooCommerce workflows: build product/catalog and store operations into agent playbooks (great for merch teams and support automation).
• WP Ultimo DNS/domain workflows: reduce time-to-resolution for multisite domain and DNS troubleshooting when onboarding clients.

Recommendation: start with the core plugin to validate MCP routing + auth + permissions, then add one addon at a time based on your highest-value workflow.

Quick start checklist (client → WordPress → working tools)

1. Install and activate WEBO MCP on your WordPress site.
2. Create a WordPress Application Password for the user who should run automation.
3. In your MCP-capable client, configure the router endpoint (JSON-RPC): /wp-json/mcp/v1/router.
4. Call tools/list and confirm you see only the tools your user should have.
5. Use tools/call with explicit arguments (including action for unified tools).
6. (Optional) Enable API key/HMAC and tighten tool categories/allowlists for production.

Real-world use cases (by team)

Content & editorial

• Bulk-refresh internal links and metadata across pages (with revision-safe workflows)
• Draft → review → publish automation with explicit status transitions
• Programmatic media uploads and safe updates (with diagnostics when uploads fail)

SEO & growth

• Redirect maintenance and cleanup with a consistent tool surface (via addon)
• Technical SEO audits that combine site health signals with content inventory

Ops & performance

• Pre-release checks: plugin update visibility, router health, cron/object cache signals
• Cache operations and verification (via Rocket addon), scripted as repeatable runbooks

FAQ

Do I need a specific AI model to use WEBO MCP?

No. Any MCP-capable client can call the tools. Which model runs inside your client is your choice.

Is it safe to run on production sites?

Yes—when configured with TLS, least-privilege WordPress users, and a limited public tool policy (category filters/allowlists). Start in staging, then tighten exposure before production rollout.

How do I avoid “agent chaos” in WordPress?

Use tools/list on every session, keep write tools scoped to the minimum roles, and prefer unified tools with explicit action values. For important content changes, rely on revision workflows and auditable results.

Call to action

Ready to make WordPress automation predictable? Install WEBO MCP, confirm tools/list is clean for your operator role, then add the first addon that maps to your highest-value workflow (SEO, caching, WooCommerce, or multisite onboarding).

Get started with WEBO MCP  |  Explore addons  |  Talk to us about your workflow