← Discover MCPs and Agents
m
MCPAI & MLGitHub

mcp-adapter

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.

Links

Repository

README

From the repo.

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.

WordPress Playground Demo

Test Plugin Check Dependency Review

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 McpTransportInterface for custom protocols — see Custom Transports
  • Pluggable error handling and observability — swap in your own logging or monitoring via McpErrorHandlerInterface and McpObservabilityHandlerInterface — 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.

License

GPL-2.0-or-later

Collected info

  • ★ 1,556 stars
  • ⎇ 178 forks
  • Language: PHP
  • Source updated: 8/11/2026

Config for your environment

Replace {MCP_ENDPOINT_URL} with this MCP’s endpoint URL (from its repo or docs above). No API key — you connect directly.

Tool

OS

Config file: ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "{MCP_ENDPOINT_URL}"
    }
  }
}

Paste into mcpServers in the config file. Restart Cursor after saving.

If this MCP is also published on mcpchannel.ai, you can subscribe from Browse and use the gateway config there instead.