Skip to main content
Glama
wirk-mcp

wirk-mcp

Official
by wirkspace

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WIRK_CONFIG_DIRNoThe 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

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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_writeB

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 5 tools

Disambiguation4/5

The five tools have mostly distinct roles: write mutates, query reads/searches, review decides proposals, show creates a live page, and status gives an overview. There is some potential overlap between query, show, and status because all involve reading or viewing work data, but the descriptions clarify their different outputs and side effects.

Naming Consistency4/5

All tools share the wirk_ prefix and use short lowercase suffixes, giving a predictable namespacing pattern. The suffixes mix verbs and nouns (write, query, review, show, status), but they remain readable and consistent enough for this small set.

Tool Count5/5

Five tools is well-scoped for this work-item management server, with each tool covering a distinct workflow: status, query, write, review, and show. There is no obvious bloat or thinness in the tool set.

Completeness4/5

The tool surface covers the core lifecycle: orientation, querying, atomic changes, review decisions, and sharing a live view. Minor gaps may exist around explicit deletion/archive operations or detailed assignment controls, but the main workflows appear supported.

Maintenance

ActivityNo data
ResponsivenessOutdated data