F
licenseB
qualityB
maintenanceA lightweight MCP server that acts as a secure proxy for AI assistants to run local Git operations and GitHub API macros simultaneously.
1
-
github-mcp
by iiinigence
Related Servers
Alternatives to github-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceMCP server that exposes GitHub operations as tools for AI agents, enabling code search, issue management, and PR review.12MIT
- FlicenseAqualityCmaintenanceMCP server that lets AI agents interact with GitHub using natural language, supporting operations like creating repositories, issues, and commits.5-
- FlicenseNot gradedqualityDmaintenanceA local MCP server that turns AI clients into power users of local git repositories, enabling clone, browse, search, and inspect code without burning API tokens.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI assistants safely access local git repositories, with free reads and gated writes requiring explicit confirmation.1MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that enables AI agents to perform GitHub operations like creating repositories, issues, and commits through natural language.-
TDQS
A4.1/5.0
Scored across 15 tools
Disambiguation5/5
Each tool targets a distinct resource and action: repos, branches, files, commits, PRs, issues, workflow runs, and auth. The only slight overlap is create_branch being implicit in push_files, but create_branch serves a distinct purpose. No two tools are genuinely ambiguous.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern (e.g., open_pr, list_branches, push_files). The only outlier is 'whoami', which is a standard standalone verb but doesn't break the overall pattern.
Tool Count5/5
15 tools is at the upper boundary of the ideal 3-15 range. Each tool has a clear role, and even the diagnostic 'whoami' and the convenience 'create_branch' earn their place. No redundant or superficial tools.
Completeness3/5
The set covers the core development loop well: branches, files, commits, PRs, and CI. However, issue management is incomplete (create and comment only — no list/get/update/close), and there's no delete-file operation, no PR update, and no repository creation. These are notable gaps for a general GitHub server.
Maintenance
ActivitySlowing
ResponsivenessNo issues