Skip to main content
Glama
Hint-Services

MCP Private GitHub Search

by Hint-Services
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP Private GitHub Search

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
      14
      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.
      MIT

    • GitHub Integrated MCP Server

      wj-yuta-imai
      -
      license
      C
      quality
      Not graded
      maintenance
      A Model Context Protocol server with GitHub API integration that enables interaction with repositories, issues, pull requests, and file management through a standardized interface.
      1
      -

    • github-mcp

      JessicaTemplet
      A
      license
      B
      quality
      B
      maintenance
      A Model Context Protocol server that enables Claude to directly interact with GitHub, including repos, files, branches, issues, pull requests, Actions, and code search using a personal access token.
      26
      28
      MIT

    • GitHub MCP Server

      Jeswinmathew12
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that exposes read-only GitHub tools to LLM clients, enabling browsing of open issues, pull requests, issue details, and recent repository activity via natural language.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: getCommitHistory retrieves commit history, getFileContents fetches specific file contents, searchFiles searches for files, and searchIssues searches for issues. There is no overlap in functionality, making tool selection unambiguous.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (getCommitHistory, getFileContents, searchFiles, searchIssues) with all tools using camelCase. However, 'searchFiles' and 'searchIssues' use plural nouns while 'getCommitHistory' and 'getFileContents' use singular or compound nouns, showing a minor deviation in noun consistency.

    Tool Count4/5

    With 4 tools, the count is appropriate for the server's purpose of interacting with a specific GitHub repository for an Obsidian vault. It covers key operations like retrieving history, files, and searching, though it might benefit from additional tools for actions like creating or updating issues or files to be more comprehensive.

    Completeness3/5

    The tool set provides good read/search capabilities for commits, files, and issues, but lacks write operations (e.g., create/update issues, commit changes, modify files). For a GitHub-focused server, this is a notable gap that could limit agent workflows, especially for collaborative or dynamic tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources