Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Use n8n’s MCP Client node to connect to the relevant Sanity MCP endpoint, confirm that n8n can authenticate and discover its tools, then run a safe read operation and compare the result with content you already know. Sanity’s general hosted MCP server and Sanity Context MCP are separate options with different credential requirements. The steps below are a documentation-based integration pattern, not a jointly tested Sanity–n8n recipe.
Choose the right Sanity endpoint first
Sanity’s general hosted MCP server is at https://mcp.sanity.io. Sanity documents OAuth and API-token authentication for this server; the token’s role determines which tool calls it can make. See Sanity’s MCP server getting-started guide.
Sanity Context MCP is a distinct hosted service accessed through Sanity Context. Its endpoint is provided by the Context app, and it offers structured, read-only access to content allowed by its configuration. It requires an organization API token with Context Viewer permissions; a project API token is not accepted. Sanity explains setup in Configure an MCP and Context MCP.
These are not interchangeable credential contexts. Decide which service you intend to validate before configuring n8n; do not substitute a project token for Context MCP’s organization token.
Connect the endpoint with n8n’s MCP Client node
n8n’s MCP Client node consumes an external MCP server. Its documented configuration includes transport, server URL, authentication, tool selection, and input mode, and it fetches the tools exposed by the server. Consult the MCP Client node documentation for the current node settings and labels.
- Add the node. In your workflow, add an MCP Client node and configure it to connect to an external server.
- Set the transport and endpoint. Choose the transport supported by the target server and enter its endpoint URL. For the general hosted server, use
https://mcp.sanity.io. For Context MCP, use the endpoint URL shown in the Context app. - Configure authentication. Select the method required by the endpoint. n8n documents bearer authentication, generic headers, multiple headers, and OAuth2. Put secrets in n8n credentials rather than ordinary workflow text. Use the organization token with Context Viewer permissions for Context MCP; for the general server, use the authentication method and appropriately scoped token configured for your access.
- Select a tool and provide its inputs. Use the node’s available-tool and input controls after the connection is configured. The tool names and availability depend on the server and its configuration.
Exact fields can vary with transport and n8n version. Follow the current node documentation rather than assuming every MCP server uses identical settings.
Validate connectivity, permissions, and results separately
A successful node configuration is not by itself proof that the integration can access the content you need. Check each layer in order so a failure points to the right place.
- Confirm the endpoint responds. Check the node’s execution result for a connection or transport error. Make sure the URL belongs to the intended Sanity service and that the selected transport is compatible.
- Confirm authentication. A permissions failure means the connection may reach the service but the credential is missing or insufficient. For Context MCP, verify that the credential is an organization token and that it has Context Viewer permissions.
- Confirm tool discovery. Check the tools n8n reports from the server. A tool list is endpoint- and configuration-dependent; do not expect every account to expose the same tools.
- Run a low-risk read. Invoke an available read operation against the intended dataset. Compare the returned document or query result with a known document or a result obtained through your normal Sanity workflow. This comparison is a practical validation step, not a vendor guarantee.
- Check the scope of the result. Confirm that the returned content is the content your workflow is supposed to access, and that the credential does not grant broader access than required.
For Sanity Context MCP, the final check is necessarily read-only: Context MCP cannot write back. Validate write behavior through a separate, appropriately authorized integration path if your application requires it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose MCP or a webhook based on how the workflow starts
| Option | Interaction style | Access and credential notes | Useful validation |
|---|---|---|---|
| General Sanity MCP | An MCP client invokes tools on demand. | Sanity documents OAuth or API-token authentication; token role scopes tool calls. | Check connection, discovered tools, then run an appropriate read operation. |
| Sanity Context MCP | An MCP client invokes tools on demand for configured content context. | Read-only. Requires an organization token with Context Viewer permissions; project tokens are not accepted. | List tools, then verify a read result against known content. |
| Sanity document webhook | Sanity sends an HTTP request when configured content-change events occur. | Can use GROQ filters and projections, configurable HTTP methods and headers, and an optional secret hashed into request headers for origin verification. | Trigger a matching content event and verify that the receiving n8n HTTP or webhook workflow handles it as expected. |
Sanity’s Webhooks API reference describes event delivery as a separate HTTP path. Use a webhook when n8n should react to a Sanity content change; use MCP when a client should call Sanity tools as needed. A webhook is not an MCP connection or a substitute for checking MCP tool discovery.
Troubleshoot common connection failures
No tools appear
Check that the endpoint URL and transport match the selected Sanity service, then review the service’s tool configuration and the account, project, or dataset permissions involved. Sanity notes that available tools can vary, so an absent tool is not necessarily a transport failure.
Rank #4
Context MCP returns a permission error
Use the organization-level token required by Context MCP and confirm it has the Context Viewer grant. A project-level token is not accepted even if its project permissions seem broad; an absent organization grant can result in a 403.
The connection works but the read returns unexpected content
Check the target dataset, endpoint configuration, and the permissions associated with the credential. Compare the result with a known document or query result from the same intended content scope; tool discovery alone does not establish that the workflow is reading the right data.
You need n8n to verify a server independently
n8n also documents verify_agent_mcp_server, a tool that tests an MCP server using an accessible credential and returns its available tools. This is a separate n8n MCP server capability, not a Sanity-specific integration recipe. See the n8n MCP server tools reference.
What this validation does—and does not—establish
Sanity and n8n document their MCP components independently. Their documentation supports the connection pattern above, but does not establish that the exact Sanity–n8n combination has been jointly tested or guarantee a fixed tool list. Treat a successful result in your own workflow as evidence for that endpoint, credential, and configuration—not as a universal compatibility guarantee.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
