Skip to main content
Glama
kevinlin

Spec-driven Development MCP Server

by kevinlin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Spec-driven Development MCP Server

No user-submitted related servers found.

    Related Servers

    • Vibe-Coder MCP Server

      crazyrabbitLTC
      A
      license
      D
      quality
      D
      maintenance
      An MCP server that implements a structured workflow for LLM-based coding, guiding development through feature clarification, documentation generation, phased implementation, and progress tracking.
      10
      44 npm
      18
      MIT

    • DevFlow MCP Server

      FaerberK
      A
      license
      B
      quality
      B
      maintenance
      MCP server that integrates DevFlow with AI code assistants to enforce structured development workflows including planning, task tracking, and code review gates.
      65
      31 npm
      1
      MIT

    • AgentPM

      gannonh
      A
      license
      Not graded
      quality
      C
      maintenance
      A planning and orchestration system for AI-driven software development that integrates as an MCP server, enabling developers to plan, prioritize, and execute complex projects with context-aware assistance.
      20 npm
      29
      MIT

    • Swarm Orchestrator

      Of-Arte
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that extends AI coding assistants with deterministic, algorithmic capabilities such as code analysis, fault localization, and formal verification, enabling an autonomous engineering team within the IDE.
      MIT

    • dev-loop-mcp

      soynog
      F
      license
      A
      quality
      D
      maintenance
      An MCP server that automates the full software development lifecycle through an AI-driven TDD state machine. It handles everything from task decomposition and test-driven development to integration testing and automated pull request creation.
      4
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose corresponding to a specific phase in the spec-driven development workflow. The naming convention with phase names (goal, requirements, design, tasks, execute) and action suffixes (_start, _confirmed) eliminates any ambiguity about which tool to use for which workflow step.

    Naming Consistency5/5

    All tools follow an identical pattern: 'spec_coding_' + [phase_name] + '_' + [action]. This consistent snake_case structure with predictable verb endings (_start, _confirmed) creates excellent predictability and readability across the entire tool set.

    Tool Count5/5

    With 9 tools, this server perfectly covers the complete spec-driven development lifecycle from workflow initiation through execution. Each tool represents a distinct phase transition, making the count well-scoped and appropriate for managing this structured development process.

    Completeness5/5

    The tool set provides complete coverage of the spec-driven development workflow, including all phase transitions from workflow start through execution. There are no gaps - every phase has both a start and confirmed tool, creating a complete, linear progression without dead ends for agents to follow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources