Developer CLI

The Taskgert repository includes a small command-line client for the MCP server, for scripts and debugging. It calls one tool, the way an agent would, and prints the answer.

export TASKGERT_MCP_URL=https://mcp.taskgert.com/mcp   # default: http://localhost:4100/mcp
export TASKGERT_MCP_TOKEN=tgt_live_…

pnpm --filter @taskgert/mcp call --list                     # the tools
pnpm --filter @taskgert/mcp call get_board '{"project":"TGT"}'

Arguments

Arguments are a JSON object, given inline, from a file with @, or from standard input with - — the last two for content too large for a command line, such as a file to upload:

pnpm --filter @taskgert/mcp call add_comment @comment.json

node -e 'const fs=require("fs");process.stdout.write(JSON.stringify({task:"TGT-12",fileName:"shot.png",mimeType:"image/png",contentBase64:fs.readFileSync("shot.png").toString("base64")}))' \
  | pnpm --filter @taskgert/mcp call upload_attachment -

# The evidence of a Taskgert's target: a recording of the finished work.
node -e 'const fs=require("fs");process.stdout.write(JSON.stringify({taskgert:"TGT-G1",fileName:"target.webm",mimeType:"video/webm",contentBase64:fs.readFileSync("target.webm").toString("base64")}))' \
  | pnpm --filter @taskgert/mcp call attach_taskgert_evidence -

Results

Text is printed as it is. Images, audio and other non-text results are listed one line each, such as [image image/png, 11938 bytes]; add --save <dir> to write them to files:

pnpm --filter @taskgert/mcp call read_attachment '{"task":"TGT-12","attachment":"shot.png"}' --save out

The exit code is 1 when the tool reports an error.

Evidence

pnpm evidence <TASKGERT-KEY> scenario.json records the proof of a Taskgert's target — a screenshot or a video — in a dockerised browser and attaches it through the MCP. It takes the same TASKGERT_MCP_URL and TASKGERT_MCP_TOKEN. The scenario format is described on the Taskgerts page.