Retiring goose's MCP registry in favor of the official MCP registry and server.json format #10830
jamadeo
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
TL;DR: We're deprecating goose's own MCP server registry and adopting the official MCP registry and its server.json format. Effective immediately, we are no longer accepting new server contributions to our registry.
Why
Maintaining our own list of MCP servers duplicates work that's already being done elsewhere — including by an official, community-governed registry. Server authors shouldn't have to publish to a goose-specific list, and we shouldn't be a bottleneck for discoverability. Standardizing on the official registry means one place to publish, and a shared format everyone can build on.
What's changing now
New contributions to the goose registry are halted. Please don't open PRs adding servers; we won't be merging them.
What's next
We'll implement support for one-click installation using the
server.jsonformat. Then, we'll replace the extensions page in the goose docs.For server authors
Publish your server to the official MCP registry using the server.json format. Once our support lands, it will show up in the goose doc pages automatically.
All reactions