For people shipping MCP servers
Paste your repo. ManyCP publishes to the official registry, opens the pull requests and fills in every form. Ship a new version and every listing follows.
Free check · no signup · 5 seconds · try github/github-mcp-server
Example: one repo, weather-mcp, is sent to 26 directories. The registry publish goes live, 11 pull requests open, and 13 forms are filled in and wait for you to send them.
Example run. Real listings are checked before they say live.
The old way
26 directories. 26 different forms, file formats and rules. Then you ship a new version, and every listing is out of date. Now do it for your other servers too.
Rough estimates for a local npm server like weather-mcp (an example). The 4 remote-only directories (Smithery, ChatGPT and Codex plugin directory, awesome-remote-mcp-servers, AIBase MCP) aren't counted.
How it works
One GitHub link. ManyCP reads your package.json, README and tags. You type nothing else.
Time saved: reading 26 rulebooks
A repo link types itself into a box. ManyCP then reads the package file, the README, the license and the tags.
One listing, reshaped for every directory: name, description, tools, install command and a server.json. Every form field is filled in for the 13 that need a person.
Time saved: ~2 hours of form typing
A listing card fills in: title, short description, tool names, install command and a server.json file.
The registry publish and the pull requests go out. The 13 forms wait for you, ready to send.
Time saved: ~3 hours of PRs and publishing
A status grid of 26 directories. Sent ones turn live. Form-only ones end as ready to send.
Stays in sync
ManyCP checks your repo every hour on Pro and every day on Starter. New tag? It updates what it can, opens an update PR only when your entry changed, and flags the rest.
Example: you push the tag v1.5.0. ManyCP sees it, updates the official registry, PulseMCP is queued (it copies the registry when its intake reopens), an update pull request opens on awesome-mcp-servers, and form-only listings are marked needs update.
Your agent can do it
ManyCP is an MCP server too. Add it once. Then say what you want, in one sentence, from Claude Code, Cursor or any client that takes remote servers.
Example in Claude Code: you type "submit weather-mcp to every directory". The agent calls manycp check_listings, then manycp submit_server. 12 directories are sent and 10 forms are ready.
claude mcp add --transport http manycp https://manycp.com/mcp --header "Authorization: Bearer mcp_…"Swap mcp_… for a key from Settings. The free plan gets the read-only tools (list, check). Paid plans can also add, submit and sync.
26 directories
Each one links to the manual steps. See the full list
Who made this
I saw a tweet from someone building 17 MCP apps who did not want to submit each one by hand.
So I built ManyCP. Paste a repo, press Submit. The registry publish and the pull requests go out, and the other 13 forms come prefilled.
I read every email. hello@manycp.com
Built by @jonahdevs · jonahdevs.com
The tweet, in numbers
Pricing
By hand: 5 h 47 min per server. Launch: $19, once. Sync: from $9 a month.
LAUNCH50% off 3 months · first 100 · subscriptions · code at checkout
Pay once
Pay once to list everywhere.
$19per server, once
1 server = $19
No subscription. New version later? Relaunch for $19.
Subscribe
List it everywhere.
$9/month
or $90/year
Cancel anytime.
For people shipping lots of MCPs
Subscribe
Set it and forget it.
$29/month
or $290/year
Cancel anytime.
Your plan covers its servers. No launch credits needed.
Try the checker free. Import 1 server free. Check my listings
Questions
Not here? Email me. I read every one.
hello@manycp.com
26 today: 1 direct publish (the official MCP Registry), 11 Auto PR (awesome lists and catalogs on GitHub), 1 auto-indexed (PulseMCP copies the registry), and 13 assisted forms. The directories page has the rules for each one.
See every directoryManyCP forks the list repo, adds one line in that list's exact format, and opens a pull request. It uses your GitHub account, with the public_repo permission you approve, so the PR comes from you. The PR body says it was submitted with ManyCP on your behalf. It only runs for repos you own.
Your registry name looks like io.github.you/your-server, and signing in with GitHub proves you own the "you" part. For an npm package, the registry also needs mcpName in the package.json of the published version. For PyPI it needs a line that starts with mcp-name: in the README. If the proof is missing, ManyCP opens a pull request on your own repo that adds it, and tells you what to release. Remote-only servers need no package proof.
No. Launch a server once for $19 and ManyCP sends it to every directory that fits, with no subscription. A launched server stays launched: retries and new directories cost nothing more. A subscription keeps every listing current after that (Starter from $9 a month). An update to a launched server takes a subscription or another launch.
See the pricesOne pull request on your own repo, never on a fork and never straight to your main branch. It adds only what is missing: .mcp.json for cursor.directory, glama.json to claim your Glama listing, gemini-extension.json for the Gemini CLI gallery, server.json and the mcpName line for the official registry. Existing files are never rewritten. You review the files and merge. cursor.directory, Glama and Gemini wait until you do. Repo topics are only added if you tick the box.
You see it marked rejected, with the reason the maintainers gave. ManyCP never re-opens a closed PR on its own. Fix the entry, then click Try again.
Every hour on Pro and every day on Starter, ManyCP checks your repo for a new version or a changed description. A new version goes straight to the official registry. Pull request lists get an update PR only when your entry text changed. Everything else is marked needs update, with the form filled in again.
The big awesome-mcp-servers list only takes servers that already have a Glama page. Glama has no submit API, so it is one of the prefilled forms. ManyCP holds that pull request until Glama shows your server, so it never opens a PR that would be closed at once.
Yes. ManyCP is an MCP server at https://manycp.com/mcp. Add it with one command and an API key from Settings, then ask your agent to submit your server. Any client that takes remote servers with a header will work. The free plan gets the read-only tools. A launch credit or a paid plan can also add, submit and sync.
Yes. A subscription cancels in one click in the billing portal. You keep access until the period you paid for ends. Listings that are already live stay live. Syncing stops. A launch is paid once, so there is nothing to cancel. If a launch payment is refunded, the credits you have not used are removed.
Your GitHub token is encrypted before it is stored and is never sent to your browser. Sign-in only asks to read your profile and email. The public_repo permission is asked once, when you first submit to a GitHub list. Stripe handles payments, so card numbers never touch ManyCP.
Read the privacy pageNo. It is one pull request per server, from the owner, following each repo's CONTRIBUTING file, with ManyCP named in the PR body. It never resubmits a closed PR, and it spaces requests out, about 10 an hour per person. If a list asks you to star the repo first, ManyCP asks you before it stars.
Ready when you are
Paste a repo. Your registry publish and pull requests go out today.