modelcontextprotocol/servers

• **Archetype**: domain-skill-pack
• **Stars**: 83,628
• **Last pushed**: 2026-03-29
• **License**: Apache-2.0 (transitioning from MIT)
• **Discovered**: 2026-04-13
• **Source**: backlog evaluation
• **Skills found**: 0 (no SKILL.md files, but comprehensive MCP server reference implementations)

Summary

Official collection of reference MCP server implementations showcasing SDK usage patterns across multiple languages. Contains 7+ server implementations (filesystem, git, memory, fetch, everything, sequentialthinking, time) with detailed documentation of API design, security patterns, tool annotations, and deployment configurations. Serves as the canonical reference for MCP server development patterns.

Assessment

Extremely high transferable value for babysitter's MCP integration surface. Each server implementation documents comprehensive development patterns: API design with proper input/output schemas, tool annotation patterns (readOnly/idempotent/destructive hints), security models (directory access controls, sandboxing), deployment patterns (Docker/NPX), and client integration (Claude Desktop, VS Code). The filesystem server alone contains 12+ documented tools with detailed patterns for file operations, directory traversal, and access control that map directly to babysitter process specializations.

Extraction Priority

• High
• Rationale: Direct relevance to babysitter's MCP integration. Contains canonical patterns from the protocol maintainers for server development, security, deployment, and client integration. Multiple extractable processes for MCP server development workflow.

Skills Inventory

Processes

- Source: src/filesystem/README.md (comprehensive reference implementation) - Placement: specializations/devx/mcp-server-development - Inputs/Outputs: Server spec → Deployed MCP server with client configs - Complexity: moderate - Notes: Covers full lifecycle from tool definitions through production deployment

• **MCP Server Development Workflow**: Multi-phase process for creating MCP servers (API design, tool implementation, security model, testing, deployment)

- Source: src/filesystem/README.md (tool annotations section, API documentation) - Placement: specializations/devx/mcp-tool-design - Inputs/Outputs: Tool requirements → Tool implementation with MCP hints - Complexity: simple - Notes: Includes readOnly/idempotent/destructive hint patterns, input validation, error handling

• **MCP Tool Design Process**: Systematic approach to designing MCP tool interfaces with proper annotations and security

- Source: src/filesystem/README.md (directory access control section) - Placement: specializations/security-compliance/mcp-security - Inputs/Outputs: Security requirements → Sandboxed MCP server with access controls - Complexity: moderate - Notes: Command-line args vs dynamic roots, path validation, permission management

• **MCP Security Model Implementation**: Process for implementing directory access controls and sandboxing

- Source: src/filesystem/README.md (usage sections), Dockerfile patterns - Placement: specializations/devx/mcp-deployment - Inputs/Outputs: MCP server implementation → Client-ready deployment configs - Complexity: simple - Notes: Docker vs NPX packaging, Claude Desktop/VS Code integration configs

• **MCP Deployment Pipeline**: Process for packaging and deploying MCP servers with multiple client integrations

Plugin Ideas

- What install.md would do: Interview user about server purpose, detect preferred language/SDK, scaffold server structure with tool definitions, security model, Docker/NPX configs, and client integration files - Processes it would copy: mcp-server-development, mcp-tool-design, mcp-security, mcp-deployment - Configs/hooks it would create: package.json, Dockerfile, tsconfig.json, MCP client configs for Claude Desktop/VS Code - Source evidence: Comprehensive reference implementations with documented patterns for all aspects of MCP server development

• **MCP Server Builder**: Plugin that scaffolds MCP servers following canonical patterns, with tool generation, security model setup, and client integration configs

- What install.md would do: Analyze existing MCP usage, enhance tool annotations, add security patterns, improve client integration configs - Processes it would copy: mcp-tool-design, mcp-security - Configs/hooks it would create: Enhanced MCP server configs, client integration improvements - Source evidence: Advanced tool annotation patterns and security models from reference implementations

• **DevX Enhancement**: MCP integration improvement plugin that extends babysitter's mcp:serve surface with reference implementation patterns

Harness Integration Ideas

N/A - This is not a harness framework repository.

Implicit Procedural Knowledge

- Source: Filesystem tool annotations table and implementation patterns - Placement: specializations/devx/mcp-tool-design - Why codify: Ensures consistent tool behavior expectations across MCP servers, improves client UX - Sketch: Analyze tool behavior → Assign appropriate hints → Document guarantees → Implement validation

• **MCP Tool Annotation Strategy**: Systematic approach to marking tools with readOnly/idempotent/destructive hints

- Source: Directory access control documentation in filesystem server - Placement: specializations/security-compliance/mcp-security - Why codify: Reusable security pattern for any resource-bounded MCP server - Sketch: Define access boundaries → Implement roots protocol → Handle runtime updates → Validate access on operations

• **Dynamic Access Control Pattern**: Process for implementing flexible directory/resource access via MCP Roots protocol

- Source: Usage sections covering Claude Desktop, VS Code, Docker, NPX deployment patterns - Placement: specializations/devx/mcp-deployment - Why codify: Standardizes deployment across different MCP client ecosystems - Sketch: Package server → Generate client configs → Test integration → Document installation

• **Multi-Client Deployment Strategy**: Process for packaging MCP servers for multiple client environments

Library Mapping

Plugin Marketplace Mapping