Skip to main content
Glama
saakshigupta2002

PR Orchestrator MCP

by saakshigupta2002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to PR Orchestrator MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      5 npm
      ISC

    • Git PR MCP Server

      peterj
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables Git repository operations and GitHub PR workflows, allowing users to manage repositories, create branches, commit changes, and create pull requests through natural language.
      2
      -

    • RepoPilot

      wellkilo
      A
      license
      A
      quality
      A
      maintenance
      MCP server for auditable repository self-maintenance, turning GitHub issues and failed CI into independently verified pull requests with full audit trails, human approvals, and runbook archival.
      14
      9 npm
      3
      Apache 2.0

    • GitHub Prod MCP

      nouhailadahmany
      A
      license
      C
      quality
      D
      maintenance
      A production-ready MCP server for GitHub operations, providing tools for repository management, issues, pull requests, and more via both MCP stdio and REST API.
      27
      MIT
    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

    C2.2/5.0

    Scored across 33 tools

    Disambiguation2/5

    There are notable overlaps: `ensure_fork` and `github_ensure_fork` appear to be duplicates, and `repo_setup_remotes` overlaps with `repo_clone` + `repo_add_remote`. The `run_*` tools with blank descriptions also create ambiguity. As a result, agents may struggle to select the right tool.

    Naming Consistency2/5

    Tool names mix conventions: many are noun_verb (`repo_diff`, `workspace_create`) while others are verb_noun (`read_file`, `run_tests`). The `github_*` prefix is used inconsistently (`ensure_fork` vs `github_ensure_fork`), and there are multiple prefixes (`repo_`, `workspace_`, `github_`) with no clear pattern.

    Tool Count2/5

    With 33 tools, the server is over-scoped for a PR orchestration workflow. Several tools are redundant (duplicate fork checks, overlapping remote setup), suggesting the tool surface could be consolidated. This exceeds the typical well-scoped range and may confuse agents.

    Completeness3/5

    The server covers the main PR creation flow (workspace, repo operations, changes, checks, push, open PR) but lacks lifecycle tools for existing PRs—no update, merge, or comment operations. There are also no PR listing or detail tools, which are common gaps for orchestration scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources