A
licenseNot graded
qualityD
maintenanceEnables AI agents to manage GitHub repositories, branches, commits, issues, pull requests, releases, and Actions through Model Context Protocol tools.
345 npm
MIT
GitHub MCP Server
Related Servers
Alternatives to GitHub MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to perform full CRUD operations on GitHub, including repositories, issues, pull requests, branches, comments, reviews, and merges through the Model Context Protocol.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage GitHub repositories, issues, files, branches, and pull requests through the Model Context Protocol.-
Tiger GitHub MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables LLMs to interact with GitHub via the Model Context Protocol, providing tools for repository management and other GitHub operations.31Apache 2.0- AlicenseBqualityCmaintenanceEnables compatible AI clients to open, inspect, edit, test, commit, and manage GitHub repositories through local STDIO or authenticated remote Streamable HTTP, including issues, pull requests, workflows, and repository creation.30MIT
- AlicenseAqualityDmaintenanceEnables LLMs to list, create, and comment on GitHub issues using your own GitHub identity via stdio transport.3MIT
TDQS
A4/5.0
Scored across 8 tools
Disambiguation5/5
Each tool targets a distinct resource+action pair: repositories (create/list), issues (create/list/close/comment), and commits (create/list). Boundaries are clean and descriptions reinforce the intent, so an agent can reliably select the right tool. No two tools overlap in purpose.
Naming Consistency5/5
All tools follow a consistent snake_case verb_noun pattern (create_repository, list_issues, close_issue, add_comment_to_issue). The style is uniform throughout with only a natural length variation for the compound comment action.
Tool Count5/5
Eight tools is well-scoped for a focused GitHub workflow server. Every tool earns its place covering the core repo/issue/commit flows without redundancy or filler.
Completeness4/5
Covers the main lifecycle: create+list repos, create+list+close+comment on issues, and create+list commits. Minor gaps remain—no update/delete repo, no edit/reopen issue, no single-record get—but core workflows are achievable with workarounds.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues