Skip to main content
Glama
pranjal-sen-2004

GitHub Activity MCP Server

by pranjal-sen-2004
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to GitHub Activity MCP Server

No user-submitted related servers found.

    Related Servers

    • Git MCP Server

      EnesOzturk11
      A
      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
      65 npm
      ISC

    • 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

      nht-x
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with GitHub directly by fetching repository information, creating issues, and triggering repository_dispatch events through natural language.
      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 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: repositories, files, commits, issues, pull requests, and user profiles are cleanly separated. There is no meaningful overlap between tools like get_repository and search_repositories or list_issues and get_issue.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, such as search_repositories, get_file_contents, and create_issue. Minor semantic differences between verbs like get and list are still predictable and uniform across the set.

    Tool Count5/5

    Thirteen tools is well within the ideal range for a domain-focused server and each tool covers a meaningful capability. The count feels appropriately scoped for GitHub browsing, issue interaction, and pull request review without being bloated.

    Completeness4/5

    The server covers read-heavy repository activity well, including search, file access, commits, issues, pull requests, and user profiles. Issue comments are supported, but lifecycle operations like updating/ closing issues or creating/merging pull requests are absent, which is a minor gap if the server is intended for broader GitHub management.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources