MCP Server List

MCPServers.org listing requirements

A category-based MCP directory whose submission form accepts repository, website, or documentation links and an optional official registry name.

Prefilled — you submit: copy our checked values into the free form yourself; not part of the paid direct submissions. This action is separate from the qualifying submission minimum.

Managed browser free submissionSources checked

What to prepare

  • A name, exact category, short description and working repository, website or documentation link.
  • A maintained contact email and accurate remote-support declaration; a real registry name if one is supplied.
  • A configured and verified service-operated browser workflow for the directory’s free submission plan.

Prepare the form without inventing registry status

The official registry name field is optional. Supply the exact verified identity if you have published one; leave it empty if you have not. A planned namespace is not an existing registry record.

Choose the category that fits the server’s primary task, then describe a useful operation rather than a broad list of industries. The remote-support flag should reflect an endpoint users can actually connect to, not a future roadmap item.

Purchase only a verified executable route

The external form offers a free plan and an optional paid review option. MCP Server List does not implicitly purchase premium review, placement or advertising. Its own service fee authorizes only the displayed execution scope.

The browser route is blocked before payment unless the operator’s current workflow and confirmation checks are available. Login, CAPTCHA or changed form requirements must be surfaced as a blocker rather than turned into a manual task after charging.

Use a maintained contact route

Use an address you can monitor for review questions and future corrections. Preserve the submitted text alongside your release version, so a later maintainer can distinguish an outdated directory field from an application regression. Once public, check the record from the perspective of someone who has never seen the repository.

Submission workflow

  1. Check the external form and current free-plan scope before including this target.
  2. Run the free preflight; the route is unavailable unless the operator has verified and enabled its managed-browser execution path.
  3. Review the exact fields and authorize the launch only if the target is ready.
  4. A configured worker must submit the free workflow and retain actual confirmation evidence; premium review is never bought implicitly.

Blockers to resolve before review

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

  • The link fails to explain setup or represents a different server.
  • The description, category, or remote-support flag is inaccurate.
  • The owner cannot answer questions sent to the supplied contact address.

Primary sources

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

← Compare all destinations