Connect Claude Code and Cursor to WordPress

• A WordPress site with AlphaBridge. WordPress 6.5 and PHP 8.0 or newer. The free plugin is enough to start.
• An administrator account. You create the connection under Settings → AlphaBridge MCP.
• Claude Code or Cursor. Claude Code connects to the endpoint directly. Cursor runs the ready-made config, which needs Node.js 18 or newer.

For Claude Code, put the Endpoint URL and the Bearer token from the plugin into this command.

claude mcp add --transport http alphabridge https://your-site.tld/wp-json/alphabridge/v1/mcp --header "Authorization: Bearer YOUR-TOKEN"

Claude Code then talks to your endpoint directly over HTTP, without Node.js.

For Cursor, the plugin shows a ready-made config. It looks like this.

{
  "mcpServers": {
    "alphabridge": {
      "command": "npx",
      "args": ["mcp-remote", "https://your-site.tld/wp-json/alphabridge/v1/mcp", "--header", "Authorization:${AUTH}"],
      "env": { "AUTH": "Bearer YOUR-TOKEN" }
    }
  }
}

In Cursor, npx starts the helper mcp-remote. It sends each request to your endpoint, with your token in the Authorization header.

Leave Authorization:${AUTH} as it is. The token sits in the env line, after the word Bearer.

For a second site, create a connection there too. Add it under another name, such as alphabridge-shop.

• The token is shown in full only once. The site keeps only a hash of it.
• Lost it? Rotate the connection under Your connections. The old token stops working at once.
• Choose the access level “read only” or “content only” when a client should not do everything.
• Set an expiry in days for access that is meant to end.
• Claude Code keeps a server added with claude mcp add in ~/.claude.json, for this project and only for you.
• Every request runs with the rights of the WordPress user the connection acts as.
• Write access holds for every connection on the site, this one included. Changes then take effect immediately and can be destructive. Switching it on is at the owner's own risk.

The first three only read. The fourth needs write access. The fifth needs Pro and write access. The last needs Agency, Site Deploy set up and write access.

Any MCP client that speaks Streamable HTTP and can send a header can use the endpoint directly. Send the token with every request as Authorization: Bearer ….

If a client strips the Authorization header, send the token as X-Api-Key instead.

Claude on the web, in Desktop and on iOS connects without a token. You approve on your site instead, as the connector page shows.