MCP Server List

Submit to Awesome MCP Servers

Contribute an installable public GitHub server to punkpeye’s curated Markdown list through a reviewed pull request.

Open a reviewed npm/stdio list contribution PR. Eligibility is checked before purchase.

Checked local-server contribution PRSources checked

What to prepare

  • A real versioned npm/stdio release with an executable package, matching source repository and accurate install_instructions.
  • An evaluated Glama server record, or selected Glama verification in the same launch with this target explicitly conditional on its evaluation.
  • The exact existing README category, a correctly formed entry and no duplicate source repository.
  • The service operator’s verified public-contribution identity and available execution worker.

A contribution to a maintained list

The useful unit here is one repository entry, not a product landing page. Describe the task the server enables and its runtime accurately. Choose tags because they help someone install the right software; an official-implementation marker needs a real relationship to the underlying service.

Read both CONTRIBUTING.md and the current validation workflow. Repository automation can enforce details beyond the prose contribution guide. This target currently checks Glama badges, names, emoji tags, duplicates, and the primary GitHub link.

Complete the Glama prerequisite before the quote

An attractive badge URL is easy to generate and proves little on its own. The full preflight checks the actual matching Glama server record, completed evaluation, discoverability and inspected tools. If those are missing, the awesome-list target is blocked before payment.

The entry is placed in the exact existing category you select and checked against current ordering and duplicate rules. There is no fixed Other Tools shortcut. A source that is only a hosted service belongs in the separate remote-server list.

Follow the review through

Record the PR URL and inspect checks and comments. Fix the same branch when changes are requested instead of opening another PR. Only mark a listing as live after verifying that the merged README contains the intended repository link. Acceptance and review timing belong to the maintainers.

Submission workflow

  1. Verify the released package and static requirements; inspect any disclosed wait for a selected Glama evaluation before including this target.
  2. Choose the exact current category and inspect the generated entry and sorted placement during free preflight.
  3. Authorize the checked launch; the service creates its contribution branch and PR after payment.
  4. Follow PR state and feedback. Only verified merged content establishes that the entry is in the maintained list.

Blockers to resolve before review

Use these as preparation checks. The destination makes its own acceptance decision.

  • A duplicate repository, non-GitHub primary URL, or remote-only server is submitted to this list.
  • The entry lacks an evaluated Glama score badge, uses an unsupported emoji, or omits owner/repo naming.
  • The category, ordering, formatting, or description needs a maintainer-requested correction.

Primary sources

Checked 2026-10-29. Follow the destination’s current instructions if its requirements change.

← Compare all destinations