Sanaf AI
Start free
Developer Tools

Grafbase, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Grafbase account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Connects with a key
  • 19 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Grafbase is

Grafbase is a platform that accelerates the development of GraphQL APIs, offering features like edge caching, unified data access, and seamless integration with popular authentication strategies.

You paste in a key from your own Grafbase account. It is kept encrypted, and you can withdraw it from inside Grafbase whenever you like.

How a run works

One message in, the work done in Grafbase.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Grafbase. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Grafbase account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

19 tools it already has

What it can do in Grafbase

These are the ready-made tools your AI employee already has in Grafbase. It is not limited to them, but it never has to be taught these.

  • Delete ExtensionTool to delete an extension configuration. Use after confirming the extensionid to remove the extension.
  • Delete Grafbase API KeyTool to delete an existing API key. Use after confirming the key ID to revoke access.
  • Delete Grafbase Audit LogTool to delete a specific Grafbase audit log entry. Note: As of current Grafbase public documentation, there is no documented API to delete audit logs programmatically. This action
  • Delete Grafbase SchemaTool to delete a Grafbase schema. Use when you need to remove a specific schema from the registry after confirming its ID.
  • Delete MCP ServerTool to delete a Grafbase MCP server configuration by its unique ID. Use after confirming the server ID to remove an existing MCP server.
  • Delete Schema CheckTool to delete a Grafbase schema check. Use when you need to remove a specific schema check by its ID after reviewing the registry.
  • Disable MCP serverTool to disable the Model Context Protocol server. Use when you need to turn off MCP via API after it has been enabled.
  • Enable Grafbase MCP ServerTool to enable the Model Context Protocol (MCP) server for a Grafbase project. Use when you need to activate MCP support; if the API endpoint is not supported, this returns guidanc
  • Get Federated SchemaTool to retrieve the composed federated graph schema. Use after deploying your federated graph when you need the full SDL.
  • Get Grafbase Audit LogTool to retrieve a specific Grafbase audit log entry. Use after confirming the audit log ID exists.
  • Get Grafbase Schema CheckTool to retrieve the result of a schema check by its ID. Use when you need to inspect a specific schema check after running a check via CLI or API.
  • Get Subgraph SchemaTool to retrieve the GraphQL SDL of a specific subgraph. Use after confirming the subgraph name to inspect its schema.
  • List API KeysTool to list all API keys for a project. Use after authenticating with a valid token to retrieve the project’s API keys.
  • List ExtensionsTool to list all extensions configured for a Grafbase project. Use after confirming project access when retrieving configured extensions programmatically.
  • List Grafbase Audit LogsTool to list all audit logs for a project. Use when you need to retrieve historical events (up to 90 days). Note: As of current Grafbase public documentation, there is no documente
  • List Grafbase Schema ChecksTool to list all Grafbase schema checks for a project. Use when you need to review past schema validation runs.
  • List Grafbase SchemasTool to list all Grafbase schemas. Use when you need to retrieve all schemas in the registry.
  • List Grafbase SubgraphsTool to list published subgraphs in a branch. Use when you need to retrieve endpoints of all subgraphs for a given branch.
  • List MCP ServersTool to list all MCP servers configured for a project. Use when you need to retrieve existing MCP server configurations.
Access, and who is in charge of it

You stay the boss of your Grafbase account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Grafbase account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Grafbase is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Grafbase and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Grafbase

Can an AI employee really work inside Grafbase?
Yes. It signs in to your own Grafbase account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Grafbase?
No. Nothing moves and nothing is replaced. Your records stay in Grafbase, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Grafbase account?
You paste in a key from your own Grafbase account. It is kept encrypted, and you can withdraw it from inside Grafbase whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Grafbase?
It has 19 ready-made tools in Grafbase today, among them Delete Extension, Delete Grafbase API Key and Delete Grafbase Audit Log. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Grafbase and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Grafbase and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Grafbase?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Grafbase is written down with what it did and when.