github-mcp
Related Servers
Alternatives to github-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that enables AI assistants to interact with GitHub via a fine-grained personal access token — pushing commits, managing branches, opening and merging PRs, creating issues, and reading repositories. It runs locally with no telemetry and supports a read-only mode.151MIT
- FlicenseNot gradedqualityDmaintenanceStandalone MCP server for GitHub that enables repository management, branch operations, pull request handling, and commit retrieval via tools listed in the README.1-
- AlicenseAqualityBmaintenanceA local MCP server that provides a safe, explicit set of Git operations for version control tasks like status, diff, branching, staging, committing, fetching, merging, and pushing.1311 npmMIT
- FlicenseAqualityDmaintenanceMCP server exposing GitHub tools for issues, pull requests, and code browsing via the GitHub REST API. Designed for local LLM clients with flat arguments and streamable HTTP support.15-
- FlicenseBqualityBmaintenanceA lightweight MCP server that acts as a secure proxy for AI assistants to run local Git operations and GitHub API macros simultaneously.1-
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server that handles git operations on behalf of AI coding assistants, running as a local HTTP service without external network exposure by default.MIT
TDQS
Scored across 6 tools
Each tool has a clear, distinct purpose. Despite some conceptual overlap between create_feature_branch and prepare_feature_workflow, the latter includes additional steps (status check, update main) that differentiate them. All other tools are uniquely scoped.
All tool names follow a consistent verb_noun pattern with underscores, using descriptive verbs like create, prepare, pull, push, and inspect. No mixing of conventions or vague terms.
Six tools is an ideal number for a focused Git workflow server. Each tool covers a necessary step without redundancy or bloat.
The set covers the core feature workflow: status, pull, branch creation, push, and PR creation. Missing operations like branch deletion or listing PRs are minor gaps that don't break the primary workflow.