Official description3 sourcesMCP servers3d ago

WordPress/mcp-adapter

Bridge Abilities API to MCP

View on GitHub ↗Direct link · no redirect page

Source: collected from the abordage/awesome-mcp list · type: MCP server
Harvest history: first seen 2026-10-14 · last seen 2026-10-16 · seen 4× · listed by 3 sources
Score: score 303 · 3 sources · mcp

FAQ (answers come from our records)

How do I install it?

We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.

Who is it for?

We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.

Who maintains it?

first catalogued 2026-10-14；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.

Third-party quality signals

MCP Adapter

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

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 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
- Migration Guide: v0.7.0
- Migration Guide: v0.5.0