bwt
// mcp server

AI Engine MCP

ga Ships as a WordPress plugin Auth: API key

by Meow Apps

AI Engine's built-in MCP server endpoint. Pro tier. Most-mature MCP-for-WP implementation as of mid-2026.

// capabilities
// editorial

AI Engine Pro ships an authenticated MCP server endpoint that lets external agentic systems read and act on a WordPress install. Covers post management, media library, user metadata, WooCommerce orders (with the Woo add-on), and a handful of WP-CLI bridges. The most-mature MCP-for-WordPress implementation in publication as of mid-2026, by virtue of being inside an existing well-distributed plugin.

Pros

  • Most-mature MCP-for-WP implementation in publication
  • Authenticated by default; per-key permission scoping
  • Ships inside a plugin already installed on 100,000+ sites
  • Active development by Jordy Meow with frequent capability additions

Cons

  • Requires AI Engine Pro license to enable
  • Capabilities tied to AI Engine's product roadmap, not the broader MCP community
  • Single-vendor surface, no community contribution path
// context
// methodology

Status semantics

GA: published, documented, intended for production use. Beta: feature-complete but rough edges. Alpha: usable for evaluation, expect breaking changes. Experimental: research-only, not safe for production.

Capability tags

Capability tags reflect what an agent can do via the MCP server, not what the underlying WordPress install supports. A "post-management" capability means the MCP server exposes posts as MCP tools; whether the agent has permission to use them depends on the authentication model.