Skip to main content
Glama
GHeeJeon

github-workflow-mcp

by GHeeJeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to github-workflow-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Git/PR Assist

      dk-niwamoto
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables Git and GitHub pull request operations through Claude AI, including repository management, branch operations, commits, and PR creation/commenting. Streamlines development workflows by providing Git commands and GitHub API integration through natural language interactions.
      -

    • ship-it-mcp

      jjm7271985
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables to interact with GitHub repositories directly from Claude, supporting actions like viewing repos, checking status, committing and pushing changes, and managing pull requests.
      -

    • GitHub MCP Server

      MCP-Mirror
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Connects Claude Desktop directly to GitHub repositories and git commands, enabling users to clone repos, check status, commit changes, push code, create repositories, and manage GitHub resources through natural conversation.
      256 npm
      -

    • 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
    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.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools are clearly distinct (create_branch, create_issue, create_pr, list_labels, get_pr_review_summary). However, run_workflow subsumes commit_and_push and run_tests, potentially causing selection ambiguity. Descriptions mitigate this by specifying that run_workflow is a high-level automated workflow.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., create_branch, list_labels, run_tests, get_pr_review_summary). Even compound verbs like commit_and_push adhere to the pattern without mixing styles.

    Tool Count5/5

    8 tools is well within the typical 3-15 range for a focused MCP server. Each tool serves a distinct purpose in the development workflow, from branching and committing to testing and PR creation, without unnecessary bloat.

    Completeness4/5

    The tool set covers the core workflow (branching, committing, testing, PR creation, issue creation) and includes supporting tools (list_labels, get_pr_review_summary). Minor gaps exist: no direct file manipulation, no delete branch, and no tools for managing PRs after creation (e.g., merge). However, the stated purpose is workflow automation, and the set is largely complete for that.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources