에이전트 강화
게시자의 자체 명령입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
npx -y @automattic/[email protected]Claude Code에는 로컬 명령용 설치 링크가 없습니다. 아래 명령을 복사해 터미널에서 실행합니다.
claude mcp add automattic-mcp-wordpress-remote -- npx -y @automattic/mcp-wordpress-remote@0.5.5터미널에서 실행합니다.
{ "mcpServers": { "automattic-mcp-wordpress-remote": { "command": "npx", "args": [ "-y", "@automattic/[email protected]" ] } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행게시자 제공
A stdio-to-HTTP pass-through proxy for WordPress MCP servers
Connect AI assistants like Claude Desktop to your WordPress sites with multiple authentication methods including OAuth 2.0, JWT tokens, and application passwords.
MCP WordPress Remote proxy server
If your MCP client supports the Streamable HTTP transport and can authenticate to your site, connect it to the MCP Adapter endpoint directly. You don't need this proxy. For example, in Claude Code (.mcp.json), using an application password:
{
"mcpServers": {
"wordpress": {
"type": "http",
"url": "https://your-wordpress-site.com/wp-json/mcp/mcp-adapter-default-server",
"headers": {
"Authorization": "Basic <base64 of username:application-password>"
}
}
}
}
Other clients use their own config format. Check your client's documentation for remote or HTTP MCP servers.
Use the proxy when one of these applies:
SOCKS_PROXY, HTTPS_PROXY, ALL_PROXY or HTTP_PROXY to route requests through it. On macOS, set USE_SYSTEM_PROXY=true to use the system PAC file or SOCKS proxy instead.WP_API_TIMEOUT_MS and WP_API_INIT_TIMEOUT_MS set the timeouts, and a failed initialize returns a degraded response instead of a broken connection (see Forwarding behavior).LOG_FILE with LOG_LEVEL=3 logs each forwarded method plus connection and authentication events (see Log Analysis)./lib bundle can send extra requests over the proxy's authenticated connection, for example for usage telemetry.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/wp-json/mcp/mcp-adapter-default-server"
}
}
}
}
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/wp-json/mcp/mcp-adapter-default-server",
"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/wp-json/mcp/mcp-adapter-default-server",
"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/wp-json/mcp/mcp-adapter-default-server" \
npx @automattic/mcp-wordpress-remote
Custom headers are included in:
OAUTH_ENABLED=true to open the browser for authorizationJWT_TOKEN environment variableWP_API_USERNAME and WP_API_PASSWORDInstall the MCP Adapter plugin on your WordPress site. Once active, it registers a default MCP server at /wp-json/mcp/mcp-adapter-default-server — set WP_API_URL to that full URL (examples throughout this README show the pattern). To target a custom server id or namespace, pass the full URL of that server instead.
The proxy forwards the MCP client's messages to the configured endpoint and returns the server's messages. It does not send its own initialization probe, select an MCP version, or register a fixed set of methods. The client and server own version negotiation, capabilities, and result validation. Requests, notifications, server requests, IDs, and metadata travel through the bridge; JSON and SSE responses are supported.
For initialization-based MCP connections, the server's selected version and session ID are used in subsequent HTTP headers. Requests carrying io.modelcontextprotocol/protocolVersion in params._meta use that version directly and do not require a proxy-generated handshake. This removes the proxy's version allowlist; it does not translate between protocol revisions or establish full compliance with every newer transport feature.
Existing authentication, custom headers, timeout, logging, token-storage, and system-proxy settings remain available. A bare-domain WP_API_URL now resolves to /?rest_route=/mcp/mcp-adapter-default-server. Full endpoint URLs remain configurable. The archived wordpress-mcp plugin's method-only request format and automatic transport fallback have been removed.
If the upstream connection fails during initialization, the proxy retains its degraded response with experimental.connectionFailed and no usable capabilities, using the client's offered version. Follow-up requests are rejected locally. Server-generated JSON-RPC errors are forwarded rather than converted to a successful handshake. The proxy does not silently reinitialize or retry failed client requests.
Tool-call hooks and wpRequest from the /lib bundle share the live authenticated connection when the proxy is running. Hook responses remain internal and hook failures cannot change the client response. Standalone wpRequest retains its result-returning interface and optional session recovery; both its existing argument shapes are encoded as standard JSON-RPC.
OAuth 2.1 uses a public native client with PKCE S256, validated MCP discovery, and coordinated token renewal. See OAuth client behavior for the supported profile, migration behavior, and optional features.
{
"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",
"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/wp-json/mcp/mcp-adapter-default-server",
"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-json/mcp/mcp-adapter-default-server",
"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/wp-json/mcp/mcp-adapter-default-server",
"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/wp-json/mcp/mcp-adapter-default-server",
"WOO_CUSTOMER_KEY": "ck_your-consumer-key",
"WOO_CUSTOMER_SECRET": "cs_your-consumer-secret"
}
}
}
}
To use only JWT or Basic Auth:
{
"env": {
"OAUTH_ENABLED": "false",
"JWT_TOKEN": "your-jwt-token"
}
}
For development and testing, you can use the local repository:
Clone the repository:
git clone https://github.com/Automattic/mcp-wordpress-remote.git
cd mcp-wordpress-remote
Install dependencies:
npm install
Build the project:
npm run build
Configure your MCP client to use the local version:
{
"mcpServers": {
"wordpress": {
"command": "node",
"args": ["/path/to/your/mcp-wordpress-remote/dist/proxy.js"],
"env": {
"WP_API_URL": "https://your-wordpress-site.com/wp-json/mcp/mcp-adapter-default-server"
}
}
}
}
npm run build:watch - Automatically rebuilds on file changesnpm test - Run the test suitenpm run check - Run TypeScript and Prettier checksTokens are automatically stored in:
~/.mcp-auth/wordpress-remote-{version}/
# View stored tokens
ls -la ~/.mcp-auth/wordpress-remote-*/
# Clear all tokens (forces re-authentication)
rm -rf ~/.mcp-auth/wordpress-remote-*/
# Clear tokens for specific version
rm -rf ~/.mcp-auth/wordpress-remote-0.2.1/
The proxy automatically coordinates between multiple instances:
If you see "waiting for other instance" messages, this is normal behavior.
OAuth browser doesn't open:
OAUTH_CALLBACK_PORTOAuth authorization fails:
JWT authentication fails:
Basic Auth fails:
API endpoint not found:
WP_API_URL points at the server route (e.g. …/wp-json/mcp/mcp-adapter-default-server)Permission denied:
If port 3000 is already in use:
{
"env": {
"OAUTH_CALLBACK_PORT": "8080"
}
}
"Waiting for other instance" messages are normal when multiple MCP clients start simultaneously. The system coordinates authentication to prevent conflicts.
Enable detailed logging:
{
"env": {
"LOG_LEVEL": "3",
"LOG_FILE": "/path/to/logfile.log"
}
}
Log levels:
0 - Errors only1 - Warnings and errors2 - Info, warnings, and errors (default)3 - Debug, info, warnings, and errorsGPL v2 or later
Contributions welcome! This project is maintained by Automattic Inc.
Need help? Check the troubleshooting section or open an issue.
{ "mcpServers": { "automattic-mcp-wordpress-remote": { "command": "npx", "args": [ "-y", "@automattic/[email protected]" ] } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
@automattic/mcp Wordpress Remote은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-11-15. MCP WordPress Remote proxy server