Connect MrKeyword to your AI assistant.

claude mcp add --transport http mrkeyword \
  https://app.mrkeyword.io/mcp \
  --header "Authorization: Bearer mk_your_token"

{
  "mcpServers": {
    "mrkeyword": {
      "type": "http",
      "url": "https://app.mrkeyword.io/mcp",
      "headers": { "Authorization": "Bearer mk_your_token" }
    }
  }
}

{
  "mcpServers": {
    "mrkeyword": {
      "url": "https://app.mrkeyword.io/mcp",
      "headers": { "Authorization": "Bearer mk_your_token" }
    }
  }
}

curl -s https://app.mrkeyword.io/mcp \
  -H "Authorization: Bearer mk_your_token" \
  -H "content-type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Replace mk_your_token with the token you just created. The endpoint URL is also printed beside the token when MrKeyword creates it, which is the copy to trust if you are on a different deployment.

A token without it that calls an action tool is refused with an error that names the tool and tells you to create a new token with “Allow this token to make changes” ticked — it never fails silently.

Protocol

JSON-RPC 2.0 over the Streamable HTTP transport, as a single POST to https://app.mrkeyword.io/mcp. It answers initialize, ping, tools/list, tools/call, prompts/list and prompts/get, and negotiates protocol versions 2025-06-18, 2025-03-26 and 2024-11-05. JSON-RPC batches are answered in one array. GET and DELETE return 405: there is no server-initiated SSE stream and no session to keep alive, because the server has nothing to push.

Capabilities

Exactly tools and prompts, both without listChanged. There is deliberately no resources capability, because there are no resources — declaring one would only make your client call resources/list and get an error.

Rate limit

120 calls a minute per token. Going over answers HTTP 429 with a Retry-After header and a message saying how long to wait. Separately, the tools that spend something spend it in the product, not at the protocol: start_site_audit uses audit pages and track_keywords uses tracked-keyword slots. Your plan sets those allowances.

Errors

A missing, revoked or expired token answers HTTP 401 with JSON-RPC -32001 and a WWW-Authenticate header. An unsupported method answers -32601; a bad argument, an unknown tool or a refused scope answers -32602. A tool that fails for an ordinary reason — no crawl yet, keyword not tracked — comes back as a normal MCP tool error with the reason in it, so your assistant can correct itself instead of treating it as a transport fault.

What the answers carry

Every payload includes an as_of date, so stale data is visible rather than implied to be current, and each figure says where it came from. The server's own initialize instructions tell your assistant the same things this website does: positions are period averages from the connected property and never live SERP ranks, and search volume comes only from research_keyword and bulk_keyword_check, fetched live from Google Keyword Planner and paid for with lookup credits, while difficulty and intent are MrKeyword estimates.

The same token works for the REST API

The workspace endpoints under /api accept the same Authorization: Bearer mk_… header, so a script that already speaks HTTP does not need an MCP client at all.

Data handling

Provider refresh tokens are encrypted at rest and are never returned by any tool. Crawled page content is escaped before it is rendered anywhere. The full picture is on the security page.