How to submit an MCP server to mcp.directory

The form on mcp.directory asks for one thing: a public GitHub repository address. Everything else is optional, and the site says it reads the rest from GitHub itself^[1]. So the route is short, and the interesting question comes before it: the site also adds servers it finds in the official MCP Registry, and if yours was found that way, you should claim the listing and not submit a second one.

First, check whether you are already listed

The page has a box headed "Already listed?". If your server is in the directory because it was found through the official registry, you can claim it to get a verified badge and edit access, by emailing the address shown on the page^[1]. Search the directory for your server's name before you fill in anything. A published registry entry is the likeliest reason you are there already; the route for that is on the official registry's page.

The five fields

• GitHub Repository URL is required. The page lists what it detects from it: name, description, language, licence, tools and README^[1].
• npm Package and PyPI Package are optional. The placeholders show the shapes it wants, @org/mcp-server for npm and a bare name for PyPI.
• Short Description is optional and limited to 100 characters, one sentence. If you leave it empty, the page says it will generate one from the README^[1].
• Your Email is optional, and is used to tell you when the server is published^[1].

After you press the button

The page lists five steps under "What happens next"^[1]:

1. It pulls metadata from GitHub: name, description, stars, language, licence and README.
2. It detects the tools by analysing the server's MCP implementation.
3. It generates install configurations for the major clients.
4. It reviews the submission for quality and accuracy, within 24 hours according to the page.
5. It publishes the listing, live and searchable.

The 24 hours is the site's statement, not something I tested, so treat it as an estimate and not a promise.

When the listing looks wrong

• The tools are missing or odd. The page says they are detected by analysing your server's MCP implementation, and the form has no field to correct them^[1]. Keep the README's tool list accurate, because it reads that too, and use the claim route for edit access.
• The description is not what you would write. Fill in the short description yourself. Otherwise it comes from the README^[1].
• A second listing for the same server. That is the "Already listed?" case above. Claim the existing one by email.

By hand

1. Make sure the GitHub repository is public and its README says what the tools do.
2. Open mcp.directory/submit. The page asks for no account.
3. Paste the repository address, add a one-sentence description and an email if you want the note, and you click Submit for Review.

I found no price on the form or the pages around it. The site's Partners page is separate from submitting: it shows a card labelled Sponsored, says some links are affiliate links, and has an enquiry form for companies that want to work with the site^[3].

Current status, 1 Oct 2026

The About page counted 2,303 servers, 9,291 skills and 1,907 or more publishers^[2]. The submit form was open with the fields above and the "Already listed?" claim route.