How to submit an MCP server to awesome-mcp-servers
By Jonah EasePublished Last checked
This is a list in a README, and the way in is a pull request that adds one line. What decides whether it is merged is mostly a bot: a workflow checks every pull request for a Glama badge, a permitted emoji, a full owner/repo name and a GitHub link, and labels it with the result[3]. Its labels are the checklist.
Is the list for your server?
The list is for servers with a public GitHub repository that you install and run yourself. A hosted, remote-only server belongs in the sibling list, awesome-remote-mcp-servers[1][2]. The bot posts that redirect on any entry whose link is not a github.com URL[3]. That sibling list is a queue of its own: 422 pull requests were open on [7].
The line you add
- [example-user/weather-mcp](https://github.com/example-user/weather-mcp) [](https://glama.ai/mcp/servers/example-user/weather-mcp) 馃搰 鈽侊笍 馃崕 馃獰 馃惂 - Weather forecasts and alerts for any city.- The name in full as
owner/repo, linked to the repository. A bare repo name fails[3]. - The Glama score badge, then at least one permitted emoji: language, local or cloud scope, and operating system[3].
- A short description of what the server does, in the right category, alphabetical within it[1].
The badge needs a Glama listing first; see Glama's page for what that takes. The bot only asks that the server has been evaluated and shows a quality score[3].
The labels the bot applies
| Label | Meaning | Open on |
|---|---|---|
| missing-glama | No Glama score badge on the new entry | 1,289 |
| duplicate | The repository link is already in the README | 210 |
| missing-emoji | No permitted emoji, or one that is not on the list | 69 |
| invalid-name | Name not in owner/repo form | 52 |
| non-github-url | A link outside GitHub | 99 |
Label meanings from the workflow[3]; counts from GitHub's search on [5][6]. The other three counts use the same query with the label swapped.
By hand
- Fork the repository, add the line, open the pull request titled for the server, and read the bot's comment when it arrives. The workflow runs again when the pull request is edited or updated, so a fix is a push to the same branch[3].
- CONTRIBUTING.md also carries a note for automated agents: a separate, streamlined merge route, opted into with three robot emoji at the end of the pull request title[1]. I did not test it and cannot say how it behaves.
- After a merge, the bot comments with a welcome and offers a flair in the project's Discord.
Current status,
On , 2,724 pull requests were open. GitHub lists 822 merged between 1 Sept and 1 Oct 2026[4][8], so merges are happening alongside the queue.
How long merges took
In the 90 days to , 1501 outside pull requests merged here; the typical one was merged 9.9 days after it was opened. The middle half took 4.0 days to 22 days.
| Window ending | Rolling median | Merges in window |
|---|---|---|
| 10 Oct 2025 | 6.3 days | 30 |
| 17 Oct 2025 | 5.9 days | 33 |
| 24 Oct 2025 | 2.5 days | 22 |
| 31 Oct 2025 | 3.4 days | 21 |
| 7 Nov 2025 | 1.9 days | 20 |
| 14 Nov 2025 | 2.2 days | 19 |
| 21 Nov 2025 | 1.4 days | 10 |
| 28 Nov 2025 | 1.2 days | 10 |
| 5 Dec 2025 | 20 h | 8 |
| 12 Dec 2025 | 48 days | 97 |
| 19 Dec 2025 | 41 days | 108 |
| 26 Dec 2025 | 41 days | 108 |
| 2 Jan 2026 | 41 days | 106 |
| 9 Jan 2026 | 1.5 days | 36 |
| 16 Jan 2026 | 18 h | 37 |
| 23 Jan 2026 | 1.5 days | 56 |
| 30 Jan 2026 | 17 days | 163 |
| 6 Feb 2026 | 26 days | 143 |
| 13 Feb 2026 | 27 days | 133 |
| 20 Feb 2026 | 5.5 days | 193 |
| 27 Feb 2026 | 12 h | 99 |
| 6 Mar 2026 | 21 h | 150 |
| 13 Mar 2026 | 1.2 days | 276 |
| 20 Mar 2026 | 1.2 days | 328 |
| 27 Mar 2026 | 2.4 days | 418 |
| 3 Apr 2026 | 3.1 days | 477 |
| 10 Apr 2026 | 2.4 days | 401 |
| 17 Apr 2026 | 3.0 days | 398 |
| 24 Apr 2026 | 4.4 days | 334 |
| 1 May 2026 | 3.8 days | 408 |
| 8 May 2026 | 4.1 days | 355 |
| 15 May 2026 | 4.7 days | 246 |
| 22 May 2026 | 4.8 days | 231 |
| 29 May 2026 | 12 days | 250 |
| 5 June 2026 | 16 days | 189 |
| 12 June 2026 | 10 days | 408 |
| 19 June 2026 | 8.2 days | 527 |
| 26 June 2026 | 5.3 days | 380 |
| 3 July 2026 | 5.2 days | 394 |
| 10 July 2026 | 3.5 days | 300 |
| 17 July 2026 | 7.0 days | 324 |
| 24 July 2026 | 9.4 days | 469 |
| 31 July 2026 | 8.9 days | 563 |
| 7 Aug 2026 | 8.9 days | 519 |
| 14 Aug 2026 | 8.6 days | 349 |
| 21 Aug 2026 | 8.5 days | 335 |
| 28 Aug 2026 | 6.3 days | 47 |
| 4 Sept 2026 | 21 days | 114 |
| 11 Sept 2026 | 19 days | 494 |
| 18 Sept 2026 | 14 days | 748 |
| 25 Sept 2026 | 11 days | 936 |
| 2 Oct 2026 | 9.8 days | 823 |
Measured . Pull requests merged on each list's GitHub repo, timed from opened to merged, read from GitHub's REST pulls list. Bot accounts ([bot]), the repo's owners, members and collaborators, and pull requests from a branch inside the list's own repo are left out. A past figure, not a promise. All 10 directories side by side: how long MCP directories take to merge.
Sources
- awesome-mcp-servers: CONTRIBUTING.md 路 checked
- awesome-mcp-servers: README (legend and scope) 路 checked
- awesome-mcp-servers: the check-glama workflow 路 checked
- awesome-mcp-servers: open pull requests 路 checked
- Open pull requests labelled missing-glama 路 checked
- Open pull requests labelled duplicate 路 checked
- awesome-remote-mcp-servers: open pull requests 路 checked
- Pull requests merged 1 Sept to 1 Oct 2026 路 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 do it in one click
ManyCP forks punkpeye/awesome-mcp-servers, adds your entry in the exact format, and opens the pull request from your GitHub account. It waits until Glama lists you, so the PR is not closed at once. It tracks the PR until it is merged.