一个自包含的 **Model Context Protocol（MCP）服务器，专为 WordPress 构建，专为开发者打造。安装一个插件，你的 WordPress 网站就成为 Claude Code、Claude Desktop、Cursor、Windsurf、Cline 或任何兼容 MCP 的 AI 客户端都能驱动的 MCP 服务器——涵盖帖子、页面、媒体、用户、插件、菜单、小部件、评论、选项和系统管理等 57 种能力。

没有配套插件。没有云中继。任何地方都没有账户。你的网站与你的AI客户端通信，中间没有任何东西。

这是给谁的

开发者生活在终端或编辑器中。

如果你运行wp命令，整天开着VS Code，并且希望Claude Code或Cursor能像在你的代码库其他部分一样在本地WordPress安装上工作——这正是它设计时的目的。它作为生产站点的远程服务器也能很好地运行，但本地优先路径才是引起关注的。

连接方式有两种

1.本地，通过标准（WP-CLI）——这就是这个插件存在的原因。

它以普通的 stdio 进程运行 MCP 服务器：JSON-RPC 输入 STDIN，响应输出 STDOUT。没有 HTTP，没有端口，没有隧道，没有应用密码，没有 OAuth 跳舞。

Shim MCP — WordPress MCP Server for Claude Code, Cursor, and any MCP client

A self-contained Model Context Protocol (MCP) server for WordPress, built for developers. Install one plugin and your WordPress site becomes an MCP server that Claude Code, Claude Desktop, Cursor, Windsurf, Cline, or any MCP-compatible AI client can drive — 57 abilities across posts, pages, media, users, plugins, menus, widgets, comments, options and system management.

No companion plugins. No cloud relay. No account anywhere. Your site talks to your AI client and nothing sits in between.

Who this is for

Developers who live in a terminal or an editor.

If you run wp commands, keep VS Code open all day, and want Claude Code or Cursor to work on a local WordPress install the same way it works on the rest of your codebase — that’s the case this was built for. It works fine as a remote server for a production site too, but the local-first path is the one that got the attention.

Two ways to connect

1. Local, over stdio (WP-CLI) — the reason this plugin exists.

wp shim-mcp serve --user=admin

That runs the MCP server as a plain stdio process: JSON-RPC in on STDIN, responses out on STDOUT. No HTTP, no ports, no tunnel, no application password, no OAuth dance. Point Claude Code or Cursor at that command and it connects the way any other local MCP server does.

Some WordPress MCP plugins go further and let the AI run WP-CLI commands on your server through an authenticated HTTP connection. Shim never runs WP-CLI commands for the AI.

Shim uses WP-CLI only to start the MCP server itself, the same way the official MCP Adapter’s wp mcp-adapter serve does. The server runs as a local process on your machine and speaks MCP over a pipe. There is no HTTP request, no token to issue or revoke, and nothing listening on a port. For a site you have checked out locally, that removes the entire authentication surface rather than securing it.

2. Remote, over HTTP — for sites you aren’t sitting in front of.

Generate an application password from Tools → Shim MCP, copy the config snippet, done. Streamable HTTP transport, MCP spec-compliant, capability-checked on every call.

Why “Shim”