sanity

This MCP server is provided as a hosted remote service at mcp.sanity.io. It uses a streamable HTTP transport and OAuth authentication, so you don’t need to manage API tokens or run local server processes. To use it, configure your MCP client to point to the remote server: set the MCP server entry with the URL https://mcp.sanity.io and specify the transport type as http. The client will handle authentication via OAuth as supported by the hosted service, and you’ll receive continuously updated tools and features without any local setup.

Once configured, your MCP client can access the available MCP capabilities (tools, data schemas, and update mechanisms) through the remote server’s API. Since this is a hosted solution, you get the latest features automatically and don’t need to install or run Node.js locally to operate the MCP environment.

Prerequisites:

• An MCP client that supports remote HTTP MCP servers
• Internet access to reach mcp.sanity.io

Step-by-step:

1. Create or update your MCP client configuration to include the Sanity MCP server: { "mcpServers": { "sanity": { "url": "https://mcp.sanity.io", "type": "http" } } }
2. Ensure your client is configured to use OAuth authentication as supported by the hosted service. Follow the client’s authentication flow to obtain access tokens if required by the client.
3. Run your MCP client as you normally would. The client will communicate with the remote server at mcp.sanity.io to access tools, data models, and update capabilities.
4. If you need installation-specific guidance, refer to the hosted service documentation at mcp.sanity.io for CLI clients, IDE integrations, or library bindings.

Notes and tips:

• This MCP server is deprecated in favor of the hosted remote server at mcp.sanity.io. There is no local server setup required.
• The remote service uses OAuth authentication; you won’t manage raw API tokens in most setups.
• If you encounter connectivity issues, verify your client’s network access to https://mcp.sanity.io and ensure your OAuth credentials are correctly configured.
• Regularly check the hosted service documentation for any changes to endpoints or authentication flows.
• If you rely on specific MCP tools (e.g., Claude Code, Cursor, VS Code integrations), use the official hosted instructions provided by Sanity at mcp.sanity.io.