What it contains
Official MCP steering-group reference servers: Everything, Fetch, Filesystem, Git, Memory, Sequential Thinking, and Time.
Typical uses
Study/test/bootstrap MCP implementations; README explicitly warns these are educational references, not production-ready solutions.
Why people choose it
Documented choice: first-party protocol examples; do not select as an unmodified production service.
LicenseApache-2.0 new contributions; existing code may be MIT
Last meaningful updateUnknown
Production readinessprototype
Classification
Subject domains
MCPagent toolsprotocol development
Task categories
MCPagent toolsprotocol development
Project phases
implementationoperations
Secondary types
reference implementationsmonorepo
Select when
- Need MCP reference implementation/testing
Do not select when
- Need production-ready third-party integration
- Need comprehensive server directory
Implementation complexitymedium
Routing heuristic 80.0%
Security boundary clarity
5/5 First-party routing documentation
5/5 Strengths
None documented.
Poor-fit scenarios
- Need production-ready third-party integration
- Need comprehensive server directory
Limitations
None documented.
src/everything
Feature/test server.
promptsresourcestools
src/fetch
Web fetch/conversion.
web
src/filesystem
Controlled file operations.
files
src/git
Git repository tools.
git
src/memory
Knowledge-graph memory.
memory
src/sequentialthinking
Reflective problem-solving tool.
reasoning
src/time
Time/timezone conversion.
time
FrameworksNone documented
Operating systemsNone documented
Installation methodsNone documented
Required credentialsNone documented
External servicesNone documented
Major dependenciesNone documented
Compatibility notes
None documented.
One-sentence semantic summary
Official MCP steering-group reference servers: Everything, Fetch, Filesystem, Git, Memory, Sequential Thinking, and Time.
Capability keywords
MCP prompts/resources/toolsfetchfilesystemgitmemorytimesequential thinking
User intent phrases
- Need MCP reference implementation/testing
Negative match phrases
- Need production-ready third-party integration
- Need comprehensive server directory
Differentiators
None documented.
Security considerations
- Implement safeguards for your threat model; reference servers are not production-ready.
Privacy considerations
None documented.
Uncertainty
Unresolved items
None documented.
Inference notes
None documented.
Repository usage guidance
installation summaryUnknown
basic usage summaryStudy/test/bootstrap MCP implementations; README explicitly warns these are educational references, not production-ready solutions.
documented entry pointsNone documented
key configuration filesNone documented
important directoriessrc/
documentation pathsREADME.md, ADDITIONAL.md, SECURITY.md
example pathsNone documented
Relationships
complementary
high
Official reference implementations versus discovery catalog.
Recommended combinations
MCP development/discovery high
Each repository covers a distinct layer; avoid combining tools that duplicate lifecycle ownership.
Order of operations
- Study reference-server patterns
- Define threat/auth model
- Select and verify production integration separately
Routing rules
rule_042: Need MCP reference implementation/testing P958
Rationale
Official MCP steering-group reference servers: Everything, Fetch, Filesystem, Git, Memory, Sequential Thinking, and Time.
Required conditions
None documented.
Preferred
modelcontextprotocol/servers
Fallback
None