GitHub Projects MCP
Related Servers
Alternatives to GitHub Projects MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to manage GitHub Projects V2, including items, fields, and views through a standardized interface.176 npm1MIT
- 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
- AlicenseAqualityAmaintenanceEnables reading GitHub Projects v2 kanban boards mid-conversation, with tools to list boards, retrieve board details, and summarize their contents.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to programmatically manage GitHub Project V2 boards with 100+ tools for issues, fields, workflows, and automation via MCP.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and human managers to turn GitHub Projects v2 into an autonomous task backbone, coordinating multi-agent work, generating PRDs, planning sprints, triaging issues, and shipping code through GitHub-native storage and 20 tools exposing 169 actions.301 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to use GitHub Projects v2 as a persistent task backbone: registering, atomically claiming tasks, coordinating via heartbeats, submitting work for review, and enforcing token budgets. It also supports AI-powered PRD generation, task breakdown, sprint planning, issue triage, roadmap creation, and materializing tasks into GitHub issues, milestones, and sprints.301 npmMIT
TDQS
Scored across 3 tools
Each tool targets a distinct level: list_projects (org collection), get_project (single project with fields), and list_project_items (items within a project). The boundaries are clear from the descriptions, though list_projects vs get_project could momentarily blur since both concern projects.
All three tools follow a consistent list_/get_ verb_noun snake_case convention. The pattern is predictable and immediately readable.
Three tools is thin for a Projects domain, and the surface is entirely read-only. It is coherent for a minimal read scope, but feels under-scoped for a server named 'GitHub Projects MCP'.
List and read operations are covered at the organization, project, and item levels, giving a reasonable read surface. However, no create/update/delete operations exist for projects, items, or field values, leaving write workflows unserved.