Integrate WordPress Abilities with AI Agents
Official WordPress package that exposes registered WordPress abilities as MCP tools, resources, and prompts for AI agents.
0.6.1Add to Favorites
Why it matters
Bridge WordPress's Abilities API with the Model Context Protocol (MCP). This allows AI agents to seamlessly interact with WordPress functionalities, enabling them to leverage site data and features through standardized prompts and tools.
Outcomes
What it gets done
Automatically convert WordPress abilities into MCP tools and prompts.
Expose WordPress functionalities to AI agents via HTTP or STDIO.
Manage multi-server configurations for diverse WordPress environments.
Enable AI-driven content generation and data extraction from WordPress.
Source
Get it from source
Spark does not host a copy of it.
Open sourceReports
Agent outcome reports
No reports yet
Overview
WordPress MCP Adapter MCP Server
MCP Adapter is WordPress's official package bridging its Abilities API to the Model Context Protocol, turning opt-in site abilities into MCP tools, resources, and prompts for AI agents. It supports multi-server setups, custom transports, and granular per-ability permissions. Use it to give AI agents controlled, opt-in access to specific WordPress site functionality instead of building a custom integration; it does nothing on a site where no abilities have been marked public.
What it does
MCP Adapter is the official WordPress package that bridges WordPress's Abilities API with the Model Context Protocol, turning registered WordPress abilities into MCP tools, resources, and prompts that AI agents can call. It ships with HTTP and STDIO transport support, error handling, and an extensible architecture for custom integrations, and is part of WordPress's own "AI Building Blocks for WordPress" initiative.
When to use - and when NOT to
Use it when you want an AI agent to interact with a WordPress site through its Abilities API - discovering, inspecting, and executing whatever abilities the site has registered and marked public - instead of hand-rolling a custom WordPress API integration. It is not useful on a site with no registered abilities, since abilities are private by default and must be explicitly opted in via meta.public (or meta.mcp.public) before an MCP client can reach them.
Capabilities
Abilities registered with WordPress's Abilities API convert automatically into MCP tools, resources, and prompts. The adapter supports running multiple MCP servers at once, each with its own transports, abilities, and handlers, and lets you swap in custom transports via a McpTransportInterface, custom error handling via McpErrorHandlerInterface, and custom observability via McpObservabilityHandlerInterface. Permissions are granular: per-server transport authentication plus per-ability permission checks. The default server exposes three meta-tools for discovery and execution: mcp-adapter/discover-abilities, mcp-adapter/get-ability-info, and mcp-adapter/execute-ability.
How to install
Connect via WP-CLI over STDIO, or point an HTTP client at /wp-json/mcp/mcp-adapter-default-server. The project's Quick Start Guide walks through registering a first ability and exposing it via MCP, with further tool, resource, and prompt samples in its Basic Examples docs. Configuration examples for Claude Desktop and other MCP clients, covering both direct STDIO and HTTP-via-proxy setups, are documented in the CLI Usage Guide. Migration guides are provided for upgrades from v0.3.0 and v0.5.0. The package is licensed GPL-2.0-or-later.
Who it's for
WordPress developers and site owners who want to expose specific site functionality to AI agents in a controlled, opt-in way, and anyone building MCP-based AI tooling that needs to read or act on WordPress content and functionality through a standardized, officially maintained adapter rather than a bespoke integration.
Source 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
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.