MCP integration
The MCP server exposes your graph, scores and recommendations as tools your agents query directly — no scraping, no bridge code.
Configuration
The server speaks Streamable HTTP at https://mcp.graphorank.com/mcp and is available on Pro plans and up. Authenticate with an API key — keys start with gr_, need the read scope, and are created in the app under API & MCP. Send the key as Authorization: Bearer (or X-Api-Key).
In Claude Code, drop this in your project's .mcp.json:
{
"mcpServers": {
"graphorank": {
"type": "http",
"url": "https://mcp.graphorank.com/mcp",
"headers": { "Authorization": "Bearer gr_..." }
}
}
}In Claude Desktop, add the server to claude_desktop_config.json through the mcp-remote bridge:
{
"mcpServers": {
"graphorank": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://mcp.graphorank.com/mcp",
"--header", "Authorization: Bearer gr_..."
]
}
}
}Supported clients
Any client that speaks the Model Context Protocol: Claude Desktop, Claude Code, Cursor, and custom agents built on the MCP SDK.
Available tools
All tools are read-only: they never start a scan or touch your data. The server also publishes the resources site://{domain}/graph and site://{domain}/report, plus an audit_geo prompt your client can invoke directly.
Plan availability
MCP access follows your plan — keys inherit the plan of the workspace that created them.