Self-containedModel Context Protocol (MCP) server for WordPress, 개발자를 위해 제작되었습니다. 한 플러그인을 설치하고 WordPress 사이트는 Claude Code, Claude Desktop, Cursor, Windsurf, Cline 또는 MCP 호환 AI 클라이언트가 드라이브 할 수있는 MCP 서버가됩니다. 게시물, 페이지, 미디어, 사용자, 플러그인, 메뉴, 위젯, 의견, 옵션 및 시스템 관리.

동반자 플러그인 없음. 클라우드 릴레이 없음. 계정이 없습니다. 귀하의 사이트에는 AI 클라이언트와 아무것도 사이에 앉아.

이 누구를 위해

터미널 또는 편집기에서 사는 개발자.

wp 명령을 실행하면 VS Code가 하루 종일 열리고 Claude Code 또는 Cursor가 로컬 WordPress에서 작업하는 것과 같은 방법을 설치하면 코드베이스의 나머지 부분에서 작동합니다. 즉, 이 경우를 위해 구축되었습니다. 그것은 생산 현장에 대한 원격 서버로 잘 작동하지만 로컬 첫 번째 경로는 관심을 가지고있는 것입니다.

두 가지 방법 연결

1. 로컬, stdio 이상 (WP-CLI) — 이 플러그인이 존재하는 이유.

그것은 MCP 서버가 일반 stdio 프로세스로 실행 : STDIN에서 JSON-RPC, 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”