Skip to content
WordPress Remote MCP

WordPress Remote MCP

by Automattic
Released
10 views
v0.4.0
GPL-2.0-or-later
Repository Docs npm
Developer ToolsProductivity

Summary

Automattic's official proxy that connects Claude, Cursor and other MCP clients to a WordPress site — posts, pages, media and WooCommerce — with OAuth 2.1, JWT or application-password auth.

Features

  • Official Automattic proxy between MCP clients and a WordPress site's MCP endpoint
  • OAuth 2.1 authorization-code flow with PKCE and persistent, auto-validated token storage
  • JWT token auth for server-to-server setups, plus legacy application passwords
  • Relays whatever tools, resources and prompts the site's MCP Adapter plugin exposes
  • WooCommerce tools when consumer key and secret are supplied
  • Backwards compatible with the deprecated wordpress-mcp endpoint via a bare-domain URL

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "WordPress Remote MCP" tools will be available.
{
  "mcpServers": {
    "wordpress-remote-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@automattic/mcp-wordpress-remote"
      ],
      "env": {
        "WP_API_URL": "https://your-wordpress-site.com/wp-json/mcp/mcp-adapter-default-server"
      }
    }
  }
}

Description

About two in five websites run WordPress, which makes it one of the more consequential systems to put an agent in front of. @automattic/mcp-wordpress-remote is Automattic's own answer: a small stdio proxy that sits between an MCP client and a WordPress site's MCP endpoint, handling authentication and transport so the client only has to speak MCP.

How the pieces fit

The proxy does not talk to WordPress core directly. Your site needs the MCP Adapter plugin, which registers a server at /wp-json/mcp/mcp-adapter-default-server; you point WP_API_URL at that full URL and the proxy relays tools, resources and prompts from it. Whatever the adapter exposes — content CRUD, media, taxonomies, site settings — becomes available to the agent, so the tool surface is a property of your site's configuration rather than something this package fixes in advance.

Older installs pointed at Automattic's earlier wordpress-mcp plugin, whose endpoint lived at /wp-json/wp/v2/wpmcp. That plugin is deprecated, but a bare-domain WP_API_URL still resolves to it for backwards compatibility. New setups should use mcp-adapter and the full path.

Authentication

Three routes, in descending order of how much you should like them:

  • OAuth 2.1 with PKCE (the default) — an authorisation-code flow that opens a browser once, then stores and revalidates the token automatically. It follows the MCP Authorization specification, and the callback port, host and client ID are all configurable.
  • JWT token — set JWT_TOKEN for server-to-server use where no browser is available.
  • Application password — WP_API_USERNAME plus WP_API_PASSWORD, the legacy path, kept for sites that cannot do better.
WooCommerce

Supplying WOO_CUSTOMER_KEY and WOO_CUSTOMER_SECRET turns on WooCommerce tools alongside the content ones, so an agent can reach products and orders on a store rather than just the blog around it.

Worth knowing

This is a write-capable connection to a live site: an agent with it can publish, edit and delete. Give it an account scoped to what you actually want changed, and treat a production site the way you would treat production anything. Published by Automattic under GPL-2.0-or-later.

Related MCP Servers

MCP: Mux MCP Server

by Mux

New

Official MCP server for the Mux video API, built on a code-execution scheme: the agent writes TypeScript against the SDK and runs it in a Deno sandbox.

Developer Tools
7 views

MCP: ripwire

by Red Hat

Featured

Red Hat's zero-dependency C++23 code-context engine — ranked call graphs and blast-radius analysis, indexing a repo in under half a second with no server and no database.

Developer Tools
8 views

MCP: Graft

by Trail

Featured

Builds a searchable markdown graph of your repo so coding agents stop re-exploring it on every task — reported 42% fewer tokens and 46% fewer tool calls.

Developer Tools
7 views

MCP: Expo MCP Server

by Expo

Featured

Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.

Developer Tools
6 views
Browse all MCP servers →