github-fetcher
Related Servers
Alternatives to github-fetcher
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query GitHub repository data through read-only tools, including repo metadata, issues, pull requests, commit statuses, PR diffs, and recent commits. Works with any MCP-compatible client over stdio or Streamable HTTP.1ISC
- AlicenseAqualityBmaintenanceEnables autonomous AI agents and developers to interact with the GitHub REST API for repositories, pull requests, issues, actions, releases, tags, and user/org data through MCP tools. It uses token-efficient response summaries and optional 3-tier read-only safeguards to keep interactions safe and context-window friendly.581 npm1MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to answer questions about repositories, issues, pull requests, and recent commits using read-only, schema-validated tools with pagination, retries, rate-limit handling, and caching.622 PyPIMIT
- AlicenseAqualityBmaintenanceGives AI agents read-only, structured access to an unfamiliar GitHub repository, exposing six tools for profiling a project, browsing its file tree, reading files, aggregating dependencies across ecosystems, checking file history, and searching code. Responses are cached, explicitly truncated, and errors typed so agents can reason about a codebase without a shell.6MIT
- AlicenseAqualityCmaintenanceEnables AI agents to ask read-only questions about a repository's history through GitHub APIs, including blame, path history, merge base, PR association, diffs, and file contents, with aggressive caching and no clone required.101MIT
- FlicenseNot gradedqualityDmaintenanceEnables read-only browsing and querying of GitHub repositories, including listing repos, reading files, fetching READMEs, searching code, and viewing commit history via MCP.-
TDQS
Scored across 41 tools
Most tools are clearly separable by scope: single-item vs list, search vs direct read, and repo/user/workflow/PR resources. A few aggregate and health-oriented tools (github_repo_health, github_repo_activity, github_compare_repos, github_trending) overlap enough to require careful selection, and PRs can be read through both github_pr and github_issue.
All tools use the github_ prefix and snake_case, with a predictable singular/plural convention for single-item vs collection reads and search_* for search tools. A few special names like github_api_get, github_doctor, github_capabilities, and github_user_starred deviate slightly but remain readable and predictable.
41 tools is well above the typical 3-15 range and exceeds the 25+ threshold for a heavy tool set, even for a broad GitHub read-only server. Many tools are specialized, but the large surface increases discovery and selection burden.
The read-only GitHub surface is extensive, covering repos, users, code/files, commits, issues, PRs, releases, workflows, contributors, languages, search, quota, and an api_get escape hatch. Minor gaps remain, such as dedicated PR review/comment coverage, orgs/teams, notifications, and security endpoints, though some are workaroundable.