Skip to main content
Glama
Sign In
github-repo-scout-mcp

github-repo-scout-mcp

by ashutosh6500
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to github-repo-scout-mcp

No user-submitted related servers found.

    Related Servers

    • github-repo-mcp

      thedhruv-07
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to analyze public GitHub repositories directly through tools for repo health scoring, recent commit summaries, good first issue discovery, and semantic Q&A over docs and issues.
      4
      32 npm
      1
      MIT

    • mcp-github-tools

      rog0x
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to perform GitHub analytics and management tasks, including repository analysis, PR summarization, issue triage, release notes generation, and contributor statistics.
      39 npm
      MIT

    • GitHub MCP Server

      guangxiangdebizi
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to analyze GitHub repository structures and read file contents with features like directory traversal, file type analysis, syntax highlighting, and code pattern detection. Supports both public and private repositories through GitHub API integration.
      8 npm
      Apache 2.0

    • projectpulse-mcp

      alexbypa
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to monitor GitHub repository health by calculating health scores, fetching repository metadata, analyzing Dependabot alerts, checking CI/CD status, and retrieving code scanning alerts.
      8
      205 npm
      1
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.6/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target clearly distinct resources or actions, and the descriptions clarify boundaries well. Minor overlap exists between list_issues and search_issues_and_prs, and between get_repo_tree and folder-listing behavior in get_file_contents, but these are not likely to cause serious misselection.

    Naming Consistency4/5

    All names use snake_case and most follow a verb_noun pattern such as get_repository, search_repositories, list_issues, and compare_repositories. Small inconsistencies appear in abbreviation (repo vs repository) and noun-first security_* tools, but the convention is still predictable.

    Tool Count4/5

    With 16 tools, the server is slightly above the typical well-scoped range but still reasonable given its broad remit of repository discovery, inspection, comparison, and security checks. Each tool has a plausible role and the set does not feel bloated.

    Completeness4/5

    The surface covers the core read-only scouting workflow very well: search, repo details, health, files, issues, PRs, comparisons, similarity, and security checks. A few minor gaps remain, such as explicit release listing or detailed issue retrieval, but agents can work around them using existing search and file tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources