A
licenseNot graded
qualityC
maintenanceA Model Context Protocol server for Huly issue tracking with full CRUD support, enabling management of issues, projects, and labels with filtering capabilities.
7 npm
MIT
Huly MCP
Related Servers
Alternatives to Huly MCP
Related Servers
- MIT
- AlicenseNot gradedqualityAmaintenanceMCP server providing full coverage of the Huly SDK — issues, projects, workspaces, members, and account management.232 npm1MIT
- AlicenseNot gradedqualityDmaintenanceThe 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.31 npm5Eclipse Public 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for Huly project management — enables managing issues, documents, people, and labels through natural language.AGPL 3.0
@spatialy/huly-mcpofficial
AlicenseNot gradedqualityDmaintenanceMCP server for Huly platform enabling project management, issue tracking, and collaboration through natural language.18 npm2MIT- AlicenseNot gradedqualityCmaintenanceMCP server that integrates with myTinyTodo to list, create, edit, and complete tasks via its JSON HTTP API.MIT
TDQS
A4.4/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a distinct role: get_huly_context and get_version provide session/version info, get_tool_schema provides schema details, list_tool_categories and search_tools provide discovery, and invoke_tool executes. No two tools overlap in purpose.
Naming Consistency4/5
Tool names follow a consistent verb_ prefix pattern: get_, list_, search_, invoke_. The deviation is that some use compound names like get_huly_context and list_tool_categories, but all are snake_case and clear. Minor inconsistency: get_version vs get_huly_context, but both start with 'get'.
Tool Count5/5
Six tools is ideal for a proxy server: context, version, schema, category listing, search, and invocation. Each tool earns its place and the count is well within the 3-15 sweet spot. No redundancy.
Completeness5/5
The surface is complete for a proxy: it covers discovery (list/search), introspection (schema/context/version), and execution (invoke). There are no obvious dead ends—agents can discover, understand, and invoke any Huly tool. The only potential gap is lack of authentication-specific tools, but that's not stated as part of the scope.
Maintenance
ActivityActive
ResponsivenessResponsive