Grafbase for AI agents
Grafbase helps teams build and manage GraphQL APIs with edge caching, unified data access, and federated schemas. Engineering teams pull it into internal tools and scripts rather than building the same capability themselves. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Grafbase.
Check a subgraph's schema
Pull a subgraph's current schema before proposing a change to a federated GraphQL API.
Review recent schema checks
List recent schema checks to see whether a proposed change would break existing queries.
Delete an API key with confirmation
Delete an old API key only after a team admin confirms it is no longer in use.
28 Grafbase actions, graded by risk.
Every Grafbase action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
15Look things up. Allowed by default.
- grafbase.list_schemasList Grafbase Schemas
- grafbase.get_audit_logGet Grafbase Audit Log
- grafbase.list_api_keysList API Keys
- grafbase.get_invitationGet Grafbase Invitation
- grafbase.list_subgraphsList Grafbase Subgraphs
- grafbase.list_audit_logsList Grafbase Audit Logs
- grafbase.list_extensionsList Extensions
- grafbase.get_schema_checkGet Grafbase Schema Check
- grafbase.list_mcp_serversList MCP Servers
- grafbase.list_schema_checksList Grafbase Schema Checks
- grafbase.get_subgraph_schemaGet Subgraph Schema
- grafbase.get_federated_schemaGet Federated Schema
- grafbase.get_extension_by_nameGet Extension by Name
- grafbase.get_notifications_inbox_messagesGet Notifications Inbox Messages
- grafbase.get_extension_version_by_name_and_versionGet Extension Version By Name And Version
write
4Create and change things. Allow, or ask the user first.
- grafbase.add_zitadel_redirectAdd Zitadel Redirect URI
- grafbase.enable_mcpEnable Grafbase MCP Server
- grafbase.assign_team_roleAssign Team Role
- grafbase.mark_notifications_as_readMark Notifications as Read
destructive
9Delete, cancel or archive. Ask first, or deny outright.
- grafbase.delete_teamDelete Grafbase Team
- grafbase.delete_schemaDelete Grafbase Subgraph
- grafbase.delete_api_keyDelete Grafbase API Key
- grafbase.delete_audit_logDelete Grafbase Audit Log
- grafbase.delete_extensionDelete Extension
- grafbase.delete_mcp_serverDelete MCP Server
- grafbase.remove_graph_ownerRemove Graph Owner
- grafbase.delete_schema_checkDelete Schema Check
- grafbase.disable_mcpDisable MCP Server
Grafbase in three steps.
- 01Your users connect GrafbaseThey add their Grafbase api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “add Zitadel Redirect URI” can wait for the user, and “delete Grafbase Team” can be denied outright.
- 03Any agent can actYour agent calls Grafbase through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('grafbase', { read: 'allow', write: 'ask', // add_zitadel_redirect destructive: 'deny', // delete_team }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Grafbase connects.
Users add their Grafbase api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Grafbase connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Grafbase from any agent.
Grafbase and Arc0, answered.
Can I use Grafbase with Claude, ChatGPT or Cursor?
Yes. Connect Grafbase to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Grafbase actions you allow.
How do users connect Grafbase?
Users add their Grafbase api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Grafbase actions can my agent take?
28 in total: 15 read, 4 write and 9 destructive, such as “add Zitadel Redirect URI”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Grafbase?
Yes. Actions like “delete Grafbase Team” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Grafbase too?
Yes. The same Grafbase connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Grafbase into your agent.
Your users connect Grafbase once, under your brand. Your agent gets 28 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan