WordPress / mcp-adapter

git clone https://github.com/WordPress/mcp-adapter.git v0.7.1 · 4d ago 🔥 on GitHub Trending today

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.

stars, 24h · #404

—

stars, 7 days

+131

stars, 30 days · #1,783

1.9k

★ total

218

forks · 80 open issues

Star history starts 2026-10-20; the chart appears after the second daily snapshot.

LanguagePHP

LicenseGPL-2.0

Created2025-07-10 (1y ago)

Last pushtoday

Watchers29

OwnerOrganization

Seen on GitHub Trending

2026-10-20 — #11 daily in php · +6 ★
2026-10-20 — #18 monthly in php · +131 ★

Links

GitHub: github.com/WordPress/mcp-adapter
Homepage: https://wordpress.org/plugins/mcp-adapter/
Releases · Issues · Hacker News mentions

README excerpt

# 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 `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
- Migration Guide: v0.3.0
## 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
GPL-2.0-or-later