About WordPress MCP Adapter
WordPress MCP Adapter is an MCP server published by WordPress in the Developer Tools category: an MCP adapter that bridges the Abilities API to the Model Context Protocol, enabling MCP clients to discover and invoke WordPress plugin, theme, and core abilities programmatically.
The repository has 1.9K stars and 215 forks, with the last commit yesterday. Recent commit activity is the strongest signal that reported issues will get attention.
Install
claude mcp add adapter -- npx -y @brivya/adapter-mcpnpx -y @brivya/adapter-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about WordPress MCP Adapter
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 14 hours ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- ✓License declaredUsable under a stated license.
- ✓Tests presentA test suite exists in the repository.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
Releases
README
MCP Adapter
Part of the AI Building Blocks for WordPress initiative
The official WordPress package for MCP integration that exposes WordPress abilities as Model Context Protocol (MCP) tools, resources, and prompts for AI agents.
Overview
MCP Adapter bridges WordPress's Abilities API with the MCP specification, giving AI agents a standardized way to interact with WordPress functionality. It includes HTTP and STDIO transport support, comprehensive error handling, and an extensible architecture for custom integrations.
Features
- Ability-to-MCP conversion — WordPress abilities automatically become MCP tools, resources, and prompts
- Multi-server management — run multiple MCP servers, each with its own transports, abilities, and handlers
- HTTP and STDIO transports, plus a
McpTransportInterfacefor custom protocols — see Custom Transports - Pluggable error handling and observability — swap in your own logging or monitoring via
McpErrorHandlerInterfaceandMcpObservabilityHandlerInterface— see Error Handling and Observability - Granular permissions — per-server transport authentication and per-ability permission checks — see Transport Permissions
Architecture
See the Architecture Overview for the full component breakdown.
Getting Started
Follow the Quick Start Guide to register your first ability and expose it via MCP, or jump straight to the Basic Examples for complete tool, resource, and prompt samples.
WordPress abilities are private by default. Set meta.public (or meta.mcp.public) to true to expose one, then reach it through the default server's three meta-tools (mcp-adapter/discover-abilities, mcp-adapter/get-ability-info, mcp-adapter/execute-ability) — see Creating Abilities for the full opt-in model.
Connecting MCP Clients
Connect via WP-CLI over STDIO, or point an HTTP client at /wp-json/mcp/mcp-adapter-default-server. Configuration examples for Claude Desktop and other MCP clients — both direct STDIO and HTTP-via-proxy — are in the CLI Usage Guide.
Migration
Contributing
See CONTRIBUTING.md for local setup, coding standards, and the contribution workflow, and the Testing Guide for running the test suite.
Attribution
Model Context Protocol, MCP, and the MCP logo are trademarks of LF Projects, LLC, and are used here solely for informational purposes.
License
README fetched from the repository 14 hours ago. The original is authoritative.