Skip to main content
Glama
cindyylim

MCP PR Workflow Server

by cindyylim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP PR Workflow Server

No user-submitted related servers found.

    Related Servers

    • CoolPlugz

      adaOctopus
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous Jira-to-PR workflows in Claude Code by fetching context from Jira, GitHub, Notion, and Slack, building structured prompts, and handling branch pushes, PR creation, CI polling, and task completion.
      1
      MIT

    • Agentic MCP Server

      ShunsukeHayashi
      -
      license
      B
      quality
      Not graded
      maintenance
      Enables AI-driven orchestration of GitHub development workflows including automated issue analysis, code generation, code review, and PR creation through multiple specialized agents. Integrates with GitHub Actions to automate the complete development process from issue to pull request.
      7
      -

    • atom

      vakra-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Manages GitHub pull request notifications in Slack, including repo-channel mappings, reminders, and standups.
      23 npm
      MIT

    • Code Review MCP

      shadabbi
      -
      license
      C
      quality
      Not graded
      maintenance
      Enables comprehensive GitHub PR reviews through Cursor's AI by fetching PR diffs, running static analysis tools (ESLint, Prettier, TypeScript, Semgrep), executing tests, and generating detailed code review reports with inline comments.
      9
      681 npm
      1
      -
    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

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: analyzing file changes, analyzing CI, updating PR status, and creating issues are distinct. However, send_slack_notification and notify_deployment_status both send Slack messages, which could cause confusion for an agent despite the latter being more specific.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., analyze_file_changes, suggest_template, create_follow_up_issue). There are no mixed conventions or vague verbs, making the pattern predictable.

    Tool Count5/5

    Seven tools is within the ideal 3-15 range and each tool serves a distinct step in the PR workflow. The count feels well-scoped without being excessive or too thin.

    Completeness4/5

    The tool set covers the main PR workflow: analyzing changes, suggesting templates, analyzing CI, updating status, sending notifications, and creating follow-ups. Minor gaps exist, such as no direct way to fetch PR details or comment on a PR, but the core lifecycle is reasonably covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources