Skip to main content
Glama
Danissimode

PetPals KittyClaw MCP Server

by Danissimode

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KITTYCLAW_AUTHORNoDefault author for operationschatgpt
KITTYCLAW_BASE_URLNoBase URL of the KittyClaw task boardhttp://localhost:5230
PETPALS_KITTYCLAW_POLICYNoPath to policy YAML file~/.config/petpals-kittyclaw-mcp/policy.yaml
PETPALS_KITTYCLAW_AUDIT_LOGNoPath to audit log file~/.local/share/petpals-kittyclaw-mcp/audit.jsonl

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
kitty.projects.listA

List all projects visible to the agent

kitty.project.getB

Get a specific project

kitty.board.summaryA

Get a board summary: columns, member count, label count, and open ticket count

kitty.columns.listC

List columns for a project

kitty.members.listB

List members for a project

kitty.labels.listB

List labels for a project

kitty.blockers.listB

List blocked tickets for a project

kitty.tickets.listA

List tickets for a project with optional filters

kitty.ticket.getB

Get a single ticket by ID

kitty.comments.listC

List comments for a ticket

kitty.mentions.getA

Get tickets where a user handle is mentioned

kitty.ticket.createC

Create a new ticket in a project

kitty.ticket.update_descriptionB

Update a ticket's description

kitty.ticket.add_commentB

Add a comment to a ticket

kitty.ticket.assign_memberB

Assign a member to a ticket

kitty.ticket.set_priorityC

Set a ticket's priority

kitty.ticket.add_labelB

Add a label to a ticket

kitty.ticket.create_subtaskB

Create a subtask under a parent ticket

kitty.ticket.move_statusB

Move a ticket to a new status

petpals.create_task_contractC

Create a task contract and update the ticket description with it

petpals.attach_acceptance_criteriaB

Attach acceptance criteria to a ticket description

petpals.attach_validation_commandsC

Attach validation commands to a ticket description

petpals.request_agent_completion_reportC

Request a structured agent completion report by adding a comment template

petpals.review_completion_reportB

Review a completion report for a ticket and return a verdict

petpals.mark_ready_for_human_reviewB

Mark a ticket as ready for human review by adding a comment

petpals.reject_completionA

Reject a ticket completion and add a comment with reasons

petpals.mark_verifiedA

Mark a ticket as verified by adding a review comment. Does NOT move to Done.

audit.recentA

Read the last N lines from the audit log

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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