How to submit an MCP server to best-of-mcp-servers

Nothing on this list is written by hand, including the part that ranks you. A weekly job reads GitHub and the package registries for every project in a YAML file, scores each one, and rewrites the README^[2][4]. Your submission is therefore a few lines of YAML, and the number that decides where you sit comes later and is not yours to set.

The README is generated, so leave it alone

The workflow runs at 00:00 UTC every Wednesday. It opens a branch named update/<date> and regenerates the list there^[2], and a maintainer merges the result; the update for 30 Sept 2026 was merged that day^[6]. The pull request template has a checkbox for exactly one thing contributors get wrong: you have not modified the README, because projects are added only in projects.yaml^[5].

An issue or a YAML edit

• Open an issue with the suggest-project template, and fill in what it asks for^[1].
• Edit projects.yaml and open a pull request, which GitHub's web editor can do for you^[1].

Either way: one project per issue or pull request, titled Add project: project-name, after searching projects.yaml, the README and the issues for a duplicate^[1].

The entry

- name: Weather MCP
  github_id: example-user/weather-mcp
  npm_id: weather-mcp
  labels: ["weather"]
  category: developer-tools

Only name and github_id are required, and the name has to be unique in the list. category and labels must be IDs that already exist in the file. A project that fits no category is left without one and lands in Others. Package IDs for PyPI, conda, npm, Docker Hub and Maven are optional and feed the metrics^[1].

Where the ranking comes from

The README says every project is ranked by a project-quality score calculated from metrics collected automatically from GitHub and package managers. On 1 Oct 2026 it described 400 projects with 1.3M stars in 34 categories^[4]. The file's own configuration sets the minimum stars and minimum project rank to zero and requires no licence or homepage, so nothing keeps a new project out^[3]. What a new repository lacks is history, and the score reflects that.

What goes wrong

• Editing the README. It is overwritten at the next run, and the template asks you to confirm you did not^[5].
• Inventing a category or label ID. Use ones already in projects.yaml, or ask for a new category through the add-or-update-category template^[1].
• Putting several projects in one request, or using a title other than Add project: name^[1].
• Adding what is already there. Search before you open anything.

By hand

1. Search for your repository in the three places the guide names.
2. Add the YAML block to projects.yaml, or open the suggest-project issue instead.
3. Title it Add project: your-name and send it.
4. Once it is merged, the next Wednesday run measures the project and ranks it.

Current status, 1 Oct 2026

On 2 Oct 2026 there were 73 open pull requests on the repository^[7]. The update workflow was still on its Wednesday schedule^[2].