Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
taskops_boardA

THE pulse: what the board is waiting for, grouped by the move each card needs (MERGE, MENTIONS, REVIEW, CHANGES, STALLED, TAKE, DOING, REVIEWING, BLOCKED). Open every turn with this.

taskops_cardA

One card in full — spec, the whole thread, the graph, file collisions, its worktree. Or query= to search titles and specs.

taskops_activityA

The whole story of a chapter in ONE read: every card's standing, commits (with numstat), where it merged, and what was reported — milestone=ms-… or tasks=[tk-…]. since= returns only what moved; depth=full adds each spec and thread. No diffs: follow branch and sha into git yourself.

taskops_filedA

Register a report you already COMMITTED under .taskops/reports/: path=, title=, sha=, milestone= (default: the single open chapter). The board stores the pointer, never the prose — every reader renders it from its own clone.

taskops_planA

Write the tree in ONE call: a milestone and its cards, dependencies included. after and parent take an index into this call's tasks. Orchestrator only.

taskops_assignA

Assign cards to workers, cut one worktree each, and return a paste-ready brief per card. Spawn one sub-agent per brief, all in one message. Orchestrator only.

taskops_mergeA

Integrate DONE cards into their milestone branch (--no-ff, in the integration worktree): task= one, tasks=[…] those in order, done=true every card waiting under MERGE. A batch stops at the first failure, reports per card, and continues on a re-run. A conflict aborts clean. main is never touched. Orchestrator only.

taskops_takeB

Claim your card and get everything back: the milestone's goal, the spec, the whole thread, the previous worker's note, collisions, your worktree. Workers only.

taskops_reviewA

THE verifier's one door: taskops_review task=… CLAIMS a submitted card (one verifier per card, full dossier back, the worker's lease untouched); with verdict=pass|changes and note= it judges it — the note reaches the worker verbatim. You may never judge your own work.

taskops_updateA

Change the CARD: close it (done needs a commit, or no_code=true), hand it in for review (status=review on a card that requires it), hand it back (status=released, note= how far you got), drop it (note= why), retitle, rewrite the spec or criteria, re-prioritise, declare a dependency. To say something: taskops_comment.

taskops_commentA

Say something on ANY open card — including one somebody else holds, on another team. mentions=[…] addresses it to them and reaches them on their very next call. THE channel between agents in parallel: when your files meet theirs, say so on their card.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bernatch22/taskops'

If you have feedback or need assistance with the MCP directory API, please join our Discord server