How to submit an MCP server to awesome-mcp-list

This list asks for very little: one bullet, in one fixed format, for a server whose source is on GitHub. That makes the format the whole review. A maintainer's habit of rewriting descriptions and landing the bullet directly is the other thing to know, and I found it in two closed pull requests^[4][5].

It has to have a public repository

The contributing guide wants a public GitHub repository for the server, and the repository must not be archived. A website or hosted endpoint without a public repo is not accepted, "even if the server is listed on the MCP Registry"^[1]. If your server is hosted-only, the remote list is the place, not this one.

The bullet

-   **[example-user/weather-mcp](https://github.com/example-user/weather-mcp)** [![GitHub stars](https://img.shields.io/github/stars/example-user/weather-mcp?style=social)](https://github.com/example-user/weather-mcp): Gets forecasts and alerts for a city.

• Three spaces after the dash, a bold link whose text is owner/repo, and the stars badge for the same owner/repo with style=social^[1][2].
• A colon, then one concise sentence that ends with a period. The template's checklist says so, and the guide asks for one concise sentence^[2].
• Add exactly one bullet at the end of the right section and change nothing else. The README has 24 sections, from Browser Control to Robotics & Physical AI^[3].

The pull request

1. Fork, then branch from main.
2. Add the one bullet. Search the README for your repository first so you do not add a duplicate^[1].
3. Title it Add owner/repo to <Category>. The template asks for the repository address, the category, and the exact line you added^[2].
4. The diff should touch only README.md.

What a maintainer does to your line

Two recent pull requests show a pattern. On 27 Sept 2026 a maintainer landed an entry directly on main and closed the pull request, after cutting "Official" from the description and the transport and hosting details, so it was one short sentence about what the server does^[5]. In another, the description was rewritten as one neutral sentence ending with a period, with a trailing npx install command removed because it made a second sentence^[4].

So write the sentence the way they will: neutral, one sentence, no install command, no word that claims status. A pull request that shows as closed and not merged on this repository can be an entry that did land.

What gets closed

The guide lists what usually ends a pull request or issue without a landing^[1]:

• It links only a website or hosted MCP address, with no public repo.
• The format is wrong: no badge, wrong spacing, no owner/repo.
• It duplicates a listing or another open pull request.
• The repository is dead or returns 404.
• It rewrites large parts of the README.

For a format closure the guide says to fix it and open a new pull request, and calls clean submissions welcome^[1].

By hand, step by step

Copy the template line, replace the owner and repo in all three places, write the sentence, paste it at the bottom of the right section, and open the pull request. That is the entire route; there is no form and no sign-in beyond GitHub.

Current status, 1 Oct 2026

On 2 Oct 2026 the list had 27 open pull requests^[6]. The contributing guide and template are the ones quoted above^[1][2].