How to submit an MCP server to mcp.so
By Jonah EasePublished Last checked
mcp.so has one submit page, and on it offered one plan on it: a $39 one-time publishing fee, with no free option on the form[1]. That is the whole decision. Everything else on this page is what the form asks for, what goes wrong, and the second place submissions are filed.
What the form asks for
| Tab | Required | Optional |
|---|---|---|
| MCP Server | Repository URL, a GitHub address | Name |
| Remote Server | Remote endpoint URL, and Name | None |
The page also has MCP Client and AI Agent tabs, which are not for servers. Read [1][2]. A required field carries an asterisk.
The price, as printed
The only plan card is headed Paid submission, $39 one-time publishing fee, and lists four things: publish immediately without review, a verified badge, featured and priority placement, and a dofollow project link[1]. The card was already ticked when the page loaded, and clicking it did not untick it. The button under it reads Pay and submit automatically.
The same page says its listings sit on a high-authority domain; that is the directory's own claim and I did not check it. Whether $39 is worth it for your server is your decision, and no one else can make it for you.
The page prints its own audience figures next to the form: a Domain Rating of 72, 2.2 million unique visitors and 6 million pageviews over twelve months, and 266 thousand monthly active users. They are mcp.so's claims as shown on [1], and I did not check them. For questions about a submission the page points to a ticket link.
The other route: a public issue
The directory's code repository, chatmcp/mcpso, also takes submissions as issues titled "Submit" or "Submit Remote MCP Server", with a name and a description. One such issue asks for a listing "through the community issue review route"[4]. On the repository had 3,407 open issues[3].
I could not find a page from mcp.so that describes this route, a review time, or who reads the issues. The evidence is indirect: an issue opened on was closed on by its author, who wrote that the server was now listed[5].
Duplicates and missing names
- The same server filed twice. Authors close their own extra issues as duplicates[6].
- A remote submission with no name. Name is a required field on the Remote Server tab and optional on the other[2].
- A repository URL in the wrong shape. The field's placeholder is
https://github.com/owner/repository[1].
By hand
Open the page, choose the tab, fill in the fields, and pay with your own card. You press Pay and submit automatically yourself, and the payment is between you and mcp.so. The issue route above shows no fee that I could see, and no stated review time.
Current status,
One plan at $39, one time, on both server tabs[1][2]. New issues were still arriving in the tracker that day[3].
Sources
- mcp.so: Submit your project (MCP Server tab) · checked
- mcp.so: Submit your project (Remote Server tab) · checked
- chatmcp/mcpso: open issues · checked
- chatmcp/mcpso issue 4556: a remote server submission · checked
- chatmcp/mcpso issue 3404: closed by its author once listed · checked
- chatmcp/mcpso issue 3439: closed as a duplicate · 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 fill it in for you
ManyCP writes every answer and opens the right page. You send it yourself. It takes your sign-in and your card.
ManyCP prepares
- The repo or endpoint URL and the name, for the right tab
You do
- Decide if it is worth $39
- Sign in
- Pay on their page