canban-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CANBAN_NSEC | No | Use this nsec instead of a key file. | |
| CANBAN_RELAY | No | Relay to connect to. | wss://relay.punkscience.ca |
| CANBAN_KEY_FILE | No | The agent's key file; created on first run. | ~/.config/canban/agent.nsec |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | This agent's Nostr identity, relay status and the companies it belongs to. Explains how to grant access if it has none. |
| list_projectsA | Projects this agent can see, with lane and task counts. |
| get_boardA | Every lane of a project in order, with its tasks in order. Bodies are omitted; use get_task for one. |
| get_taskB | One task in full, including its markdown body and lane. |
| create_taskA | Add a task to the bottom of a lane. Defaults to the first lane. |
| update_taskA | Change a task's title, body, labels or assignee. Fields left out stay as they are. Pass assignee "" to unassign. |
| move_taskB | Move a task to another lane (or reorder within one), at the top or bottom. |
| delete_taskB | Remove a task from the board for everyone. |
| create_laneB | Add a lane to the right-hand end of a project. |
| rename_laneC | Rename a lane in a project. |
| list_peopleA | People in a company, with their roles. Use their names as task assignees. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool maps to a distinct resource+action (identity, projects, board, task CRUD, lane create/rename, people), and get_board vs get_task is explicitly clarified by the note that bodies are omitted. Minor residual overlap between get_board and get_task is the only soft spot.
Consistent verb_noun snake_case throughout (list_projects, get_task, create_task, update_task, move_task, delete_task, create_lane, rename_lane, list_people), with whoami the only conventional exception and it is idiomatic.
11 tools is well within the sweet spot and every tool corresponds to a concrete board operation; nothing feels padded or missing at the count level.
Task lifecycle is fully covered (create/get/update/move/delete) plus board reads, lane creation/renaming, and people listing. Gaps: no delete_lane or lane reordering, and no project creation, which could be a dead end for cleanup or lane restructuring.