# How to connect Sanity to OpenClaw (paste one key, 21 tools) > Connect Sanity to OpenClaw with ClawLink: paste your Sanity key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/sanity The usual route to Sanity 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 Sanity setup: install one ClawHub skill, connect Sanity in the browser, and OpenClaw can call real Sanity 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 Sanity. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Sanity** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect sanity # connect Sanity (browser OAuth) npx -y @useclawlink/cli actions sanity # list available actions npx -y @useclawlink/cli run sanity --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Sanity in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Sanity API key once. Verify the connection by asking OpenClaw: > Create it in Sanity for me, then confirm the important fields before you finish. ### 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Sanity is connected in the dashboard, that agent calls the same 21 Sanity tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Sanity MCP for OpenClaw Looking for a Sanity MCP server for OpenClaw? ClawLink connects Sanity to OpenClaw and exposes 21 Sanity tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Sanity integration](https://claw-link.dev/hermes/sanity) works the same way. ## What the OpenClaw Sanity integration can do 21 Sanity tools are ready for OpenClaw once the account is connected. The 17 below are the ones people reach for most; your agent can call all 21. ### 17 of 21 Sanity tools for OpenClaw | Tool | What it does | |---|---| | **Create prompt post** `sanity_create_prompt_post` | Send a one-shot prompt to the Sanity Content Agent | | **Get document** `sanity_get_document` | Fetch a single document by its ID from Sanity | | **Get invite by token** `sanity_get_invite_by_token` | Retrieve an invite by its public token | | **Get org role** `sanity_get_org_role` | Retrieve a specific organization role by its ID | | **Get permission** `sanity_get_permission` | Get a permission for a specific resource | | **Get project** `sanity_get_project` | Retrieve full details for a specific Sanity project by its ID | | **Get robots** `sanity_get_robots` | Get robots with access to a resource | | **Get role** `sanity_get_role` | Retrieve a specific role for a given resource type and resource ID | | **Get users** `sanity_get_users` | List all users of a resource and their assigned roles | | **List org roles** `sanity_list_org_roles` | List all roles available for an organization | | **List user attributes** `sanity_list_user_attributes` | Retrieve user attributes from a Sanity organization | | **Query all screening** `sanity_query_all_screening` | Execute a GROQ query to fetch all screening documents from Sanity | | **Query documents** `sanity_query_documents` | Execute an arbitrary GROQ query against a Sanity dataset | | **Validate credential** `sanity_validate_credential` | Validate Sanity API credentials by fetching the authenticated user's information | | **Add default role to users** `sanity_add_default_role_to_users` | Apply organization default role to all users | | **Create attr definition** `sanity_create_attr_definition` | Create a new user attribute definition in Sanity | | **Update org acl** `sanity_update_org_acl` | Assign a role to a member in a Sanity organization | ## Example prompts **Create Prompt Post** > Create it in Sanity for me, then confirm the important fields before you finish. **Get Document** > Pull the relevant data from Sanity, summarize it in plain English, and point out anything that needs attention. **Get Invite By Token** > Pull the relevant data from Sanity, summarize it in plain English, and point out anything that needs attention. **Get Org Role** > Pull the relevant data from Sanity, 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 Sanity working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Sanity API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Sanity 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 Sanity. | 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 Sanity actions to the runtime in a format your agent can reliably use. | 21 tools for Sanity are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Sanity 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 Sanity in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the Sanity key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Sanity skill but can't call the tools The ClawHub skill teaches OpenClaw about Sanity, but the calls run through the ClawLink plugin and your connected account. Make sure Sanity 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 Sanity 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 Sanity tools Sanity 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 Sanity 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. ### Sanity 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 Sanity has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Sanity integration? Yes. ClawLink is the fastest way to connect OpenClaw to Sanity: link your Sanity account once in the browser and OpenClaw can call the Sanity API through 21 ready-made tools — no custom code or token handling. ### How do I add Sanity to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Sanity skill from ClawHub, then you click Connect in the dashboard to authorize Sanity. OpenClaw calls the tools from the next message — no config files, and the Sanity key you paste is stored server-side instead of in your environment. ### How long does it take to connect Sanity to OpenClaw? About two minutes. Sign in, click Connect next to Sanity in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Sanity 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 Sanity working from chat. ### OpenClaw installed the Sanity skill but can't call the tools The ClawHub skill teaches OpenClaw about Sanity, but the calls run through the ClawLink plugin and your connected account. Make sure Sanity 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 tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — 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.