Confirm that this is the right list
punkpeye’s awesome-mcp-servers contribution guide currently covers public GitHub repositories for servers people can install and run. Remote-only services are directed to a separate awesome-remote-mcp-servers list. A public marketing repository does not by itself make a hosted-only service installable.
Read the current contribution guide and validation workflow immediately before preparing the PR. Keep the change focused on one server. A small diff helps reviewers assess the new entry without disentangling unrelated formatting edits.
Resolve the Glama dependency
The current validation workflow requires a Glama badge tied to an evaluated server. MCP Server List checks the authenticated matching record, completed evaluation, inspected tools and actual discovery before this target can pass preflight. A generated badge URL is not enough.
If evaluation cannot start, reproduce the launch and introspection steps in a clean environment. Check missing files, required configuration, and startup output. Follow Glama’s current instructions for its environment instead of assuming your development Dockerfile or shell session is sufficient.
- Find or create the correct Glama server record.
- Resolve startup and introspection problems reported by its checks.
- Inspect the score page and use the exact displayed listing path.
- Keep ownership claims separate from evaluation: managing a listing does not prove its runtime works.
Write one precise entry
Use the full owner/repo as the entry name, a GitHub primary link, a permitted emoji describing the language or execution environment, and a brief task-focused description. Use only claims a reader can verify from the repository.
The example below is an illustrative shape. OWNER/REPO and its badge path must be replaced with real values. Choose the correct language and runtime markers instead of copying them blindly, and follow the current category and alphabetical conventions.
- [OWNER/REPO](https://github.com/OWNER/REPO) 📇 🏠 - Query example records through a locally runnable MCP server. [](https://glama.ai/mcp/servers/OWNER/REPO)Search for duplicates and inspect the diff
Search the base README for the repository URL, including a previous name or moved repository if relevant. A listing may exist under an unexpected category. When updating an existing record, explain the correction instead of presenting it as a new server.
Review the rendered Markdown and raw diff. Confirm that the primary link, badge image, and badge destination resolve correctly. Keep one server on one line and avoid incidental whitespace changes that make ordering hard to review.
# In your checkout of the awesome list:
rg -n -i "github\.com/OWNER/REPO" README.md
git diff --check
git diff -- README.mdKeep submission, merge, and visibility distinct
A successful PR creation gives you a review reference. It does not mean the entry is accepted. Inspect automated feedback and maintainer comments, update the same branch, and verify the merged README before calling the listing live.
MCP Server List’s local adapter verifies the versioned npm executable, source repository, installation instructions, real Glama evaluation, duplicate status and exact existing category before payment. It inserts the checked entry in the current sorted section and opens the PR through the operator’s contribution account after you authorize the scope. No fixed Other Tools placement or badge-pattern shortcut is sold. A remote-only service uses the separately checked remote-list route. A maintainer’s acceptance decision remains separate from a successful contribution request.
Use the remote list for a hosted service
The separate remote list evaluates a shared public endpoint rather than a local installation. A homepage, endpoint, authentication marker and actual healthy Glama connector evidence belong in that entry. The owner must explicitly attest public or public-signup availability; private and per-user services do not fit that scope.
The initial service adapter supports Streamable HTTP and checks its current operator prerequisites before charging. Follow the remote contribution guide and the exact free preflight report, rather than adapting a local repository line by simply replacing its URL.
Sources and scope
Primary documentation checked 2026-10-29. The workflow advice is MCP Server List’s editorial guidance; each destination controls its own current requirements and review.