@automattic/mcp-wordpress-remote
It exited or refused to answer until it is given configuration, such as a key or an argument. Run 2026-11-16.
Needs to start: WP_API_PASSWORD, WP_OAUTH_CLIENT_ID, WP_API_URL +2
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @automattic/mcp-wordpress-remote@0.5.5
Installing a package runs its code. Use a sandbox for anything you have not read.
Its error output names these settings: WP_API_PASSWORD, WP_OAUTH_CLIENT_ID, WP_API_URL, JWT_TOKEN, WP_API_USERNAME.
What it said when it did not start
ME=username and WP_API_PASSWORD=app_password (for application passwords)\n • Set OAUTH_ENABLED=true and WP_OAUTH_CLIENT_ID=your_client_id (for OAuth 2.1)\n • CUSTOM_HEADERS='{\"X-API-Key\": \"your_api_key\"}' (for custom header authentication), WP_API_URL must be set to your WordPress site URL. Example: WP_API_URL=https://yoursite.com",
"stack": "APIError: Configuration validation failed: No authentication method configured. Please set one of: JWT_TOKEN, WP_API_USERNAME+WP_API_PASSWORD, enable OAuth, or set CUSTOM_HEADERS. Configure one of these options:\n • JWT_TOKEN=your_jwt_token (preferred for APIs)\n • WP_API_USERNAME=username and WP_API_PASSWORD=app_password (for application passwords)\n • Set OAUTH_ENABLED=true and WP_OAUTH_CLIENT_ID=your_client_id (for OAuth 2.1)\n • CUSTOM_HEADERS='{\"X-API-Key\": \"your_api_key\"}' (for custom header authentication), WP_API_URL must be set to your WordPress site URL. Example: WP_API_URL=https://yoursite.com\n at failure (file:///app/node_modules/@automattic/mcp-wordpress-remote/dist/proxy.js:80124:64)\n at send (file:///app/node_modules/@automattic/mcp-wordpress-remote/dist/proxy.js:80259:13)\n at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n at async StreamableHTTPClientTransport.send (file:///app/node_modules/@automattic/mcp-wordpress-remote/dist/proxy.js:77510:24)\n at async send (file:///app/node_modules/@automattic/mcp-wordpress-remote/dist/proxy.js:80417:7)",
"statusCode": 0,
"endpoint": "https://example.com/?rest_route=/mcp/mcp-adapter-default-server"
}
Written by the package or by npm, not by this site.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18.0.0 |
| Source | github.com/Automattic/mcp-wordpress-remote |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-dHQIzEldCPtBEoIVh1nrsUOKQGjiOu8qnGjkPYFW6ZqfyYNzUxb2d3Sbe9nnljnZh74qQSwfCIWzqhphKZQASA== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40automattic/mcp-wordpress-remote)
New version out? Ask for a fresh report.