How to connect Grafbase to OpenClaw
Connect Grafbase to OpenClaw with ClawLink: paste your Grafbase key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine.
GrafbaseAPI KEYMCPGrafbase 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.. Once connected, OpenClaw can read and act on Grafbase from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Grafbase access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Grafbase setup: install one ClawHub skill, connect Grafbase in the browser, and OpenClaw can call real Grafbase actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Grafbase.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Grafbase
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Grafbase?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Grafbase in the ClawLink dashboard — paste your Grafbase API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Grafbase, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Grafbase is connected in the dashboard, that agent calls the same 28 Grafbase tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Grafbase MCP for OpenClaw
Looking for a Grafbase MCP server for OpenClaw? ClawLink connects Grafbase to OpenClaw and exposes 28 Grafbase tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Grafbase integration works the same way.
What the OpenClaw Grafbase integration can do
28 Grafbase tools are ready for OpenClaw once the account is connected. The 21 below are the ones people reach for most; your agent can call all 28.
21 of 28 Grafbase tools for OpenClaw
| Tool | What it does |
|---|---|
Get audit log grafbase_get_audit_log | Retrieve a specific Grafbase audit log entry by searching organization activity |
Get extension by name grafbase_get_extension_by_name | Retrieve a Grafbase extension by its name |
Get extension version by name and version grafbase_get_extension_version_by_name_and_version | Retrieve details of a specific Grafbase extension version by name and version |
Get federated schema grafbase_get_federated_schema | Retrieves the composed federated graph schema from Grafbase in SDL format |
Get invitation grafbase_get_invitation | Retrieve details about a specific Grafbase invitation by ID |
Get notifications inbox messages grafbase_get_notifications_inbox_messages | Retrieve notifications inbox messages for the authenticated Grafbase user |
Get schema check grafbase_get_schema_check | Retrieve details of a specific schema check by its ID |
Get subgraph schema grafbase_get_subgraph_schema | Retrieves the GraphQL SDL schema for a specific subgraph by name |
List API keys grafbase_list_api_keys | List all API keys (access tokens) for the authenticated Grafbase user |
List audit logs grafbase_list_audit_logs | List audit logs for Grafbase organizations |
List extensions grafbase_list_extensions | List all extensions configured for a Grafbase project |
List mcp servers grafbase_list_mcp_servers | Check MCP server configuration status for a Grafbase gateway |
List schema checks grafbase_list_schema_checks | List schema checks for a Grafbase graph |
List schemas grafbase_list_schemas | List all schemas in the Grafbase schema registry |
List subgraphs grafbase_list_subgraphs | List published subgraphs in your Grafbase federated graphs |
Add zitadel redirect grafbase_add_zitadel_redirect | Add a redirect URI to Zitadel OAuth configuration in Grafbase |
Assign team role grafbase_assign_team_role | Assign a role to a team member in Grafbase |
Enable mcp grafbase_enable_mcp | Enable the Model Context Protocol (MCP) server on a Grafbase gateway |
Mark notifications as read grafbase_mark_notifications_as_read | Mark Grafbase notifications as read |
Disable mcp grafbase_disable_mcp | Disable the Model Context Protocol (MCP) server for a Grafbase project |
Remove graph owner grafbase_remove_graph_owner | Remove an owner from a Grafbase graph |
Try it: find the Grafbase tool you need
Browse the 21 Grafbase tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Grafbase, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Grafbase, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Grafbase, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Grafbase, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Grafbase working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Grafbase API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Grafbase account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Grafbase. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Grafbase actions to the runtime in a format your agent can reliably use. | 28 tools for Grafbase are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Grafbase to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Grafbase in the browser, and the 28 tools above work from chat. There is no SDK and no config file, and the Grafbase key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Grafbase skill but can't call the tools
The ClawHub skill teaches OpenClaw about Grafbase, but the calls run through the ClawLink plugin and your connected account. Make sure Grafbase is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Grafbase from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Grafbase tools
Grafbase tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Grafbase call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Grafbase returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Grafbase has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Grafbase integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Grafbase: link your Grafbase account once in the browser and OpenClaw can call the Grafbase API through 28 ready-made tools — no custom code or token handling.
How do I add Grafbase to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Grafbase skill from ClawHub, then you click Connect in the dashboard to authorize Grafbase. OpenClaw calls the tools from the next message — no config files, and the Grafbase key you paste is stored server-side instead of in your environment.
How long does it take to connect Grafbase to OpenClaw?
About two minutes. Sign in, click Connect next to Grafbase in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Grafbase up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Grafbase working from chat.
OpenClaw installed the Grafbase skill but can't call the tools
The ClawHub skill teaches OpenClaw about Grafbase, but the calls run through the ClawLink plugin and your connected account. Make sure Grafbase is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
GitHub
Manage repositories, issues, pull requests, and workflows
OpenClaw PagerDuty integration
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.