huly-mcp-selfhost
Related Servers
Alternatives to huly-mcp-selfhost
- AlicenseAqualityAmaintenanceMCP server for Huly (task tracker) integration61,170 npm64MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact with Huly's project and document management platform, providing search and write actions for issues, milestones, and more.7 npmMIT
- AlicenseNot gradedqualityCmaintenanceComplete MCP server for Huly project management with 209 tools across 23 categories — issues, projects, tasks, comments, documents, cards, channels, calendar, time tracking, test management, processes, custom fields, attachments, leads and more. Includes custom task type support (Ticket, Bug, Feature) with project-scoped status workflows and read-side Process plugin tools.24 npmMIT
- AlicenseNot gradedqualityCmaintenanceThe most complete MCP server for Huly, the open-source project management platform. It connects MCP-compatible clients to a Huly workspace, enabling management of projects, issues, milestones, components, documents, labels, and more via natural language.78 npm5Eclipse Public 2.0
- AlicenseNot gradedqualityBmaintenanceAgent-first project management MCP server that enables AI agents to manage tasks, spaces, lists, boards, subtasks, comments, and automations via natural language, with full audit trail and real-time sync.7,930 npm2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Huly project management that enables AI assistants to manage issues, track time, update statuses, and more directly from your IDE.18 npmMIT
- AlicenseBqualityAmaintenanceSelf-hosted issue tracker built for agent-driven development. One binary, SQLite storage, MCP-native, with a web UI, REST API, and CLI for the humans.2789Apache 2.0
TDQS
Scored across 99 tools
Core CRUD tools target distinct resources cleanly, but several clusters overlap: search vs search_issues, get_issue vs get_issue_context vs get_activity, claim_issue vs start_work vs finish_work, and my_day vs standup vs triage_inbox vs project_report. The descriptions do differentiate them (context bundles, workflow shortcuts, report shapes), which keeps misselection recoverable rather than fatal. Still, at 99 tools an agent must read carefully to pick the right entry point.
The dominant convention is clear snake_case verb_noun (list_issues, create_issue, add_label, remove_reaction, update_document). A minority break the pattern with noun-first or bare names (my_day, standup, finish_work, search, project_report, release_notes, check_setup), which reads more like a curated shortcut layer than inconsistency. Overall predictable and readable.
99 tools is far beyond a comfortable surface for a model to reason over, even for a broad workspace covering issues, docs, chat, CRM, planner, notifications, and time tracking. Many workflow/reporting conveniences (my_day, standup, project_report, triage_inbox, release_notes, changes_since, issues_from_meeting) could be collapsed into fewer parameterized tools. The breadth is defensible but the granularity is excessive.
Coverage is unusually deep: full issue lifecycle, relations/blockers, docs, comments, labels, components, milestones, persons, organizations, todos, chat, attachments, notifications, time tracking, plus search, setup diagnostics, and an undo facility. Gaps exist in delete/lifecycle symmetry (no delete_milestone, delete_component, delete_label, delete_teamspace, delete_channel) and update_organization only changes description. These are minor workarounds, not dead ends.