wirk-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WIRK_CONFIG_DIR | No | The configuration directory used by the server. Defaults to ~/.config/wirk. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wirk_statusB | Start here: who you work for, your wirk, what waits, and recent changes. Writes nothing. |
| wirk_queryC | Fetch by ID, short ID or exact title; list with fields; find what matters for about (by meaning on Pro); or look up a receipt. A result "label: query …" maps bare refs to fetch, known keys to arguments, other KEY=VALUE to fields (comma values as lists, except text, linked and folder). |
| wirk_writeA | Change items and links atomically. In expect put each changed or linked-from item’s rN and the parent work of a contributes_to link; missing revisions get basis_changed. Context changes apply when you may make them; requires_review means propose with a reason. |
| wirk_reviewA | Accept, reject or defer proposals at the revision you read. Anyone whose role may review decides; other roles get not_authorized. A background agent never decides. |
| wirk_showC | A live read-only page for a person, from the preset status or a view config; returns its link. Anyone with the link can open it until it expires after 24 hours. |
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 5 tools
The tools are mostly distinct by role: query reads, write mutates, review decides proposals, show publishes a read-only view, and status gives a starting dashboard. Status, query, and show all involve reading, but their descriptions clarify different outputs and use cases.
All tools share a clear wirk_ prefix and follow a predictable second-word pattern. The names are concise and consistently snake_case.
Five tools are well-scoped for a work-item collaboration server. Each tool maps to a distinct lifecycle phase without obvious redundancy.
The surface covers reading, atomic writes, review decisions, sharing, and status, which is strong lifecycle coverage. Minor gaps remain around explicit create/delete/archive semantics, though wirk_write may cover some of these implicitly.