A
licenseNot graded
qualityD
maintenanceMCP server for managing Kaiten tasks through AI agents like Claude, enabling task retrieval, creation, updating, and time logging.
27 npm
2
MIT
KiraHub MCP Server
by PendingSpark
Related Servers
Alternatives to KiraHub MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for integrating Linear with Claude Code and other MCP clients. Enables issue management, project planning, and status tracking through a set of tools.-
- AlicenseAqualityBmaintenanceMCP Server for the Notion API, enabling Claude to interact with Notion workspaces.31850 npm922MIT
- AlicenseNot gradedqualityDmaintenanceA work management MCP server for Claude Code that integrates with Jira Cloud to handle sprints, tickets, and project tracking via natural language.6 npmMIT
- AlicenseAqualityAmaintenanceMCP server for Karea task management, enabling creation, editing, closing, and linking tasks MCP tools from Claude Code and other MCP clients.449211 npm1MIT
- FlicenseBqualityDmaintenanceMCP server for team task tracking, code review, and activity monitoring via Claude Code. Assign tasks, track branch activity, review code, and get daily summaries through natural language.18-
TDQS
B3.2/5.0
Scored across 28 tools
Disambiguation4/5
Most tools have clearly distinct purposes: task management, epics, notes, dependencies, knowledge, activity, shared context, and plan wiki. A few pairs like add_project_knowledge vs set_shared_context and get_task_details vs get_task_notes could be confused, but their descriptions provide enough clarification.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern in lowercase snake_case (e.g., get_next_task, create_epic, add_working_note, resolve_working_note, post_activity). All verbs clearly indicate the action, and there are no mixed conventions or vague names.
Tool Count2/5
With 28 tools, the server exceeds the 25+ threshold that indicates a heavy, oversized toolset. While each tool serves a distinct function, the sheer number may overwhelm agents and suggests a need for consolidation or sub-servers.
Completeness3/5
The toolset covers a broad lifecycle: task and epic CRUD (though missing delete), notes, dependencies, knowledge, activity, shared context, and plan wiki. Notable gaps include no direct list_tasks tool (only via epics) and no deletion capabilities for tasks or epics, which agents may need.
Maintenance
ActivityInactive
ResponsivenessNo issues