Agent MCP Directory

Sanity: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sanity at mcp.sanity.io answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.

Fact sheet

CompanySanity
Domainsanity.io
CategoryDeveloper Tools (Ora leaderboard category)
MCP serverSign-in required (OAuth with client registration)
Tranco rank3,733 on the list of 4 November 2026
Ora score72, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for sanity.io, a vendor-published score)
Company found throughthe vendor's own documentation; Ora's public leaderboard
Last verified4 November 2026

MCP server

Endpointhttps://mcp.sanity.io
How it was foundlisted in the vendor's own documentation; Ora's public leaderboard
Transportstreamable-http
HTTP status401
Connected4 November 2026, 20:01 UTC
Handshake time436 ms over 1 attempt
Documentationwww.sanity.io

The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:56:03Z https://mcp.sanity.io sent initialize result auth-required (HTTP 401) 371 ms
  • 20:01:39Z https://mcp.sanity.io sent initialize result auth-required (HTTP 401) 436 ms

Authentication

Auth typeOAuth with client registration
What the challenge saidBearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.sanity.io/.well-known/oauth-protected-resource"
Protected resource metadatamcp.sanity.io
Authorization server metadatamcp.sanity.io
Registration endpointhttps://mcp.sanity.io/register

The sign-in route, step by step

  1. Request https://mcp.sanity.io without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the protected resource metadata at https://mcp.sanity.io/.well-known/oauth-protected-resource to find the authorization server.
  3. Register a client at the registration endpoint https://mcp.sanity.io/register (dynamic client registration), so no human has to create an app first.
  4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

Package@sanity/cli on npm (page)
Existsyes
Latest version8.27.0
Last publish30 October 2026
Command namessanity
Checked4 November 2026

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNot read: the site's robots.txt disallows the path for this crawler.
WebMCP in the initial HTMLNot detected on the home page by the shared crawl.
MCP discovery fileNot found (the crawl got a non-200 answer).
A2A agent cardNot found (the crawl got a non-200 answer).
A2A agent card (older path)Not found (the crawl got a non-200 answer).
agents.jsonNot read: robots.txt or the crawl budget kept the shared crawl away from this path.
OAuth authorization server metadataNot found (the crawl got a non-200 answer).
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryNo
GitHub MCP RegistryNo
awesome-remote-mcp-serversNo
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.