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_statusA | Start here. Who you work for, your wirk, what is in progress, what needs your review, recent changes and how to ask for more. Writes nothing. |
| wirk_queryC | Fetch by ID, short ID or exact title; list with fields; find what matters for the words in about, ranked by meaning; or look up a receipt. |
| wirk_writeA | Change items and links in one atomic batch. Put the revision you read (rN) of each existing item you change or link from in expect; one left out is refused as basis_changed. Context changes apply when you may make them; otherwise they are refused with requires_review: propose them (mode propose, with a reason). After an uncertain result, resend the identical body with the request_id it names. |
| wirk_reviewA | Only people decide proposals: as an agent this is refused (not_authorized for your own proposal, person_required for any other), and the proposal waits. Your person decides at their terminal: wirk review ID@N accept --reason WHY --person. |
| wirk_showC | Not live yet on api.wirk.life: answers views_unavailable. Make a live, read-only page a person can open, from the preset status or a view config; returns its link. Anyone with the link can open it until it expires. |
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
Each tool has a fairly distinct role: status is a read-only overview, query is targeted fetch/list/search, write mutates, review handles governance, show publishes a page. status and query both read, which creates some mild overlap, but the 'start here' framing and query's specificity keep them separable.
All tools follow a clean wirk_<verb> snake_case pattern with no style mixing. The only minor quirk is that 'status' is a noun while the rest are verbs, but the prefix-and-shape convention is fully consistent.
Five tools is well-scoped for a work-coordination server, with each mapping to a distinct lifecycle stage (overview, read, mutate, review, publish). Nothing feels redundant or missing at the count level.
Read (status/query), mutate (write handles create/update/link atomically), and governance (review) are all covered, giving a coherent lifecycle. The notable gap is wirk_show, which is admitted to be non-functional ('views_unavailable'), leaving a dead end in the surface.