Skip to main content
Glama
sdlc-workflow-mcp

sdlc-workflow-mcp

by Tingsum26

Related Servers

Alternatives to sdlc-workflow-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents and humans to collaborate on local, evidence-driven planning by exposing MCP tools for plan listing and binding, workflow catalog/run operations, and task tracking with human-reviewed decisions.
      2
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code to delegate tasks to persistent GitHub Copilot CLI sessions via MCP, inspect pending tool requests, and approve each operation once or deny it while continuing multi-turn context. It bridges ACP runtime sessions locally over stdio without a public service or background daemon.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI clients over MCP stdio to run local-first, auditable multi-model workflows that draft, require structured review, and revise outputs on demand, with BYOK credential handling and no telemetry. Exposes tools for listing workflows, running cancellable workflows with step-level progress, and retrieving run summaries.
      3
      1,323 npm
      1
      MIT

    TDQS

    C2.7/5.0

    Scored across 42 tools

    Disambiguation3/5

    While most tools have distinct verbs and resources, there is overlap among the many graph/onboarding/analysis tools (e.g., workflow_get_repository_graph, workflow_get_journey_graph, workflow_analyze_journey, workflow_analyze_http_dependencies) and between workflow_ticket_advance and advance_repo_task. Descriptions help clarify, but the sheer number of similar read/analysis operations could still lead to misselection.

    Naming Consistency3/5

    All names use snake_case, but the ordering is inconsistent: some follow workflow_<entity>_<action> (workflow_epic_create) while others follow workflow_<action>_<object> (workflow_get_task_context). One tool (advance_repo_task) also lacks the workflow_ prefix, making the convention mixed though still readable.

    Tool Count2/5

    42 tools far exceeds the 3-15 sweet spot and the rubric's 25+ threshold for 'too many,' making the surface heavy even for a complex SDLC domain. While each tool may have a distinct purpose, the volume increases cognitive load and selection risk.

    Completeness4/5

    The set covers a broad SDLC workflow lifecycle: epic/ticket/task creation, advancement, approvals, artifacts, decisions, blockers, onboarding, graphs, diagnostics, and identity. Some gaps exist (e.g., no explicit list/get for epics or tickets beyond task context), but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data