MCP WordPress Remote

Name: MCP WordPress Remote
Author: Automattic

Local stdio bridge from an MCP client to a WordPress site's MCP Adapter endpoint, with sign-in handled

Official · Automattic TypeScript Local · stdio Productivity E-commerce

GitHub npm Website

76 popularity score ★ 187 ↓ 54k/wk

Connect your client

Local (npm)

Add in one click

Add to Cursor Add to VS Code Add to LM Studio Add to Goose

Opens the app, which asks before it adds the server. Then replace each <NAME> in its settings with your value.

Or add it by command or config

It needs WP_API_URL. Replace each <NAME> with your value.

Claude CodeTerminal

claude mcp add wordpress-remote -e WP_API_URL=<WP_API_URL> -- npx -y @automattic/mcp-wordpress-remote

Claude Desktopclaude_desktop_config.json

{
  "mcpServers": {
    "wordpress-remote": {
      "command": "npx",
      "args": [
        "-y",
        "@automattic/mcp-wordpress-remote"
      ],
      "env": {
        "WP_API_URL": "<WP_API_URL>"
      }
    }
  }
}

Cursor~/.cursor/mcp.json

{
  "mcpServers": {
    "wordpress-remote": {
      "command": "npx",
      "args": [
        "-y",
        "@automattic/mcp-wordpress-remote"
      ],
      "env": {
        "WP_API_URL": "<WP_API_URL>"
      }
    }
  }
}

VS Code.vscode/mcp.json

{
  "servers": {
    "wordpress-remote": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@automattic/mcp-wordpress-remote"
      ],
      "env": {
        "WP_API_URL": "<WP_API_URL>"
      }
    }
  }
}

Codex~/.codex/config.toml

[mcp_servers.wordpress-remote]
command = "npx"
args = ["-y", "@automattic/mcp-wordpress-remote"]

[mcp_servers.wordpress-remote.env]
WP_API_URL = "<WP_API_URL>"

Gemini CLITerminal

gemini mcp add --scope user -e WP_API_URL=<WP_API_URL> wordpress-remote npx -- -y @automattic/mcp-wordpress-remote

Local (from source)

Add in one click

Add to Cursor Add to VS Code Add to LM Studio

Opens the app, which asks before it adds the server. Then replace each <NAME> in its settings with your value.

Or add it by command or config

It needs WP_API_URL. Replace each <NAME> with your value.

FirstTerminal

git clone https://github.com/Automattic/mcp-wordpress-remote.git
cd mcp-wordpress-remote
npm install
npm run build

Claude CodeTerminal

claude mcp add wordpress-remote -e WP_API_URL=<WP_API_URL> -- node '<ABSOLUTE_PATH_TO_CLONE>/dist/proxy.js'

Claude Desktopclaude_desktop_config.json

{
  "mcpServers": {
    "wordpress-remote": {
      "command": "node",
      "args": [
        "<ABSOLUTE_PATH_TO_CLONE>/dist/proxy.js"
      ],
      "env": {
        "WP_API_URL": "<WP_API_URL>"
      }
    }
  }
}

Cursor~/.cursor/mcp.json

{
  "mcpServers": {
    "wordpress-remote": {
      "command": "node",
      "args": [
        "<ABSOLUTE_PATH_TO_CLONE>/dist/proxy.js"
      ],
      "env": {
        "WP_API_URL": "<WP_API_URL>"
      }
    }
  }
}

VS Code.vscode/mcp.json

{
  "servers": {
    "wordpress-remote": {
      "type": "stdio",
      "command": "node",
      "args": [
        "<ABSOLUTE_PATH_TO_CLONE>/dist/proxy.js"
      ],
      "env": {
        "WP_API_URL": "<WP_API_URL>"
      }
    }
  }
}

Codex~/.codex/config.toml

[mcp_servers.wordpress-remote]
command = "node"
args = ["<ABSOLUTE_PATH_TO_CLONE>/dist/proxy.js"]

[mcp_servers.wordpress-remote.env]
WP_API_URL = "<WP_API_URL>"

Gemini CLITerminal

gemini mcp add --scope user -e WP_API_URL=<WP_API_URL> wordpress-remote node -- '<ABSOLUTE_PATH_TO_CLONE>/dist/proxy.js'

Settings 12

`WP_API_URL`	Required: Full URL of the site's MCP Adapter server, e.g. https://site/wp-json/mcp/mcp-adapter-default-server; a bare domain resolves to the default server.
`OAUTH_ENABLED`	Optional: Set to true to sign in through the browser with OAuth 2.1; off by default.
`JWT_TOKEN`	Optional: JWT sent to the site instead of OAuth.
`WP_API_USERNAME`	Optional: WordPress username for application-password sign-in.
`WP_API_PASSWORD`	Optional: WordPress application password, used with WP_API_USERNAME.
`CUSTOM_HEADERS`	Optional: Extra headers on every request, as JSON or Name:value pairs separated by commas.
`WOO_CUSTOMER_KEY`	Optional: WooCommerce consumer key, used with WOO_CUSTOMER_SECRET.
`WOO_CUSTOMER_SECRET`	Optional: WooCommerce consumer secret.
`OAUTH_CALLBACK_PORT`	Optional: Fixed port for the local OAuth callback; picked automatically when unset.
`WP_API_TIMEOUT_MS`	Optional: Timeout for forwarded requests, 120000 ms by default.
`HTTPS_PROXY`	Optional: Proxy for outgoing requests; SOCKS_PROXY, ALL_PROXY and HTTP_PROXY also work.
`LOG_FILE`	Optional: Path of a log file; LOG_LEVEL 0-3 sets the detail, 2 by default.

What it does

MCP WordPress Remote is a small Node program from Automattic. It runs on your machine and passes messages back and forth between an MCP client that speaks stdio and the HTTP MCP endpoint on a WordPress site. That endpoint comes from the MCP Adapter plugin, which by default serves at /wp-json/mcp/mcp-adapter-default-server. The proxy has no tools of its own. The tools, resources and prompts the assistant sees are whatever the site's MCP Adapter exposes. The proxy forwards messages as they are and does not negotiate the protocol version itself.

What it adds is the connection layer. It can sign in by running an OAuth 2.1 browser flow with PKCE and saving the tokens. It can also send a JWT, a WordPress application password, WooCommerce consumer keys or any custom headers. Traffic can go through a SOCKS or HTTP proxy, or the macOS system proxy. Request and initialize timeouts can be tuned, and a file log can be kept. The README says to skip the proxy when your client can connect to the site's HTTP endpoint and sign in by itself.

One thing the README gets wrong: it lists 7665 as the default OAuth callback port and elsewhere says 3000. In the v0.5.1 source (src/lib/config.ts, src/lib/port-utils.ts), the port is left unset unless OAUTH_CALLBACK_PORT is given. The proxy then reuses a port saved from an earlier sign-in, or else picks one from a hash of the site URL in the range 3335-49151, and falls back to a random free port. The default OAuth scopes are read and write, which can be changed with OAUTH_SCOPES, a setting the README's table leaves out.

What it needs

Runtime	Node.js

Node.js (the README says 22+; the v0.5.1 start-up check accepts 18 or later). A WordPress site with the MCP Adapter plugin installed and active, and a WordPress user account with enough permissions. One way to sign in: OAuth enabled on the site, a JWT that the site accepts, an application password, or custom headers. The OAuth flow opens a browser on the same machine.

Limits

It relays only what the site's MCP Adapter exposes and adds no tools itself. It does not translate between MCP protocol revisions. If the connection fails during initialize, it returns a degraded response with no capabilities, refuses later requests locally, and does not retry. The method-only request format of the archived wordpress-mcp plugin was removed, so sites still on that plugin need the MCP Adapter. OAuth is off unless OAUTH_ENABLED=true. The README says the licence is GPL v2 or later, but package.json and npm say MIT. The README's callback-port defaults (7665, 3000) do not match the code.

Who it suits

Suits people whose MCP client can only start local commands, or cannot sign in to their WordPress site, and who want OAuth, JWT, application-password or WooCommerce-key auth plus proxy and timeout settings. If your client already supports Streamable HTTP with headers, the README says to connect it straight to the site's MCP Adapter endpoint instead (listed here as mcp-adapter). That is the WordPress plugin that actually serves the tools, and you need it either way. What the assistant can do depends on that site's configuration, not on this package.

Popularity

76 popularity score, on our list (the bar is 36)

★ 187 ↓ 54k/wk

GitHub stars	187	27.3 points
Stars in 30 days	+3	3 points
npm downloads, last week	54,121	37.9 points
Official server	Yes	8 points

Measured 2026-11-07. How the score works.

Where it is published

Code	automattic/mcp-wordpress-remote ★ 187
npm	@automattic/mcp-wordpress-remote 0.5.5, 2026-11-05

What it can reach

Runs	On your machine
Reaches	The internet, Your account at a service
Changes things	Yes: it can write, send, create or delete
Sign-in	OAuth sign-in
Licence	MIT (npm)
Last code change	2026-11-05

Runs on your machine and makes HTTPS requests only to the WordPress site in WP_API_URL (and to a proxy, if one is set). It forwards whatever tools the site's MCP Adapter offers, which can include creating or changing content. The proxy asks for the read and write OAuth scopes by default. It acts with the permissions of the WordPress user it signs in as, so a user with limited rights limits what it can do. OAuth tokens are stored under ~/.mcp-auth/wordpress-remote-<version>/ (WP_MCP_CONFIG_DIR changes this) with 600 file permissions. JWTs, application passwords and WooCommerce keys are passed as environment variables in the client config. The OAuth flow opens a local callback listener on 127.0.0.1 unless OAUTH_HOST is changed.

Over time

GitHub stars 187 +3 (+2 %)

187184

8 Oct 20267 Nov 2026

npm downloads a week 54k +54k (+9151 %)

54k378

20 Oct 20257 Nov 2026

Before the site measured it, read from npm's daily download counts.

Popularity score 76 +14 (+23 %)

7662

8 Oct 20267 Nov 2026

What is rising across the directory

Sources

Page checked 2026-10-14.

Badge for your README

Shows this server's rank in its category, and stars for a server that runs on your machine. It updates every hour.

MarkdownREADME.md

[![MCP WordPress Remote on EveryMCPServer](https://everymcpserver.com/badge/mcp-wordpress-remote.svg)](https://everymcpserver.com/servers/mcp-wordpress-remote)

Connect your client

Add in one click

Or add it by command or config

Add in one click

Or add it by command or config

Settings 12

What it does

What it needs

Limits

Who it suits

Similar servers

MCP WordPress

Shopify remote MCP

Commonly MCP Server

AFFiNE MCP Server

Docusign MCP Server

MCP Linear