MCP Context A8C
MCP server for ContextA8C.
Installation
npm install @automattic/mcp-context-a8c
Usage
Claude Code
Add to your MCP configuration:
{
"mcpServers": {
"context-a8c": {
"command": "npx",
"args": ["@automattic/mcp-context-a8c"]
}
}
}
Direct execution
npx @automattic/mcp-context-a8c
Features
- OAuth 2.1: WordPress.com authorization code with PKCE, automatic client registration, and refresh-token recovery
- System proxy support: Automatically detects and uses system proxy (PAC file on macOS, env vars on Linux)
Proxy Support
This package enables system proxy detection by default (USE_SYSTEM_PROXY=true).
Environment Variables
All settings can be overridden via environment variables:
| Variable | Default | Description |
|---|---|---|
WP_API_URL | Context A8C endpoint | API endpoint URL |
OAUTH_ENABLED | true | Enable OAuth authentication |
OAUTH_CALLBACK_PORT | automatic | Override the local callback port |
OAUTH_TIMEOUT_MS | 300000 | Time allowed to complete browser authorization |
USE_SYSTEM_PROXY | true | Enable system proxy detection |
Upgrading from 0.4.x requires one fresh sign-in because the upstream credential directory is versioned. Concurrent processes share authorization and refresh tokens through the upstream OAuth lock.
Proxy-route changes and expired MCP sessions may require reconnecting your MCP client. The wrapper forwards upstream failures to the client rather than replaying requests.
Implementation Notes
This package is a thin wrapper around @automattic/mcp-wordpress-remote. It sets Automattic-specific environment defaults before delegating to the base MCP server.
See the mcp-wordpress-remote documentation for additional configuration options and details.
The upstream package is consumed as published; the wrapper does not rewrite dependency bundles. npm run build verifies fragmented HTTP chunk endings in the built executable. npm test builds first and runs the wrapper and heartbeat regressions.