Skip to main content
Glama
thiagorchaves

GitHub Flow MCP

by thiagorchaves
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to GitHub Flow MCP

No user-submitted related servers found.

    Related Servers

    • ContextBridge

      Vatsal212005
      A
      license
      B
      quality
      B
      maintenance
      A security-first MCP gateway that enables AI assistants to safely inspect and interact with GitHub repositories through a controlled, auditable tool layer with policy enforcement and human approval for mutations.
      27
      MIT

    • github-mcp

      iiinigence
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with GitHub via a fine-grained personal access token — pushing commits, managing branches, opening and merging PRs, creating issues, and reading repositories. It runs locally with no telemetry and supports a read-only mode.
      15
      1
      MIT

    • 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
      14 npm
      3
      Apache 2.0

    • GitHub MCP Toolkit

      kartik-012
      A
      license
      Not graded
      quality
      B
      maintenance
      A production-grade MCP server that provides LLMs with safe, structured, tool-based access to GitHub repositories, including issue management, semantic search, and guarded write operations.
      MIT

    • Moory

      dalmaktube-creator
      A
      license
      Not graded
      quality
      A
      maintenance
      A self-hosted MCP bridge that enables Notion AI to interact with approved Git repositories and curated GitHub APIs, supporting guarded code changes, pull requests, issues, Actions, logs, releases, secret scanning, and audit logging.
      Apache 2.0
    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 18 tools

    Disambiguation2/5

    There is heavy overlap among the many 'preview_' tools: preview_branch_name, preview_local_commit, preview_remote_branch, preview_pull_request, and preview_pull_request_comment all follow a 'preview' pattern but differ in what they preview. More seriously, inspect_local_repository and preview_local_commit both involve inspecting local state, and several tools have empty descriptions (healthcheck, get_authenticated_user, get_repository, list_branches) that provide no cues for disambiguation, making misselection likely.

    Naming Consistency3/5

    Most tools follow a consistent verb_noun pattern (list_pull_requests, get_pull_request, list_branches, list_workflows). However, there is a notable deviation with build_basecamp_pr_update and healthcheck, and the 'preview_' family uses a verb style distinct from the rest of the set, creating a mixed but still readable convention.

    Tool Count4/5

    At 18 tools, the count is on the heavier side but reasonable for a GitHub workflow orchestration server that spans local inspection, PR operations, Basecamp integration, and CI workflows. Several tools feel edge-case specific (healthcheck, get_authenticated_user, list_collaborator_permission), but each has a defensible purpose.

    Completeness3/5

    The server covers core GitHub operations like listing/getting PRs, branches, workflows, and repository information. However, there are notable gaps: no create/update/merge pull request tools, no create/delete branch tools, and no workflow dispatch or run detail tools. The surface is read-inspection heavy but lacks the mutation actions expected of a 'workflow' server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources