A
licenseNot graded
qualityA
maintenanceEnables MCP clients to search, retrieve, and validate portable SKILL.md files through skill resources and read-only tools.
1,464 PyPI
1
MIT
sdd-mcp-server
by manoel-6163
Related Servers
Alternatives to sdd-mcp-server
No user-submitted related servers found.
Related Servers
craftbag-mcpofficial
AlicenseNot gradedqualityAmaintenanceEnables MCP hosts to discover, list, load, explain, and validate Agent Skills (SKILL.md) from project and home skill trees. Hosts can filter, rank, and load skills without depending on any one agent product.2MIT- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to discover, search, and load Agent Skills stored as SKILL.md files without rebuilding, and to read text resources or preview/stage proposed edits for review.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to browse and use a directory of SKILL.md skills, collect feedback and run traces, and manage recipes over stdio or authenticated HTTP.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that unifies and synchronizes AI coding skills across multiple tools, exposing skill discovery and retrieval via list_skills and read_skill.79 npm14MIT
- AlicenseAqualityDmaintenanceExposes Cursor-style skill packs (SKILL.md trees) via MCP resources, tools, and prompts, enabling any MCP client to list, get, search skills, and retrieve skill context.320 npmISC
TDQS
C2.8/5.0
Scored across 16 tools
Disambiguation4/5
Most tools target a clearly distinct stage or artifact (spec-init, spec-requirements, spec-design, spec-tasks, spec-approve, spec-impl). The main overlap is spec-status vs spec-feedback, both of which surface progress/status information, and the three validate_* tools differ only by target. Descriptions largely resolve these ambiguities.
Naming Consistency2/5
The set mixes two conventions: snake_case (list_specs, get_skill, validate_spec, prepare_generation_context) and kebab-case (spec-init, spec-requirements, validate-design, validate-gap), plus a bare noun 'steering'. While the spec-* family is internally consistent, the overall pattern is unpredictable.
Tool Count3/5
16 tools is borderline-heavy for a spec-driven-development server. Many serve a genuine lifecycle stage, but the validate_* trio and the status/feedback pair feel partially redundant, suggesting some tools could be consolidated.
Completeness4/5
The surface covers the full spec lifecycle: init, requirements, design, tasks, approval, implementation prep, status, feedback, plus skills/steering and validation. Minor gaps around editing/versioning of specs exist, but core CRUD-style workflows are covered without dead ends.
Maintenance
ActivitySlowing
ResponsivenessNo issues