How to submit an MCP server to Goose extensions
By Jonah EasePublished Last checked
Goose's extension directory used to take pull requests that added a line to a JSON file. It does not any more. On a maintainer announced that the project was retiring its own list of MCP servers in favour of the official MCP Registry, and that new contributions were halted[1]. This page is short because the route is. The useful part is what to do instead.
What the maintainers said
- New contributions to the Goose registry are stopped. The announcement asks people not to open pull requests adding servers, and says they will not be merged[1].
- For authors, the instruction is to publish to the official MCP Registry in its
server.jsonformat. Goose plans one-click install from that format and then to replace the extensions page in its docs[1]. - The repository's documentation guide repeats it: do not add new third-party servers to
static/servers.json, and do not write server-specific tutorials just to support a directory submission[2].
What the file still holds
servers.json still exists and existing entries may be maintained or migrated[2]. On it listed 57 entries. Eleven of them are remote, with a url and a streamable-http type, and the other 46 start a local command[3]. That matters for one old assumption: the list was never only for servers you run on your own machine.
What happened to pull requests after the announcement
Two pull requests that added a server to the directory were closed unmerged in September, after the announcement. On a maintainer replied to one with a message that the project had decided to stop accepting new entries and a link to the announcement[4]. On the author of another closed their own pull request after reading the guide, noting that the server was already published in the official registry, so nothing further was needed[5].
If you opened a pull request before reading any of this, there is nothing to fix in the pull request itself. The format of the entry was never the problem.
The route that replaces it
Publish to the official registry with the command-line publisher, a server.json that validates, and proof that you own the name[6]. The step-by-step is on the official registry's page. Goose's note says that once its support lands, your server will appear in its doc pages automatically[1]. It does not say when.
Until then, the entries in the file show the two shapes Goose understands: a command with its environment variables, or a Streamable HTTP address[3]. Put whichever fits your server in your README, so a Goose user has something to copy.
By hand, nothing to submit
There is no form to fill in and no pull request to open for Goose today, so there is no by-hand route to describe. The by-hand work is the registry publish above, and it serves every client that reads the registry, not just this one.
Current status,
Closed to new entries since . The announcement had no replies and gives no reopening date, and the documentation guide still carried the same instruction[1][2].
Sources
- Goose discussion 10830: Retiring goose's MCP registry in favor of the official MCP registry · checked
- Goose documentation/AGENTS.md: MCP Extension Directory · checked
- Goose documentation/static/servers.json · checked
- Goose pull request 11917: Add Zovo Invoice to the extensions directory (closed) · checked
- Goose pull request 12058: Add HasData remote MCP server (closed) · checked
- MCP Registry docs: Quickstart · checked
ManyCP is not affiliated with, endorsed by or sponsored by any directory, Docker, OpenAI, Anthropic or GitHub named here. Names are used to say which service a fact is about.
Or skip all of that
Or let ManyCP publish it to the registry
Goose takes no new entries. ManyCP builds your server.json, checks it with the official MCP Registry and publishes it with your GitHub sign-in, the route Goose's maintainers point to. Goose has not said when it will read from the registry.