Skip to main content
Glama
NityaShukla25

github-ops-mcp

by NityaShukla25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to github-ops-mcp

No user-submitted related servers found.

    Related Servers

    • @cloud9-labs/mcp-github

      cloud9-labs
      A
      license
      B
      quality
      D
      maintenance
      MCP (Model Context Protocol) server for GitHub API integration. This server provides comprehensive tools for interacting with GitHub repositories, issues, pull requests, branches, and code search through a unified interface.
      15
      2 npm
      MIT

    • mcp-github

      bryarpatch36
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only GitHub MCP server that lets assistants search and read repositories, issues, pull requests, commits, and file contents, scoped to the user's personal access token.
      MIT

    • 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

    • repogate

      JohnXu22786
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that wraps the GitHub REST API into tools for repo queries, issue/PR management, code review, search, and authentication, letting coding agents operate GitHub directly in conversations.
      6 npm
      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

    C2.8/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., get_contributors vs get_language_breakdown). Some overlap exists between get_repo_info, get_repo_stats, and generate_repo_summary, but descriptions clarify their roles. get_diff and get_pr_diff are similar but context-specific.

    Naming Consistency4/5

    Tools consistently use snake_case verb_noun patterns like list_, get_, search_, clone_, checkout_. Minor deviations like pull_latest are still readable and do not break the overall pattern.

    Tool Count3/5

    25 tools is at the upper edge of the borderline range. While many are focused, there is redundancy (e.g., get_repo_info and get_repo_stats could be consolidated), making the set feel heavier than necessary.

    Completeness3/5

    The server provides extensive read-only repo metadata and local git operations, but lacks write operations like creating/updating issues or PRs, and lacks push/commit capabilities. This leaves notable gaps for a server named 'ops'.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources