servers README

The project's README from github.com/modelcontextprotocol/servers. As one markdown file: README.md.

Model Context Protocol servers

This repository is a collection of reference implementations for the Model Context Protocol (MCP), as well as references to community-built servers and additional resources.

[!IMPORTANT] If you are looking for a list of MCP servers, you can browse published servers on the MCP Registry. The repository served by this README is dedicated to housing just the small number of reference servers maintained by the MCP steering group.

[!WARNING] The servers in this repository are intended as reference implementations to demonstrate MCP features and SDK usage. They are meant to serve as educational examples for developers building their own MCP servers, not as production-ready solutions. Developers should evaluate their own security requirements and implement appropriate safeguards based on their specific threat model and use case.

The servers in this repository showcase the versatility and extensibility of MCP, demonstrating how it can be used to give Large Language Models (LLMs) secure, controlled access to tools and data sources. Typically, each MCP server is implemented with an MCP SDK:

🌟 Reference Servers

These servers aim to demonstrate MCP features and the official SDKs.

Archived

The following reference servers are now archived and can be found at servers-archived.

🚀 Getting Started

Using MCP Servers in this Repository

TypeScript-based servers in this repository can be used directly with npx.

For example, this will start the Memory server:

npx -y @modelcontextprotocol/server-memory

Python-based servers in this repository can be used directly with uvx or pip. uvx is recommended for ease of use and setup.

For example, this will start the Git server:

# With uvx
uvx mcp-server-git

# With pip
pip install mcp-server-git
python -m mcp_server_git

Follow these instructions to install uv / uvx and these to install pip.

Using an MCP Client

However, running a server on its own isn't very useful, and should instead be configured into an MCP client. For example, here's the Claude Desktop configuration to use the above server:

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-memory"]
    }
  }
}

On Windows, wrap npx with cmd /c:

{
  "mcpServers": {
    "memory": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-memory"]
    }
  }
}

Additional examples of using the Claude Desktop as an MCP client might look like:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/allowed/files"]
    },
    "git": {
      "command": "uvx",
      "args": ["mcp-server-git", "--repository", "path/to/git/repo"]
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    },
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres", "postgresql://localhost/mydb"]
    }
  }
}

On Windows, apply the same wrapper to each npx-based entry above by changing "command" to "cmd" and prepending "/c", "npx" to the existing args. Leave uvx entries unchanged.

🛠️ Creating Your Own Server

Interested in creating your own MCP server? Visit the official documentation at modelcontextprotocol.io for comprehensive guides, best practices, and technical details on implementing MCP servers.

📚 Learn More

See ADDITIONAL.md for a curated list of frameworks and resources that simplify building MCP servers and clients.

🤝 Contributing

See CONTRIBUTING.md for information about contributing to this repository.

📦 Releasing

See RELEASING.md for how packages are published (OIDC trusted publishing from CI — no registry tokens) and how to retry a failed publish.

🔒 Security

See SECURITY.md for reporting security vulnerabilities.

📜 License

This project is licensed under the Apache License, Version 2.0 for new contributions, with existing code under MIT - see the LICENSE file for details.

💬 Community

⭐ Support

If you find MCP servers useful, please consider starring the repository and contributing new servers or improvements!


Managed by Anthropic, but built together with the community. The Model Context Protocol is open source and we encourage everyone to contribute their own servers and improvements!

servers (modelcontextprotocol/servers)

Searching Database…

91.3K ·GitHub
这是什么?这是 Model Context Protocol(MCP)的参考服务器实现合集,展示如何让大语言模型安全、可控地访问工具和数据源。
这是一个应用,还是多个独立的服务器?这是一个单体仓库(monorepo),包含多个相互独立的参考服务器(Everything、Fetch、Filesystem、Git、Memory、Sequential Thinking、Time),每个都基于 TypeScript 或 Python 的 MCP SDK 构建。
怎么运行其中某个服务器?基于 TypeScript 的服务器直接用 npx 运行(例如启动 Memory 服务器),基于 Python 的服务器用 uvx 或 pip 运行(例如启动 Git 服务器);然后把该服务器接入 Claude Desktop 等 MCP 客户端即可。
使用这些服务器需要先安装什么?TypeScript 服务器需要 Node.js(用于 npx),Python 服务器需要 uv/uvx(或 pip),此外还需要 Claude Desktop 等兼容 MCP 的客户端来实际调用它们。
这些服务器可以直接用于生产环境吗?不可以。维护者明确表示这些是用于教学的参考实现,并非为生产环境准备,并建议开发者在实际使用前先评估自身的安全需求。
在 Windows 上的设置有什么不同?有不同。在 Windows 上,需要在客户端配置中用 'cmd /c' 包裹基于 npx 的条目,而基于 uvx 的 Python 条目保持不变。
Everything 服务器是做什么的?它是一个参考/测试服务器,集合了提示词、资源和工具,主要用于端到端地测试和演示 MCP 的各项功能。
GitHub、Slack、PostgreSQL 等服务器为什么被归档?它们被移至单独的 servers-archived 仓库,其中几个已由官方维护的同类服务取代(例如 Brave Search 改由其厂商自己的 MCP 服务器提供,Slack 现由 Zencoder 维护)。
如何使用这个仓库构建我自己的 MCP 服务器?可以参考 modelcontextprotocol.io 上的官方文档了解指南和最佳实践,并搭配官方 SDK 使用(支持 TypeScript、Python、Go、Java、Kotlin、PHP、Ruby、Rust、Swift 和 C#)。
Size
31.2 MB
Stars
91.3K
Age
1y
Commits · 90 Days