Give Claude, Codex, Cursor, and any MCP-compatible AI assistant secure, direct access to your GrapheneDB account and databases.

GrapheneDB ships a hosted MCP (Model Context Protocol) server, so any MCP-compatible AI client can act on your account directly — no context switching to the Console.
It works today with Claude, Codex, and Cursor, and any other client that speaks MCP. Point it at https://console.graphenedb.com/mcp, sign in with your GrapheneDB account, and you're connected — see the full setup guide for exact steps per client.
Ask about a database the way you'd ask a teammate. CPU and memory metrics, deployment logs, query logs, and account-wide activity history are all available as tools your assistant can call directly.
No dashboard to open first — describe the symptom, and your assistant pulls the right metrics and logs to confirm what's actually going on.
Link a database once from its Connect page in the Console, and your assistant can run Cypher directly against it — including PROFILE, to see exactly how a query executes before you act on its suggestions.
GrapheneDB never stores your database credentials. The link only lasts as long as the Console tab stays open, and you can revoke it at any time.
Every tool call runs with the permissions of whichever GrapheneDB user or database credentials you authenticate with — nothing more.
Account-level tools are scoped to what your GrapheneDB user can already see in the Console, and database access ends the moment you unlink it.

