How to submit an MCP server to awesome-remote-mcp-servers
Open a pull request that adds one entry to punkpeye/awesome-remote-mcp-servers. A maintainer merges it. It needs a listing on Glama first.
The awesome list for hosted MCP servers.
- How
- Auto PR
- Fits
- Remote servers (a public URL)
- By hand
- ~25 min
- Speed
- Median about 36 hours (Sept 2026).
Do Glama first. awesome-remote-mcp-servers depends on it.
The steps, by hand
- 1
Star the repo. Pull requests from accounts that did not star it are not merged.
- 2
Get a Glama connector listing. Publishing to the official registry does it.
- 3
Fork punkpeye/awesome-remote-mcp-servers.
- 4
Add a 3-line entry to README.md: your name linking to your homepage plus the endpoint in backticks, then the Glama connector badge indented two spaces, then an auth marker and a description of 120 characters or fewer.
- 5
Open a pull request titled "Add <name> remote MCP server".
- 6
A check calls your endpoint's initialize method. A 401 or 403 counts as alive.
What you need
- A public endpoint that answers an MCP initialize call
- Streamable HTTP or SSE
- A Glama connector listing
- The account that opens the PR has starred the repo
- One endpoint for everyone (no per-user URLs)
// or skip all of that
Or let ManyCP do it in one click
ManyCP forks punkpeye/awesome-remote-mcp-servers, adds your entry in the exact format, and opens the pull request from your GitHub account. It waits until Glama lists you, so the PR is not closed at once. It tracks the PR until it is merged.