How to submit an MCP server to GitHub MCP Registry

There is no form for the GitHub MCP Registry, and no page that lists criteria. There is a public discussion thread, and a short sequence that replies in it describe: be in the official registry first, then ask for onboarding^[1]. Once a server is in, a reply speaking for the registry says new versions published to the official registry sync from there^[1].

The sequence

• Publish to the official registry. A reply in November 2025, from an account whose profile lists GitHub as its company, says this comes first, and calls the GitHub list curated at that time^[1].
• Ask. GitHub's blog post says to email partnerships@github.com once published^[2], and the discussion is where requesters post a comment instead.
• Wait. In May 2026 another reply, written as "our side", said that syncing versions now works but onboarding a new server is "still a manual curation process", and that the poster's request would go to the product team^[1].

What a request comment carries

GitHub does not publish a required format. The requests in the thread share these fields, taken from the longer ones^[1]:

### Onboarding request: io.github.your-name/your-server

| Field         | Value                                                        |
| ------------- | ------------------------------------------------------------ |
| Registry name | io.github.your-name/your-server                              |
| Version       | 1.0.0 (active, isLatest: true in the official registry)     |
| Transport     | stdio, or streamable-http with the URL                       |
| Repository    | https://github.com/your-name/your-server (licence named)     |
| Description   | one sentence                                                 |

You press Comment yourself, signed in to GitHub, and the comment is public under your name.

How to see whether you are in

# is it in the GitHub registry's list? (public API)
curl "https://api.mcp.github.com/v0.1/servers?search=your-server"

# or open the server's own page: 200 if listed, 404 if not
https://github.com/mcp/io.github.your-name/your-server

A requester in the thread used the second check, and noted that a server's page returned 404 until it was onboarded^[1]. The API and the web list are both GitHub's own^[3][4].

Why a request sits unanswered

• It was not in the official registry yet. The replies say that comes first^[1]. Check with the official registry's search, using search=.
• The same request posted twice. One requester came back on 8 Sept 2026 to say their request, posted 13 Aug, had no reply^[1]. Replies speaking for the registry are few: I found three, dated 10 Nov 2025, 19 May 2026 and 30 June 2026.
• An entry that is not active and latest. Requesters quote their official-registry entry as active with isLatest: true when they ask^[1], so check yours returns that before you post.

By hand

Everything on this page is by hand: the registry publish in your terminal, then one public comment or one email. The thread links its own guide to publishing, which is the same flow described on the official registry's page.

Current status, 1 Oct 2026

On 1 Oct 2026, GitHub's registry API listed 339 servers^[3]. The thread had 61 comments asking for onboarding since 9 July 2026, from 59 accounts. Seven of those comments name servers that are in the list now, nine servers in all, which I matched by registry name^[1][3]. One earlier request, posted 19 Oct 2025, was answered on 30 June 2026 with a note that the poster's servers were onboarded^[1]. The thread's own page is here.