Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TASKRCNoTaskwarrior configuration file path
TASKDATANoTaskwarrior data directory
CLAUDE_PROJECT_DIRNoThe project folder told by Claude Code; used when calls don't name a folder
TASKWARRIOR_MCP_SSHNoThe ledger host for the ssh relay
TASKWARRIOR_MCP_HOSTNoMachine label in claim ownershostname
TASKWARRIOR_MCP_ROOTSNoColon-separated roots; `*` matches one folder/home/*/projects:/home/*/Work:…
TASKWARRIOR_BACKUP_DIRNoUsed by the backup and maintenance scripts~/.task-backups
TASKWARRIOR_MCP_AGENT_IDNoClaim owner for clients that send no session idmcp-<host>-<pid>
TASKWARRIOR_MCP_STALE_DAYSNoIdle days before a task leaves NEXT60
TASKWARRIOR_MCP_TASK_TIMEOUT_MSNoTimeout for each `task` call30000

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
task_contextA

Start here. Working view for this folder's project: your claims, handoffs for you, tasks other operators hold, NEXT ready work, blocked, waiting on owner. Scope comes from the session folder; pass all_projects for a per-project overview.

task_listB

Search/filter tasks in scope. Defaults to open tasks in this folder's project, most urgent first. stale:true shows tasks untouched for 60+ days.

task_getA

Full detail of one task: claim, handoff, context, dependencies, last 5 notes.

task_createA

Create a durable task for work that outlives this session (multi-session work, blockers, follow-ups, handoffs). Not for work you finish now. Project comes from the session folder unless job/repo is given. Returns an existing open task instead of a duplicate. claim:true claims it immediately.

task_updateA

Change a task: fields, a progress note, or status (done / deleted with reason / pending to reopen). Claims it for you first and renews your claim (never shortens it), so no task_claim is needed before or after an update; refuses if another operator holds it. Set waiting_on:"" to clear.

task_claimA

Mutation-scope claims (operator methodology). Claim once when you start a scope and release once when you stop; task_update keeps the claim alive in between. claim: take a lease (default 30 min; pass minutes for long work). release: give it up. handoff: keep it until to accepts (needs note with state + next action). accept: take a handoff addressed to your lane. takeover: take a claim from a session confirmed gone (needs note with reason).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 6 tools

Disambiguation4/5

Each tool targets a distinct aspect of task management: claim lifecycle, context dashboard, search/list, single-task detail, creation, and updates. The only mild overlap is between task_context (curated view) and task_list (search/filter), but descriptions clarify their different roles.

Naming Consistency4/5

All tools use a consistent `task_` prefix and snake_case, with most following a verb_noun pattern (claim, list, get, create, update). `task_context` is a noun and slightly breaks the verb pattern, but the set remains highly predictable.

Tool Count5/5

Six tools are well-scoped for a task management server with claim/handoff workflows. Each tool has a clear, non-redundant purpose, and the count is neither thin nor bloated.

Completeness4/5

The surface covers full task lifecycle (create, read, update, delete via status change) plus a sophisticated claim/handoff mechanism. Minor gaps exist, such as no explicit tool for adding/removing dependencies or managing tags, though task_update may accommodate some field changes.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues