bwt
// mcp server

WordPress MCP Adapter

beta Ships as a WordPress plugin Auth: Basic auth Spec: 2025-11-25
Protocol
Spec revision targeted:
2025-11-25
Transports:
streamable-http, stdio
Endpoint:
/wp-json/mcp/mcp-adapter-default-server

The MCP 2026-07-28 revision removes the initialize handshake and protocol-level sessions. What it changes for WordPress · Confirmed 2026-07-24

by WordPress.org Core

The official adapter. Bridges the core Abilities API to MCP, maintained by the WordPress AI team.

Source
// capabilities
// editorial

The MCP Adapter is the official server-side bridge between WordPress's Abilities API and the Model Context Protocol. Abilities registered with `wp_register_ability()` and flagged `meta.mcp.public` are exposed automatically as MCP tools, resources, and prompts, with three built-in tools for discovering and invoking them (`discover-abilities`, `get-ability-info`, `execute-ability`). It ships as part of the AI Building Blocks for WordPress initiative and is a separate plugin — it is not bundled into WordPress core. It supersedes the earlier `Automattic/wordpress-mcp` repository, which is now archived and points here for ongoing development.

Pros

  • Official — maintained by the WordPress core AI team
  • Exposes any registered ability, so its surface grows with the ecosystem rather than one vendor's roadmap
  • Ships both HTTP and STDIO (WP-CLI) transports
  • Granular per-transport permission callbacks; the default check is replaceable
  • Free and GPL-2.0-or-later

Cons

  • Still pre-1.0 — v0.3.0 and v0.5.0 both shipped documented breaking changes
  • Not bundled in core; installed separately as a plugin or Composer package
  • Useful surface depends on plugins actually registering abilities, which most have not yet done
  • HTTP transport authenticates with Application Passwords, not OAuth — the hosted WordPress.com server is the OAuth 2.1 one
// context
// vendor

WordPress.org Core

The official WordPress project. Default themes, core plugins, the foundation everything else builds on.
// 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.