Skip to main content
Glama
crunchtools

MCP GitHub CrunchTools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MCP GitHub CrunchTools

No user-submitted related servers found.

    Related Servers

    • mcp-github

      nhevers
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for GitHub operations, providing tools for repository management, issues, pull requests, and code search.
      -

    • GitHub Prod MCP

      nouhailadahmany
      A
      license
      C
      quality
      D
      maintenance
      A production-ready MCP server for GitHub operations, providing tools for repository management, issues, pull requests, and more via both MCP stdio and REST API.
      27
      MIT

    • Gooseworks MCP

      EduardKuun
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that exposes GitHub tools for repository management, code search, issue creation, and pull request operations.
      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.6/5.0

    Scored across 18 tools

    Disambiguation4/5

    Tools are mostly distinct, but there is potential confusion between rerun_workflow_run_tool and rerun_failed_jobs_tool, and between list_issues_tool and search_issues_tool, though the descriptions help differentiate them. The diff tool and get_pull_request_tool are clearly distinct. Overall, agents should select correctly with careful reading.

    Naming Consistency4/5

    Most tool names follow a consistent verb_noun pattern (e.g., list_issues, create_issue, update_issue, get_pull_request). Minor deviations exist such as get_pull_request_diff_tool and get_pull_request_checks_tool, which are more specific but still follow the pattern. No mixed conventions or chaotic naming.

    Tool Count4/5

    With 18 tools, the server is on the higher end of the recommended range but still reasonable for a GitHub MCP server covering issues, PRs, workflows, code search, and file access. Each tool has a distinct purpose, though some consolidation could be possible without losing functionality.

    Completeness4/5

    The server covers core workflows for issues, PRs, workflow runs, and code search, including create, read, update, and search operations. Missing operations include deleting issues/PRs, listing comments, and managing repositories, but these are not critical for typical agent tasks. The coverage is solid for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources