WordPress MCP 서버를 위한 stdio-to-HTTP 패스스루 프록시

Claude Desktop 같은 AI 비서를 OAuth 2.0, JWT 토큰, 애플리케이션 비밀번호 등 다양한 인증 방법으로 워드프레스 사이트에 연결하세요.

특징

• MCP OAuth 클라이언트 - 권한 코드 PKCE, 검증된 발견, 발행자 바운딩 자격 증명, 그리고 조정된 갱신
• OAuth 2.1 with PKCE - 보안 권한 코드 흐름 with PKCE (RFC 7636)
• 리소스 표시자 - 토큰 오디언스 바인딩을 위한 RFC 8707 준수
• 동적 클라이언트 등록 - RFC 7591 자동 클라이언트 등록 지원
• 보호된 자원 메타데이터 발견 - 자동 엔드포인트 탐색을 위한 RFC 9728
• 다중 인증 방법 - OAuth 2.1, JWT 토큰, WordPress 애플리케이션 비밀번호
• 영구 토큰 저장 - 자동 검증으로 안전하게 저장된 OAuth 토큰
• 다중 인스턴스 조정 - 락파일은 인증 충돌을 방지합니다
• 자동 토큰 관리 - 검증, 새로고침, 정리 처리함
• 향상된 오류 처리 - 적절한 분류가 포함된 상세한 오류 메시지
• 종합 로깅 - 카테고리와 레벨을 가진 구조화된 로깅

MCP WordPress Remote

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.

Features

• MCP OAuth Client - Authorization-code PKCE, validated discovery, issuer-bound credentials, and coordinated renewal
• OAuth 2.1 with PKCE - Secure authorization code flow with PKCE (RFC 7636)
• Resource Indicators - RFC 8707 compliance for token audience binding
• Dynamic Client Registration - RFC 7591 support for automatic client registration
• Protected Resource Metadata Discovery - RFC 9728 for automatic endpoint discovery
• Multiple Authentication Methods - OAuth 2.1, JWT tokens, and WordPress application passwords
• Persistent Token Storage - OAuth tokens stored securely with automatic validation
• Multi-instance Coordination - Lockfiles prevent authentication conflicts
• Automatic Token Management - Handles validation, refresh, and cleanup
• Enhanced Error Handling - Detailed error messages with proper categorization
• Comprehensive Logging - Structured logging with categories and levels
• Complete MCP Support - Tools, resources, prompts, and more

When to use this proxy

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 "
      }
    }
  }
}

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:

1. Your client only supports stdio. It can launch a local command but cannot connect to an HTTP MCP server.
2. Your client can’t authenticate the way your site requires. The proxy can send application passwords, JWT tokens, WooCommerce keys, or custom headers, and it can run the OAuth flow and store tokens for clients that can’t.
3. Your traffic must go through a proxy. Set 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.
4. Your site is slow or unreliable. 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).