Cursor · Claude Code · Grok
Same URL. Bearer key.
These clients do not open the sign-in browser. They send Authorization: Bearer wpa_live_…. Mint the key once in Account → Connect. ChatGPT is the other path: Developer mode, then sign in.
The URL
https://wpadapter.com/mcp
Include the word Bearer. A key that starts with wpa_site_ belongs in WordPress, not here. A WordPress application password is never used on the cloud path.
Cursor
Put this in mcp.json (Cursor Settings → MCP).
{
"mcpServers": {
"wp-adapter": {
"url": "https://wpadapter.com/mcp",
"headers": {
"Authorization": "Bearer wpa_live_YOUR_KEY"
}
}
}
}
Claude Code
claude mcp add --transport http wp-adapter https://wpadapter.com/mcp \ --header "Authorization: Bearer wpa_live_YOUR_KEY"
Grok, Depaza
Depaza.eu uses the same URL. Grok: URL https://wpadapter.com/mcp, header Authorization = Bearer wpa_live_…. ChatGPT is its own chapter — OAuth first, Bearer only if ChatGPT asks for a token.
After it connects
- Ask
list-sites. You should see every WordPress you paired, unless this is a client key (one site). - More than one site: pass
site_idon later calls. Keys and site_id. - Editor: “Patch the homepage H1. Keep draft.” Forms: “Make a waitlist. Keep it draft.”
Lost the key? Mint another on Account → Connect. The old one still works until you revoke it.