@kitsy/coop-mcp
v2.3.0
Published
MCP server for COOP.
Readme
@kitsy/coop-mcp
MCP server for COOP.
This package exposes local COOP workspace state and operations to MCP-compatible clients over stdio.
Exposed Tools
coop_workspace_info()coop_list_tasks(filters?)coop_show_task(id)coop_graph_next(track?)coop_plan_delivery(name)coop_transition_task(id, status)coop_create_task(fields)
Exposed Resources
coop://workspacecoop://taskscoop://tasks/{id}coop://deliveriescoop://graph
Local Usage
From the repo root:
pnpm --filter @kitsy/coop-mcp build
node packages/mcp/dist/index.js --repo C:/path/to/your/repoOr, after installation/build:
coop-mcp --repo C:/path/to/your/repo
coop-mcp --repo C:/path/to/your/repo --project webappIf --repo is omitted, the server resolves the nearest parent directory containing .coop/.
If the workspace contains multiple COOP projects, pass --project <id> or set the workspace current project first.
Claude Code Setup
Example MCP configuration:
{
"mcpServers": {
"coop": {
"command": "node",
"args": [
"C:/Users/pkvsi/Wks/kitsy/coop/packages/mcp/dist/index.js",
"--repo",
"C:/path/to/your/workspace"
]
}
}
}If you prefer pnpm during local development:
{
"mcpServers": {
"coop": {
"command": "pnpm",
"args": [
"--dir",
"C:/Users/pkvsi/Wks/kitsy/coop",
"--filter",
"@kitsy/coop-mcp",
"exec",
"coop-mcp",
"--repo",
"C:/path/to/your/workspace"
]
}
}
}Other MCP-Compatible Tools
Any MCP client that supports stdio transports can launch this server with the same command/args pattern.
Notes
- The server reads and writes the local
.coop/workspace directly. - Tool mutations go through shared core rules for task writing, planning, and state transitions.
- Workspace identity is exposed from the active project's
.coop/projects/<project.id>/config.yml -> projectblock for orchestrators and multi-repo agents. - This phase intentionally keeps transport simple: local
stdio, no remote hosting, no auth layer.
