Agent Connectors

Compare

Context7 MCP server vs Sanity MCP server

Context7 MCP server and Sanity MCP server are MCP implementations in Knowledge and documents. Publisher class, status, transport, auth, tool coverage, hosting, and last checked appear only with a source. A field without one says Not documented upstream. This page is not a ranking.

Context7 listingSanity listing

Context7 MCP server vs Sanity MCP server
FieldContext7Sanity
DescriptionContext7, from Upstash, is an MCP server an agent can use to fetch up-to-date code documentation for a prompt. This paraphrases the MCP Registry record io.github.upstash/context7, version 4.4.1.Sanity is an MCP server for direct access to Sanity projects, including content, datasets, releases, schemas, and agent rules. This paraphrases the MCP Registry record io.sanity.www/mcp, version 2.40.0.
CategoryKnowledge and documentsKnowledge and documents
Publisher classVendor. Registry namespace io.github.upstash matches the repository org upstash. sourceVendor. Registry namespace io.sanity.www is the vendor's domain. The MCP Registry verifies that namespace against the domain. source
StatusNot documented upstream sourceNot documented upstream source
TransportRemote: https://mcp.context7.com/mcp sourceRemote: https://mcp.sanity.io source
AuthNot documented upstream sourceNot documented upstream source
Tool coverageNot documented upstream sourceNot documented upstream source
HostingNot documented upstream sourceNot documented upstream source
Last checked2026-10-15 source2026-10-15 source
Listing linkhttps://context7.comhttps://github.com/sanity-io/agent-toolkit
Repositoryhttps://github.com/upstash/context7https://github.com/sanity-io/agent-toolkit
Homepagehttps://context7.comNot listed
Sourcehttps://registry.modelcontextprotocol.io/v0.1/servers/io.github.upstash%2Fcontext7/versions/4.4.1https://registry.modelcontextprotocol.io/v0.1/servers/io.sanity.www%2Fmcp/versions/2.40.0

Connect it: Context7

from vendor docs, not tested by us

Configuration validation checks that these snippets parse and include every environment variable named in the Auth fact. It is not a connection test.

Source: MCP Registry record io.github.upstash/context7 4.4.1

The same record names the npm package @upstash/context7-mcp for stdio. It does not write an npx command, so this snippet uses only the remote URL.

Remote URL

Claude Desktop

{
  "mcpServers": {
    "context7": {
      "url": "https://mcp.context7.com/mcp"
    }
  }
}

Claude Code

claude mcp add --transport http context7 "https://mcp.context7.com/mcp"

Cursor

{
  "mcpServers": {
    "context7": {
      "url": "https://mcp.context7.com/mcp"
    }
  }
}

VS Code

{
  "servers": {
    "context7": {
      "type": "http",
      "url": "https://mcp.context7.com/mcp"
    }
  }
}

Connect it: Sanity

from vendor docs, not tested by us

Configuration validation checks that these snippets parse and include every environment variable named in the Auth fact. It is not a connection test.

Source: MCP Registry record io.sanity.www/mcp 2.40.0

Remote URL

Claude Desktop

{
  "mcpServers": {
    "sanity": {
      "url": "https://mcp.sanity.io"
    }
  }
}

Claude Code

claude mcp add --transport http sanity "https://mcp.sanity.io"

Cursor

{
  "mcpServers": {
    "sanity": {
      "url": "https://mcp.sanity.io"
    }
  }
}

VS Code

{
  "servers": {
    "sanity": {
      "type": "http",
      "url": "https://mcp.sanity.io"
    }
  }
}