Skip to main content
Glama
Sign In
@sumirati/mcp-github

@sumirati/mcp-github

by sumirati
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to @sumirati/mcp-github

No user-submitted related servers found.

    Related Servers

    • GitHub MCP Server

      pipseedai
      A
      license
      A
      quality
      Not graded
      maintenance
      Enables AI agents to interact with GitHub repositories through the GitHub REST API for managing files, issues, and repository metadata. It supports both read operations like searching code and write operations such as creating repositories and updating issue comments.
      9
      -

    • github-fetcher

      KurvCygnus
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to read GitHub repositories, files, commits, issues, pull requests, releases, Actions, and search results through 18 read-only MCP tools. It reuses existing credentials, routes around unreliable networks, and caches responses on disk to stay within rate limits.
      22
      440 npm
      MIT

    • GitHub Dev Copilot

      yashwant-kumar08
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with GitHub via MCP, managing repositories, issues, PRs, and analyzing repository health through tools like list_repositories, read_issues, create_issue, comment_on_pr, and analyze_repo_health.
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    The three eager tools (get_repository, get_file_contents, get_commit) each target a distinct resource, and the find/execute pair has a clear discover-then-run relationship. Minor overlap exists because repo/file/commit reads are also reachable through github_execute_action, but the descriptions clearly frame the get_ tools as fast-path shortcuts.

    Naming Consistency4/5

    Two coherent families exist: snake_case get_noun for the eager daily drivers and github_verb_noun for the catalog tools, each internally consistent. The split prefix conventions are a minor deviation but deliberate and readable.

    Tool Count4/5

    Five visible tools is lean, but the find/execute meta-tools compress an 83-action surface into two entries, which is efficient rather than thin. The design is well-scoped, though direct-operation coverage is intentionally minimal.

    Completeness4/5

    The 83-action catalog spans PRs, issues, releases, workflows, collaborators, webhooks, variables, and security alerts, giving broad lifecycle coverage through github_execute_action. The eager tools alone lack full CRUD, but agents can work around this via the catalog.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources