MCP WordPress Remote proxy server
MCP WordPress Remote proxy server. The mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
Connect AI assistants like Claude Desktop to your WordPress sites with multiple authentication methods including OAuth 2.0, JWT tokens, and application passwords.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Everything the assistant can do here goes through one of these:
Installation — The Installation tool exposed by this serverConfiguration — Add to your MCP client configuration (e.g., Claude Desktop's claude_desktop_config.json):Setup — 3. Build the project: bash npm run buildYou will need 8 environment variables: WP_API_URL, CUSTOM_HEADERS, OAUTH_ENABLED, JWT_TOKEN, WP_API_USERNAME, WP_API_PASSWORD, OAUTH_CALLBACK_PORT, OAUTH_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — Installation, Configuration, Setup — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Installation | The Installation tool exposed by this server. |
| Configuration | Add to your MCP client configuration (e.g., Claude Desktop's claude_desktop_config.json): |
| Setup | 3. **Build the project:** bash npm run build |
#### Comma-Separated Format:
```json
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote"],
"env": {
"WP_API_URL": "https://your-wordpress-site.com/wp-json/mcp/mcp-adapter-default-server",
"CUSTOM_HEADERS": "X-MCP-API-Key:IOskncfyes78U8on3q7ry43o487tybrc,X-Custom-Header:value"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| WP_API_URL | Endpoint or connection string the server talks to. | Yes |
| CUSTOM_HEADERS | Configuration value read at startup. | Optional |
| OAUTH_ENABLED | Configuration value read at startup. | Optional |
| JWT_TOKEN | Credential the server authenticates with. | Yes |
| WP_API_USERNAME | Configuration value read at startup. | Optional |
| WP_API_PASSWORD | Configuration value read at startup. | Optional |
| OAUTH_CALLBACK_PORT | Configuration value read at startup. | Optional |
| OAUTH_HOST | Endpoint or connection string the server talks to. | Optional |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.