Skip to main content
Glama
sam170203

Personal GitHub MCP

by sam170203
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Personal GitHub MCP

No user-submitted related servers found.

    Related Servers

    • AutomateHub

      Xesderte
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate GitHub repository management, issue tracking, and commits using natural language.
      2 npm
      Apache 2.0

    • GithubMCP

      Dhananjayrbiraris
      A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to GitHub repositories, pull requests, issues, commits, and code search while enabling repository visibility controls, CI/CD monitoring, sandboxed local filesystem access, and code quality/security analysis.
      13
      1
      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.
      -
    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

    B3.2/5.0

    Scored across 20 tools

    Disambiguation2/5

    Several tools have overlapping purposes: repository_summary, explain_repository, and project_statistics all describe repository characteristics; publish_project and publish_current_project both publish local projects; and search_code, where_did_i_use, and search_my_engineering_memory all perform search operations. These unclear boundaries make it difficult for an agent to reliably select the correct tool.

    Naming Consistency2/5

    Naming is mixed between verb-first (list_repositories, create_repository, search_code) and noun-first (repository_summary, project_statistics, dependency_summary) patterns, with the exception of 'where_did_i_use' which uses a completely different sentence-like format. The inconsistency is significant enough to hinder predictable tool selection.

    Tool Count3/5

    With 20 tools, the server is on the heavy side—slightly above the ideal 3–15 range. While the count is not outrageous, the many overlapping tools inflate the number and make the set feel heavier than it needs to be.

    Completeness2/5

    The server covers repository listing, creation, searching, publishing, and local project analysis, but lacks basic GitHub operations such as updating or deleting repositories, managing issues and pull requests, or viewing commit history. These are significant gaps for a GitHub-related MCP, leaving core workflows incomplete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources