Skip to main content
Glama
ma-nakaya

onprem-gh-cli-mcp-server

by ma-nakaya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to onprem-gh-cli-mcp-server

No user-submitted related servers found.

    Related Servers

    • GitHub MCP

      charlesnpx
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables self-hosted, read-only remote interaction with GitHub repositories, allowing listing repositories, searching code, and inspecting commits, pull requests, issues, and diffs via authenticated MCP clients.
      78 npm
      MIT

    • GitHub MCP Server

      Arnab1999india
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to answer natural-language GitHub queries by listing repositories, issues, pull requests, branches, commits, and files, as well as performing writes with dry-run and confirmation safeguards.
      -

    • slim-github-mcp

      0xBakeer
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables local models to query GitHub read-only through nine compact tools that return small, capped results, such as repositories, issues, pull requests, commits, code search, and file contents.
      2
      MIT

    • Git MCP Server

      EnesOzturk11
      F
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to inspect local Git repositories and interact with the GitHub API for reading commits, diffs, files, issues, comments, pull requests, and project boards.
      10
      99 npm
      -
    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.6/5.0

    Scored across 64 tools

    Disambiguation5/5

    Tools are exceptionally well-differentiated. Each targets a distinct resource-action pair, and the PR review comment family (create/reply/update/delete/threads) is meticulously broken down with clear boundaries. Even closely related tools like list_pull_request_reviews vs list_pull_request_review_comments vs list_pull_request_review_threads are clearly separated by what each returns. The only mild overlap risk is run_gh vs the typed repository tools, but descriptions explicitly disambiguate them.

    Naming Consistency5/5

    The naming follows a very consistent verb_noun pattern throughout: list_*, get_*, create_*, update_*, delete_*, comment_*, merge_*, dispatch_*, add_*, remove_*, set_*, clear_*, reply_*, resolve_*, unresolve_*. Multi-word resources use underscore delimiters (pull_request, issue_events, workflow_runs, project_item_field). The pattern is predictable and scannable across all 64 tools.

    Tool Count3/5

    64 tools is high, but the scope is genuinely broad—repositories, branches, files, issues, PRs, workflows, releases, labels, milestones, and Projects v2. Each tool maps to a specific GitHub API capability and earns its place. While above the typical 'well-scoped' range of 3-15, the extensive surface is justified by the breadth of GitHub operations this server legitimately covers, and no tool appears redundant.

    Completeness5/5

    The tool surface is extraordinarily comprehensive, covering repositories, branches, files, commits, issues, PRs (including review threads, comments, diffs, checks), workflows, releases, labels, milestones, and Projects v2. The only minor gaps are item-level comment operations for Projects and resource/audit query tools, but those are edge cases. For a GitHub CLI wrapper, this is near-complete lifecycle coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources