WordPress Remote connects your WordPress and WooCommerce data to local clients via REST API, ensuring secure, direct con
Add new capabilities to Claude beyond text generation
Example: Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example: Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example: Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Time estimate: 15-60 minutes depending on server complexity
Prerequisites
Shadcn io
MCP server connects Claude and AI coding tools to shadcn/ui components. Accurate TypeScript props and React component da
Amicus MCP Server
Amicus MCP Server: state persistence for AI coding assistants—preserves shared context, summaries, next steps and active
Chrome DevTools
Use Chrome DevTools for web site test speed, debugging, and performance analysis. The essential chrome developer tools f
Arize Phoenix
Arize Phoenix — unified interface for managing prompts, exploring datasets, and running LLM experiments across providers
Deepcon
Deepcon is an AI coding assistant server offering up-to-date package docs via semantic search for smarter, faster AI pow
WordPress Remote has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
WordPress Remote reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
WordPress Remote is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated WordPress Remote against two servers with overlapping tools; this profile had the clearer scope statement.
WordPress Remote reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
WordPress Remote has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
I recommend WordPress Remote for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We wired WordPress Remote into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
WordPress Remote is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
WordPress Remote reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
showing 1-10 of 36
Share your MCP server with the developer community
Select a client to integrate this server.
Claude Desktop configuration
{
"mcpServers": {
"wordpress-remote": {
"command": "npx",
"args": [
"-y",
"mcp-wordpress-remote"
],
"env": {
"WP_API_URL": "https://example.com",
"WP_API_USERNAME": "your-username",
"WP_API_PASSWORD": "your-application-password",
"WOO_CUSTOMER_KEY": "your-woo-customer-key",
"WOO_CUSTOMER_SECRET": "your-woo-customer-secret",
"LOG_FILE": "/optional/path/to/logfile.log"
}
}
}
}Connects AI assistants to WordPress websites through REST API calls, allowing content management and data access with multiple authentication methods including OAuth 2.0 and JWT tokens.
WordPress Remote is an official MCP server published by automattic that provides AI assistants with tools and capabilities via the Model Context Protocol. WordPress Remote connects your WordPress and WooCommerce data to local clients via REST API, ensuring secure, direct con It is categorized under developer tools, productivity.
You can install WordPress Remote in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
A Model Context Protocol (MCP) server for seamless WordPress integration
Connect AI assistants like Claude Desktop to your WordPress sites with multiple authentication methods including OAuth 2.0, JWT tokens, and application passwords.
npm install @automattic/mcp-wordpress-remote
Add to your MCP client configuration (e.g., Claude Desktop's claude_desktop_config.json):
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote"],
"env": {
"WP_API_URL": "https://your-wordpress-site.com"
}
}
}
}
You can add custom headers to all API requests using the CUSTOM_HEADERS environment variable. This is useful for API keys, custom authentication, or other header requirements.
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote"],
"env": {
"WP_API_URL": "https://your-wordpress-site.com",
"CUSTOM_HEADERS": "{"X-MCP-API-Key": "*Ibo7tweixlbfuwaiufxgakjyefctwajcetb*", "X-Custom-Header": "value"}"
}
}
}
}
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote"],
"env": {
"WP_API_URL": "https://your-wordpress-site.com",
"CUSTOM_HEADERS": "X-MCP-API-Key:IOskncfyes78U8on3q7ry43o487tybrc,X-Custom-Header:value"
}
}
}
}
CUSTOM_HEADERS='{"X-MCP-API-Key": "wc_mcp_FaQduhQcW0mfVaZgP3yaaqDuXaZ3mw7j"}' \
WP_API_URL="https://your-site.com" \
npx @automattic/mcp-wordpress-remote
Custom headers are included in:
JWT_TOKEN environment variableWP_API_USERNAME and WP_API_PASSWORDYou need to install the wordpress-mcp plugin on your WordPress website and enable MCP Functionality in Settings > MCP Settings.
OAuth 2.1 provides the most secure and user-friendly experience with full MCP Authorization specification compliance.
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote"],
"env": {
"WP_API_URL": "https://your-wordpress-site.com",
"OAUTH_ENABLED": "true"
}
}
}
}
MCP Authorization Specification Features:
Benefits:
For server-to-server authentication or when OAuth is not available.
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote"],
"env": {
"WP_API_URL": "https://your-wordpress-site.com",
"JWT_TOKEN": "your-jwt-token-here"
}
}
}
}
Uses WordPress username and application password for basic authentication.
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote"],
"env": {
"WP_API_URL": "https://your-wordpress-site.com",
"WP_API_USERNAME": "your-username",
"WP_API_PASSWORD": "your-application-password",
"OAUTH_ENABLED": "false"
}
}
}
}
To create an application password:
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote"],
"env": {
"WP_API_URL": "https://your-wordpress-site.com",
"OAUTH_CALLBACK_PORT": "7665",
"OAUTH_HOST": "127.0.0.1",
"WP_OAUTH_CLIENT_ID": "your-custom-client-id"
}
}
}
}
For WooCommerce-specific tools and reports:
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["-y", "@automattic/mcp-wordpress-remote"],
"env": {
"WP_API_URL": "https://your-wordpress-site.com",
"WOO_CUSTOMER_KEY": "ck_your-consumer-key",
"WOO_CUSTOMER_SECRET": "cs_your-consumer-secret"
}
}
}
}
| Variable | Description | Default | Required |
|---|---|---|---|
WP_API_URL | WordPress site URL | - | ✅ |
OAUTH_ENABLED | Enable OAuth authentication | true | - |
OAUTH_CALLBACK_PORT | OAuth callback port | 7665 | - |
OAUTH_HOST | OAuth callback hostname | 127.0.0.1 | - |
WP_OAUTH_CLIENT_ID | Custom OAuth client ID | - | - |
| OAuth Endpoints | |||
OAUTH_AUTHORIZE_ENDPOINT | OAuth authorization endpoint | - | ✅ (for custom OAuth) |
OAUTH_TOKEN_ENDPOINT | OAuth token endpoint | - | ✅ (for custom OAuth) |
OAUTH_AUTHENTICATE_ENDPOINT | OAuth authenticate endpoint | - | - |
| MCP OAuth 2.1 Settings | |||
OAUTH_FLOW_TYPE | OAuth flow type (authorization_code or implicit) | authorization_code | - |
OAUTH_USE_PKCE | Use PKCE (required for OAuth 2.1) | true | - |
OAUTH_DYNAMIC_REGISTRATION | Enable dynamic client registration | true | - |
OAUTH_RESOURCE_INDICATOR | Use resource indicators (RFC 8707) | true | - |
| Configuration | |||
WP_MCP_CONFIG_DIR | Config directory override | ~/.mcp-auth | - |
LOG_FILE | Log file path | - | - |
LOG_LEVEL | Log level (0-3) | 2 | - |
| Legacy Authentication | |||
JWT_TOKEN | JWT token for authentication | - | - |
WP_API_USERNAME | WordPress username (legacy) | - | - |
WP_API_PASSWORD | WordPress app password (legacy) | - | - |
WOO_CUSTOMER_KEY | WooCommerce consumer key | - | - |
WOO_CUSTOMER_SECRET | WooCommerce consumer secret |
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.