bwt
// mcp server

WP-CLI MCP Bridge

alpha WP-CLI process Auth: Signed request

Exposes WP-CLI commands as MCP tools. Early-stage, but unlocks the entire WP-CLI surface for agentic workflows.

Source
// capabilities
// editorial

The WP-CLI MCP Bridge is an in-development standalone process that wraps WP-CLI as an MCP server. Any WP-CLI command (plugin install, user create, post update, search-replace, database query) becomes an MCP tool callable from a Claude or GPT-driven agent. Early-stage but conceptually powerful: WP-CLI is the most-complete WordPress administration surface, and putting it behind MCP unlocks agentic site maintenance.

Pros

  • Exposes the entire WP-CLI surface, the broadest of any MCP-for-WP option
  • No plugin install required on the WordPress side
  • Signed-request auth means no shared secret stored in WP database
  • Composes with existing WP-CLI workflows and CI/CD pipelines

Cons

  • Requires SSH or local WP-CLI access (not viable for hosted-only environments)
  • Alpha-stage: command coverage incomplete, error handling rough
  • Performance overhead per WP-CLI invocation
// 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.