11st of 1 in MCP servers
servers
Reference MCP servers for files, git, fetch, memory and time
Documentation ↗
(opens in a new tab)Website ↗
(opens in a new tab)Repository on GitHub ↗
(opens in a new tab)
- Stars
- 91.7k
- License
- custom license
- Last commit
- Oct 2026
- Last release
- Oct 2026
- Language
- TypeScript
82,317 on 10 Apr 202691,732 on 30 Oct 2026
From GitHub's daily star counts.
Checked on GitHub.
Overview
Official collection of reference Model Context Protocol servers maintained by the MCP steering group: Everything, Fetch, Filesystem, Git, Memory, Sequential Thinking and Time. TypeScript servers start with npx and Python ones with uvx or pip. All serve stdio; only Everything also serves Streamable HTTP. The README states they are educational examples, not production-ready.
Who it is for: Developers learning MCP or wiring basic tools into an MCP client
Strengths
- Maintained by the MCP steering group, so it tracks the spec and official SDKs
- Seven small servers covering files, git, web fetch, knowledge-graph memory and time
- Starts with one command: npx for TypeScript servers, uvx or pip for Python ones
- Everything server exercises prompts, resources and tools, and also serves Streamable HTTP
Weaknesses
- README says these are reference implementations, not production-ready
- Only Everything supports Streamable HTTP; the other servers are stdio only
- Many earlier servers (GitHub, Postgres, Slack, Redis and others) are archived
- License is reported as NOASSERTION: Apache-2.0 for new contributions, MIT for older code
What it needs
- no GPU
- Needs Node.js (npx), uv or pip (Python servers), MCP client
Quick answers
Is servers open source?
Its code is public on GitHub under its own license terms; read them before you use it at work.
Does servers need a GPU?
No, it runs without one.