Skip to content

feat: expose Sanity MCP on MCP Registry - #19

Closed
jonahsnider wants to merge 3 commits into
mainfrom
aigro-4537/mcp-registry
Closed

feat: expose Sanity MCP on MCP Registry#19
jonahsnider wants to merge 3 commits into
mainfrom
aigro-4537/mcp-registry

Conversation

@jonahsnider

@jonahsnider jonahsnider commented Feb 12, 2026

Copy link
Copy Markdown
Member

Closes AIGRO-4176

Since the MCP repo is closed source I opted to add this functionality to agent-toolkit. Once merged, we can trigger releases to the MCP Registry from GitHub Actions using their workflow_dispatch functionality.

The server.json is currently setup with a name of io.github.sanity-io/mcp - AFAIK this means we can publish without needing to prove DNS or HTTPS ownership of sanity.io. I think we can change this in the future if needed?
server.json has a name of io.sanity/mcp, which requires us to prove we own sanity.io -- see sanity-io/www-sanity-io#3295

Here's some resources to add context during review:

jonahsnider commented Feb 12, 2026

Copy link
Copy Markdown
Member Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@jonahsnider
jonahsnider force-pushed the aigro-4537/mcp-registry branch from 5f26e24 to a065956 Compare February 12, 2026 20:24
@jonahsnider
jonahsnider requested a review from jwoods02 February 12, 2026 20:34
@jonahsnider
jonahsnider marked this pull request as ready for review February 12, 2026 20:50

@jwoods02 jwoods02 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for picking this up, love adding this to a GH action.

I'd recommend we use io.sanity/mcp as the name from the start rather than io.github.sanity-io/mcp. Per the registry docs on verifying server authenticity (https://modelcontextprotocol.io/registry/about#verifying-server-authenticity), the namespace is how the registry establishes trust — domain-verified names (io.sanity/) signal this is officially from Sanity, while GitHub-based names (io.github.sanity-io/) are the convention for individual devs or projects without domain verification.

Changing the name later would effectively create a new server in the registry (it's the unique identifier), so it's worth getting right up front.

The publish workflow will also need to switch from github-oidc auth to DNS or HTTP auth, but should be a relatively easy change, just needs the private key stored as a GitHub Actions secret.

@jonahsnider
jonahsnider changed the base branch from ci/add-ci to graphite-base/19 February 13, 2026 14:55
@jonahsnider
jonahsnider force-pushed the aigro-4537/mcp-registry branch from 73ef717 to dd44847 Compare February 13, 2026 14:55
@graphite-app
graphite-app Bot changed the base branch from graphite-base/19 to main February 13, 2026 14:55
@jonahsnider
jonahsnider force-pushed the aigro-4537/mcp-registry branch from dd44847 to a4845a3 Compare February 13, 2026 14:55
@jonahsnider
jonahsnider requested a review from jwoods02 February 13, 2026 22:33
@jonahsnider

Copy link
Copy Markdown
Member Author

I'd recommend we use io.sanity/mcp as the name from the start

done 🫡 - see sanity-io/www-sanity-io#3295 for the PR to add the proof file to sanity.io

@jonahsnider

Copy link
Copy Markdown
Member Author

Superseded by sanity-io/mellon#275

@jonahsnider
jonahsnider deleted the aigro-4537/mcp-registry branch February 18, 2026 02:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants