zenhub-mcp
Related Servers
Alternatives to zenhub-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables querying and exploring the GitHub GraphQL API schema and executing optimized GraphQL queries to retrieve precise GitHub data (repositories, issues, PRs, users) with reduced token consumption.-
- AlicenseNot gradedqualityDmaintenanceEnables management of GitHub projects and issues using GitHub's GraphQL API. Supports creating/updating issues with images, managing labels and assignees, organizing ProjectsV2 boards, and updating project item statuses.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables users to interact with GitHub's Projects v2 API through natural language for Agile project management, supporting repository details, issue tracking, and project board management operations.35GPL 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceEnables comprehensive issue tracking and project management through Linear's GraphQL API. Supports creating and managing issues, organizing projects and sprints, team collaboration, and roadmap planning for modern development workflows.-
- AlicenseCqualityDmaintenanceEnables comprehensive interaction with the GitHub API for managing repositories, issues, pull requests, commits, and GitHub Actions workflows through natural language.2068 npmMIT
- FlicenseAqualityDmaintenanceConverts natural language queries into valid GraphQL queries and executes them against GraphQL APIs. Includes schema introspection, query validation, execution with authentication, and query history tracking.525-
TDQS
Scored across 51 tools
Most tools have distinct purposes, but the presence of 'zenhub_query_potentially_dangerous' allows arbitrary GraphQL queries, creating ambiguity and overlap with all other tools. Additionally, some tools like 'search_issues' and 'search_issues_in_repository' are similar but separate, adding slight confusion.
All tools follow a consistent 'zenhub_verb_noun' pattern, with verbs like add, create, get, update, delete, close, reopen, move, set, etc. This pattern is uniform across all 51 tools, making the naming highly predictable and systematic.
With 51 tools, the server is overly granular for its domain. Many operations could be consolidated (e.g., single vs. bulk variants of add/remove assignees, labels, and estimates). This count exceeds typical well-scoped MCP servers (3-15 tools) and feels bloated.
The tool set covers a comprehensive range of ZenHub operations: CRUD for issues, epics, milestones, sprints, workspaces, labels, dependencies, and estimates. Minor gaps exist (e.g., no pipeline create/update/delete), but the fallback query tool mitigates missing operations. Overall, core workflows are well-covered.