A
licenseNot graded
qualityD
maintenanceEnables AI coding agents to interact with ClawWork task management, allowing them to access task feeds, claim and complete tasks, post comments, and submit artifacts.
31 npm
MIT
PetPals KittyClaw MCP Server
by Danissimode
Related Servers
Alternatives to PetPals KittyClaw MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceManages AI agent workflows through a state machine and Git branches, enforcing isolated phases and audit trails via SPEC, PLAN, and AGENTS files.MIT
- FlicenseBqualityDmaintenanceEnables AI agents to interact with ClawBoard tasks, including listing, searching, viewing details, posting comments, and upvoting.5-
- AlicenseAqualityBmaintenanceEnables AI agents to manage a task board by investigating needs, creating well-specified tasks, and executing them end-to-end.6MIT
- AlicenseNot gradedqualityAmaintenanceCoordinates parallel AI coding agents by providing task ownership, scoped file locks, handoffs, and verification workflows.MIT
- AlicenseAqualityAmaintenanceMCP server for Claude Code agents to manage persistent shared task boards with dependency graphs, atomic claims, and git-bound tasks.11123 PyPIMIT
TDQS
B3.2/5.0
Scored across 28 tools
Disambiguation5/5
Each tool targets a specific resource and action, with clear names that leave little room for confusion. Even related tools like board.summary and columns.list are distinct because one provides aggregated counts and the other lists detailed items. No two tools appear to duplicate functionality.
Naming Consistency3/5
The kitty namespace follows a resource.action dot pattern, but uses plural for list and singular for get (e.g., projects.list vs project.get). The petpals namespace uses underscore verb_phrase (e.g., create_task_contract), and audit uses just a noun. This mixing of conventions across namespaces makes the overall naming less predictable.
Tool Count2/5
With 28 tools, the set exceeds the 25+ threshold for 'too many.' Though the scope is broad, many ticket update operations could be consolidated into a generic update tool, and the workflow tools add significant volume. The high count makes selection more difficult for agents.
Completeness3/5
The core ticket lifecycle is well covered: create, get, list, update description/status/priority/labels/assignment, add comments, and create subtasks. The petpals workflow also spans contract creation to verification. However, there are notable gaps such as no project creation/update, no ticket deletion or title updates, and no management of columns/members/labels beyond reading.
Maintenance
ActivitySlowing
ResponsivenessSyncing