登录

servers

modelcontextprotocol活跃维护

Model Context Protocol 官方参考服务器集合，提供文件系统、Git、数据库等现成 MCP 服务实现，让 AI Agent 快速接入外部工具和数据源。

Model Context Protocol Reference Servers

v2.3.0发布于 2026-11-04 21:28 UTC91,898star +55 / 7 天11,932fork同步于 2026-11-10 05:17 UTC
MCP 服务器Agent 工具接入参考实现上下文协议TypeScript
对比 GitHub 官网

怎么上手

由 README 提炼，执行前请确认
原文 
npx -y @modelcontextprotocol/server-memory
uvx mcp-server-git
硬件要求按 README 说明

README 未说明，未提及显存、GPU 或 CPU 运行要求

下载：源码 zip·GitHub Releases（安装包）本站不镜像安装包

项目说明

由 README 自动翻译提炼
没人工点评？写下你的经验

MCP 官方参考服务器集合，演示如何让 LLM 安全受控地访问工具与数据源

Model Context Protocol 官方参考服务器集合，提供文件系统、Git、数据库等现成 MCP 服务实现，让 AI Agent 快速接入外部工具和数据源。

核心能力

  • 提供 Filesystem、Git、Fetch、Memory 等 7 个参考服务器
  • 覆盖 C#、Go、Java、Python、TypeScript 等 10 种官方 SDK 实现
  • 用 stdio 传输，由客户端以子进程方式拉起服务器
  • Everything 服务器额外支持 Streamable HTTP 传输
  • 可用 MCP Inspector 免客户端调试工具调用

容易踩的坑

这些服务器只是教学用参考实现，README 明确说明不适合直接用于生产；stdio 服务器启动后不监听端口、看似卡住是正常现象，需由 MCP 客户端配置拉起；Windows 上需用 cmd /c 包裹 npx 命令。

内容由模型根据 README 生成，可能不完整或不准确，以官方文档为准。看原文 README

最近发版

5 个版本v2.3.0
全部 release
  1. v2.3.0最新正式版2026-11-04 · 2026-11-04 21:28 UTC

    Packages

    PackageVersionRegistryIn this release
    @modelcontextprotocol/server-everything2.2.1npmpublished
    @modelcontextprotocol/server-filesystem2.2.0npmpublished
    @modelcontextprotocol/server-memory2.1.0npmpublished
    @modelcontextprotocol/server-sequential-thinking2.1.1npmpublished
    mcp-server-fetch2026.11.4PyPIpublished
    mcp-server-git2026.11.4PyPIpublished
    mcp-server-time2026.11.4PyPIpublished

    Release ledger: v2/chore/5425-release-v2.3.0

    @modelcontextprotocol/server-everything 2.2.1

    What's Changed

    @modelcontextprotocol/server-filesystem 2.2.0

    What's Changed

  2. v2.2.02026-10-28 · 2026-10-28 20:57 UTC
    查看更新说明

    Security: Node.js runtime and CA certificate updates (October 2026)

    On October 20, 2026, eMudhra disclosed that the private keys for eight of its intermediate CA certificates could be recovered from the public certificates. On October 21, Node.js shipped security releases that update its bundled CA certificates for the compromise and fix several unrelated high-severity runtime CVEs. On October 23, Python's certifi 2026.10.23 removed the eMudhra roots emSign Root CA - C1 and emSign ECC Root CA - C3.

    How these servers stand

    • The TypeScript servers rely on the Node.js runtime for certificate checks. They ship no CA certificates of their own. Only server-everything makes outbound HTTPS requests (gzip-file-as-resource), and the Node.js it runs on verifies them. server-filesystem, server-memory and server-sequential-thinking make no network connections.
    • mcp-server-fetch verifies HTTPS against the certifi bundle, through httpx. Installing from PyPI (uvx mcp-server-fetch, pip install mcp-server-fetch) resolves the current certifi, 2026.10.23 or later. The repository's fetch Dockerfile installs from its lockfile, which this release moves to certifi 2026.10.23 (#5341).
    • mcp-server-git and mcp-server-time make no network connections.

    If you run a TypeScript server from npm (npx or a global install)

    It runs on your Node.js, which we can't update for you. Please run Node.js 24.22.1 or 26.12.1, or later, and check with node --version. The packages' engines field accepts any Node.js 24, so npm won't warn you about an older, unpatched runtime.

    If you run mcp-server-fetch from an existing environment

    An environment created before October 23 keeps its older certifi. Refresh it with uvx --refresh mcp-server-fetch, or pip install -U certifi.

    Packages

    PackageVersionRegistryIn this release
    @modelcontextprotocol/server-everything2.1.0npmpublished
    @modelcontextprotocol/server-filesystem2.1.0npmpublished
    @modelcontextprotocol/server-memory2.0.1npmpublished
    @modelcontextprotocol/server-sequential-thinking2.0.0npmunchanged
    mcp-server-fetch2026.10.28PyPIpublished
    mcp-server-git2026.10.28PyPIpublished
    mcp-server-time2026.10.28PyPIpublished

    Release ledger: v2/chore/5330-release-v2.2.0

    @modelcontextprotocol/server-everything 2.1.0

    What's Changed

    @modelcontextprotocol/server-filesystem 2.1.0

    What's Changed

    • fix(filesystem): accept a case-only respelling of an allowed direc
  3. v2.1.02026-10-25 · 2026-10-25 00:03 UTC
    查看更新说明

    Security fixes

    v2.1.0 fixes eight vulnerabilities in three servers. Upgrade @modelcontextprotocol/server-filesystem and @modelcontextprotocol/server-everything to 2.0.1, and mcp-server-fetch to 2026.10.24.

    PackageAffectedFixed in
    @modelcontextprotocol/server-filesystem1.0.0 through 2.0.0, and date versions through 2026.8.312.0.1
    @modelcontextprotocol/server-everything1.0.0 through 2.0.0, and date versions 2025.9.24 through 2026.8.312.0.1
    mcp-server-fetchthrough 2026.10.192026.10.24

    @modelcontextprotocol/server-filesystem 2.0.1

    • Writes stay inside the directory that was checked (Linux and macOS). A parent directory swapped for a symlink between the access check and the write can no longer redirect write_file, edit_file, create_directory or the move_file destination outside the allowed directories. On Windows this is only partly fixed; the advisory says what is still exposed and how to configure around it (GHSA-53mr-w429-c597)
    • Paths are checked exactly as they are used. The access check no longer strips a trailing quote or whitespace that the file operation keeps, so a sibling directory named after an allowed one with that suffix is no longer reachable (GHSA-7rgq-gccq-qphx)
    • A symlink spelled in a different letter case no longer passes the symlink check for a new path on a case-insensitive volume, such as macOS's default. This was a regression in 2026.8.31 (GHSA-4gxg-m5jx-9j57)
    • list_directory_with_sizes checks each entry before reading its size, so a symlink inside an allowed directory no longer reveals the size and modification time of a file outside it (GHSA-hhwq-wxfx-cj7g)

    @modelcontextprotocol/server-everything 2.0.1

    • The HTTP and SSE transports refuse requests from other web origins. They now check the Origin header and no longer send Access-Control-Allow-Origin: *, so a web page the user visits can no longer call the server's tools (such as get-env) or read their results (GHSA-mvf5-2qqv-rg3c)

    mcp-server-fetch 2026.10.24

    • The address check and the connection use the same host name. For an internationalized (IDNA) host name, the server used to check one form of the name and connect to another, which could reach an internal address (GHSA-v38p-wf49-hx2j)
    • NAT64 addresses are judged by the IPv4 address they carry. An address in 64:ff9b::/96 that wraps a private, loopback or link-local IPv4 address is now refused, as an IPv4-mapped one already was (GHSA-66qx-2266-pmj6)
    • robots.txt is checked again after every redirect, not only for the URL first requested (GHSA-3jqg-r5pp-rmp2)

    Upgrading from a date-versioned npm release

    The TypeScript servers moved from date versions (2025.x, 2026.x) to semantic versions in 1.0.0. Package managers rank 2.0.1 below every 2025.x and 2026.x version, so they won't offer it as an upgrade. If you are on a date version, install 2.0.1 explicitly, for example npm install @modelcontextprotocol/[email protected].

    Packages

    PackageVersionRegistryIn this release
    @modelcontextprotocol/server-everything2.0.1npmpublished
  4. v2.0.02026-10-19 · 2026-10-19 06:46 UTC
    查看更新说明

    Servers refactored to modern era

    This release refactors all the servers to support the modern era spec, while still answering legacy era clients as expected.

    Packages

    PackageVersionRegistryIn this release
    @modelcontextprotocol/server-everything2.0.0npmpublished
    @modelcontextprotocol/server-filesystem2.0.0npmpublished
    @modelcontextprotocol/server-memory2.0.0npmpublished
    @modelcontextprotocol/server-sequential-thinking2.0.0npmpublished
    mcp-server-fetch2026.10.19PyPIpublished
    mcp-server-git2026.10.19PyPIpublished
    mcp-server-time2026.10.19PyPIpublished

    Release ledger: v2/chore/5159-release-v2.0.0

    @modelcontextprotocol/server-everything 2.0.0

    What's Changed

    @modelcontextprotocol/server-filesystem 2.0.0

    What's Changed

  5. v1.0.02026-10-11 · 2026-10-11 02:40 UTC
    查看更新说明

    Final Legacy Server Release

    This release contains many bug and security fixes, and represents the final release of the legacy era servers.

    Packages

    PackageVersionRegistryIn this release
    @modelcontextprotocol/server-everything1.0.0npmpublished
    @modelcontextprotocol/server-filesystem1.0.0npmpublished
    @modelcontextprotocol/server-memory1.0.0npmpublished
    @modelcontextprotocol/server-sequential-thinking1.0.0npmpublished
    mcp-server-fetch2026.10.10PyPIpublished
    mcp-server-git2026.10.10PyPIpublished
    mcp-server-time2026.10.10PyPIpublished

    Release ledger: v2/chore/5080-release-v1.0.0-sdk1

    @modelcontextprotocol/server-everything 1.0.0

    What's Changed

    @modelcontextprotocol/server-filesystem 1.0.0

    What's Changed

用户点评

登录用户的真实使用记录，可按版本和硬件筛选
共 0 条

    还没有人点评。第一个说出真实体验的人最有价值。

    README 原文

    未翻译
    在 GitHub 打开

    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.

    • Everything - Reference / test server with prompts, resources, and tools.
    • Fetch - Web content fetching and conversion for efficient LLM usage.
    • Filesystem - Secure file operations with configurable access controls.
    • Git - Tools to read, search, and manipulate Git repositories.
    • Memory - Knowledge graph-based persistent memory system.
    • Sequential Thinking - Dynamic and reflective problem-solving through thought sequences.
    • Time - Time and timezone conversion capabilities.

    Archived

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

    • AWS KB Retrieval - Retrieval from AWS Knowledge Base using Bedrock Agent Runtime.
    • Brave Search - Web and local search using Brave's Search API. Has been replaced by the official server (@brave/brave-search-mcp-server).
    • EverArt - AI image generation using various models.
    • GitHub - Repository management, file operations, and GitHub API integration.
    • GitLab - GitLab API, enabling project management.
    • Google Drive - File access and search capabilities for Google Drive.
    • Google Maps - Location services, directions, and place details.
    • PostgreSQL - Read-only database access with schema inspection.
    • Puppeteer - Browser automation and web scraping.
    • Redis - Interact with Redis key-value stores.
    • Sentry - Retrieving and analyzing issues from Sentry.io.
    • Slack - Channel management and messaging capabilities. Now maintained by Zencoder
    • SQLite - Database interaction and business intelligence capabilities.

    🚀 Getting Started

    Using MCP Servers in this Repository

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

    For example, this will start the Memory server:

    npx -y @modelcontextprotocol/server-memory

    Python-based servers in this repository can be started 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"]
    },
    "fetch": {
      "command": "uvx",
      "args": ["mcp-server-fetch"]
    }
  }
}

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

    Transports: stdio and Streamable HTTP

    An MCP server talks to its client over a transport. The protocol defines two standard ones, and they run very differently:

    TransportHow the server runsHow a client reaches it
    stdioThe client launches the server as a subprocess and talks to it over the process's stdin and stdout. The server opens no port.A command and args in the client's configuration, as in the examples above
    Streamable HTTPThe server runs on its own as an HTTP service, and can serve many clientsA URL, such as http://localhost:3001/mcp

    Every server in this repository serves stdio, and only Everything also serves Streamable HTTP (its README shows how to start it that way, and covers its deprecated HTTP+SSE transport too). So when you run uvx mcp-server-git or npx -y @modelcontextprotocol/server-memory in a terminal, it opens no port, prints at most a one-line startup notice, and then appears to hang. That is expected: it is waiting for a client to send it messages on stdin. You do not normally start a stdio server yourself; your MCP client starts it from its configuration and stops it when it is done.

    To try a server without setting up a client, use the MCP Inspector. Given a stdio server's command, it launches the server for you and lets you browse and call its tools; given a URL, it connects to a running Streamable HTTP server:

    # A stdio server: the Inspector launches it
npx @modelcontextprotocol/inspector uvx mcp-server-git

# A Streamable HTTP server: start it first, then connect to its URL
npx @modelcontextprotocol/server-everything streamableHttp
npx @modelcontextprotocol/inspector --transport http --server-url http://localhost:3001/mcp

    For more, see the transport layer in the MCP architecture overview, and Transports in the specification.

    🛠️ 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!

    相关项目

    同分类里 star 最高的项目
    对比全部 →
    n8n
    n8n-io·TypeScript

    可视化搭建工作流并支持自定义代码的自动化平台，内置 AI 能力，提供 400+ 集成，可自托管或上云，用来把各类 API 和数据流串起来。

    工作流自动化+4MCP 生态
    209960+22861kstable2026-11-10 04:58 UTC
    Scrapling
    D4Vinci·Python

    Python 网页抓取框架，从单次请求到大规模爬取都能处理，内置 Playwright 支持，还提供 MCP 服务方便接入 AI 工作流。

    网页抓取+4MCP 生态
    100680+170411kv0.5.12026-11-09 10:36 UTC
    awesome-mcp-servers
    punkpeye

    一份精选的 MCP 服务器清单，帮你在接入 Model Context Protocol 生态时快速找到可用的服务端实现。

    MCP 服务器+3MCP 生态
    97546+14320k2026-11-06 17:59 UTC
    worldmonitor
    koala73·TypeScript

    实时全球情报仪表盘，用 AI 聚合新闻、监控地缘政治与基础设施动态，把分散信息整合进统一的态势感知界面。

    态势感知+4MCP 生态
    90426+13614kv2.11.82026-11-10 05:10 UTC