feat: expose Sanity MCP on MCP Registry - #19
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
5f26e24 to
a065956
Compare
jwoods02
left a comment
There was a problem hiding this comment.
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.
73ef717 to
dd44847
Compare
88b08f1 to
0a140e3
Compare
dd44847 to
a4845a3
Compare
done 🫡 - see sanity-io/www-sanity-io#3295 for the PR to add the proof file to sanity.io |
|
Superseded by sanity-io/mellon#275 |

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_dispatchfunctionality.Theserver.jsonis currently setup with anameofio.github.sanity-io/mcp- AFAIK this means we can publish without needing to prove DNS or HTTPS ownership ofsanity.io. I think we can change this in the future if needed?server.jsonhas a name ofio.sanity/mcp, which requires us to prove we own sanity.io -- see sanity-io/www-sanity-io#3295Here's some resources to add context during review:
server.json