Skip to main content
Glama
SergioRodas

mcp-dev-workflow

by SergioRodas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-dev-workflow

No user-submitted related servers found.

    Related Servers

    • 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
      66 npm
      1
      MIT

    • devflow-mcp

      boranesn
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server that provides AI assistants with comprehensive GitHub developer tooling including PR analysis, code review, changelog generation, dependency auditing, commit summarization, and refactoring suggestions.
      10 npm
      ISC

    • mcp-review-pr

      thangtn83
      F
      license
      A
      quality
      D
      maintenance
      An MCP server for multi-language PR review with deterministic analysis, providing AI-powered code review tools that detect languages, apply review guidelines, and run quality checks.
      7
      -
    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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct stage of the development workflow: branch name generation, commit message validation/normalization, and PR checklist construction. There is no overlap in purpose, so an agent can easily select the right tool based on the task.

    Naming Consistency5/5

    All tool names follow the same lowercase_with_underscore pattern and are noun phrases indicating the artifact they handle: branch_name, commit_message, pr_checklist. This consistent convention makes the API predictable and easy to navigate.

    Tool Count5/5

    With only three tools, the server is tightly scoped to a specific development workflow without unnecessary clutter. Each tool serves a clear, non-redundant purpose within that scope, making the count appropriate for the server's stated function.

    Completeness4/5

    The tools cover the essential lifecycle of a conventional development workflow: creating a branch, validating commit messages, and assembling a pull request. A minor gap is the lack of a tool to generate a commit message from a diff, but the validation tool provides sufficient coverage for enforcing conventions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources