mirror of https://github.com/modelcontextprotocol/servers.git synced 2026-04-17 21:54:05 +02:00

Files

olaservo 5914f61340 docs: retire third-party server list in favor of MCP Registry

The Third-Party Servers section (Official Integrations + Community
Servers) has been superseded by the MCP Registry at
https://registry.modelcontextprotocol.io/. The README already carried a
deprecation note and CONTRIBUTING.md froze new additions. This removes
the list, updates CONTRIBUTING.md to describe the new state, and
refreshes the readme-pr-check workflow's bot comment.

2026-04-14 08:05:23 -07:00

2.6 KiB

Raw Blame History

Contributing to MCP Servers

Thanks for your interest in contributing! Here's how you can help make this repo better.

We accept changes through the standard GitHub flow model.

Server Listings

The README no longer contains a list of third-party MCP servers — that list has been retired in favor of the MCP Server Registry. To make your server discoverable, follow the quickstart guide to publish it there.

You can browse published servers at https://registry.modelcontextprotocol.io/.

Server Implementations

We welcome:

Bug fixes — Help us squash those pesky bugs.
Usability improvements — Making servers easier to use for humans and agents.
Enhancements that demonstrate MCP protocol features — We encourage contributions that help reference servers better illustrate underutilized aspects of the MCP protocol beyond just Tools, such as Resources, Prompts, or Roots. For example, adding Roots support to filesystem-server helps showcase this important but lesser-known feature.

We're more selective about:

Other new features — Especially if they're not crucial to the server's core purpose or are highly opinionated. The existing servers are reference servers meant to inspire the community. If you need specific features, we encourage you to build enhanced versions and publish them to the MCP Server Registry! We think a diverse ecosystem of servers is beneficial for everyone.

We don't accept:

New server implementations — We encourage you to publish them to the MCP Server Registry instead.

Testing

When adding or configuring tests for servers implemented in TypeScript, use vitest as the test framework. Vitest provides better ESM support, faster test execution, and a more modern testing experience.

Documentation

Improvements to existing documentation is welcome - although generally we'd prefer ergonomic improvements than documenting pain points if possible!

We're more selective about adding wholly new documentation, especially in ways that aren't vendor neutral (e.g. how to run a particular server with a particular client).

Community

Learn how the MCP community communicates.

Thank you for helping make MCP servers better for everyone!

2.6 KiB Raw Blame History