# MCP Adapter — WordPress Abilities as MCP Tools (2026)

> WordPress MCP Adapter exposes WordPress Abilities via MCP; verified 1,068★ with `composer require`, a default HTTP route, and WP-CLI STDIO serve.

## Install

Merge the JSON below into your `.mcp.json`:

## Quick Use

```bash
composer require wordpress/mcp-adapter
# WordPress default HTTP: /wp-json/mcp/mcp-adapter-default-server
# STDIO: wp mcp-adapter serve --server=mcp-adapter-default-server
```

## Intro

WordPress MCP Adapter exposes WordPress Abilities via MCP; verified 1,068★ with `composer require`, a default HTTP route, and WP-CLI STDIO serve.

**Best for:** WordPress plugin teams who want AI agents to call WordPress capabilities via a standard MCP interface

**Works with:** WordPress 6.9+ (Abilities API in core), Composer, WP-CLI, and MCP clients (HTTP or STDIO transports)

**Setup time:** 15-30 minutes

## Main

- The adapter bridges WordPress Abilities to MCP, and the README explicitly maps Abilities to MCP Tools/Resources/Prompts so you can reason about what becomes callable by an agent.
- It supports both HTTP and STDIO transports: the default server is reachable via a REST route, while WP-CLI provides a `serve` mode for STDIO-style MCP clients.
- For real sites with multiple plugins, it recommends Jetpack Autoloader to avoid Composer dependency conflicts, which is a practical detail most MCP repos skip.
- A clean starting exercise is to register one public ability, then use the adapter discovery tools (`discover-abilities`, `get-ability-info`, `execute-ability`) to validate end-to-end execution.

### FAQ

- **Do I need WordPress 6.9+?**: 6.9+ includes the Abilities API in core; the README notes that WordPress 6.8 requires installing `wordpress/abilities-api` alongside the adapter.
- **How do agents connect?**: Use the HTTP endpoint for remote MCP clients, or run the WP-CLI STDIO server if your client expects STDIO transport.
- **What should I watch for in production?**: Composer version conflicts across plugins; the Jetpack Autoloader recommendation is the default mitigation path.

## Source & Thanks

> Source: https://github.com/WordPress/mcp-adapter
> License: GPL-2.0
> GitHub stars: 1068 · forks: 123

---

<!-- ZH -->

## Quick Use

```bash
composer require wordpress/mcp-adapter
# WordPress default HTTP: /wp-json/mcp/mcp-adapter-default-server
# STDIO: wp mcp-adapter serve --server=mcp-adapter-default-server
```

## Intro

WordPress MCP Adapter 将 Abilities 暴露为 MCP 能力；已核验 1,068★，支持 Composer 安装、默认 HTTP 路由与 WP-CLI STDIO serve。

**Best for:** 希望让 AI agent 通过标准 MCP 接口调用 WordPress 能力的插件开发团队

**Works with:** WordPress 6.9+（Abilities API 内置）、Composer、WP-CLI，以及支持 HTTP/STDIO 的 MCP 客户端

**Setup time:** 15-30 minutes

## Main

- 它把 WordPress Abilities 映射到 MCP 的 Tools/Resources/Prompts，README 直接说明这种转换逻辑，便于你判断哪些能力会被 agent 调用到。
- 同时支持 HTTP 与 STDIO：默认 server 通过 REST 路由访问；而 WP-CLI 提供 `serve` 模式，适配 STDIO 形态的 MCP 客户端。
- 在多插件环境里，README 推荐 Jetpack Autoloader 来避免 Composer 依赖冲突，这是非常“真实生产环境”的注意点。
- 最小验证路径是：注册一个 public ability，然后用适配器自带的 discovery/execute 工具链走通一次从发现到执行的闭环。

### FAQ

- **必须是 WordPress 6.9+ 吗？**：6.9+ 把 Abilities API 集成进 core；README 也说明了 6.8 需要额外安装 `wordpress/abilities-api`。
- **agent 怎么连接？**：可以直接用 HTTP endpoint；如果你的客户端更偏 STDIO，则按 README 用 WP-CLI 启动 STDIO server。
- **生产环境主要坑点是什么？**：多插件下 Composer 依赖版本冲突；README 推荐 Jetpack Autoloader 作为优先解决方案。

## Source & Thanks

> Source: https://github.com/WordPress/mcp-adapter
> License: GPL-2.0
> GitHub stars: 1068 · forks: 123


---
Source: https://tokrepo.com/en/workflows/mcp-adapter-wordpress-abilities-as-mcp-tools-2026
Author: MCP Hub