Skip to main content
Glama
taskguard-mcp

taskguard-mcp

TaskGuard MCP

TaskGuard MCP is a Model Context Protocol server that gives AI agents a lightweight task-management and self-verification layer.

It helps agents:

  • define clear goals before execution

  • break work into measurable checkpoints

  • detect scope drift before doing unrelated work

  • record decisions, blockers, and verification evidence

  • verify final results against explicit done criteria

TaskGuard is designed for coding agents, research agents, automation agents, and any long-running AI workflow where staying focused matters.

Why TaskGuard?

Agents are powerful, but they often fail in predictable ways:

  • They expand the scope with “while I’m here...” cleanup.

  • They lose track of what the user actually asked for.

  • They report progress without evidence.

  • They say “done” before acceptance criteria are satisfied.

TaskGuard gives the agent a durable task contract and an audit trail it can consult throughout the run.

Related MCP server: agent-runtime-mcp

Install

npm install -g taskguard-mcp

Or run directly:

npx taskguard-mcp

For local development:

npm install
npm run build
node dist/index.js

MCP client configuration

Published package:

{
  "mcpServers": {
    "taskguard": {
      "command": "npx",
      "args": ["taskguard-mcp"]
    }
  }
}

Local build:

{
  "mcpServers": {
    "taskguard": {
      "command": "node",
      "args": ["/absolute/path/to/taskguard-mcp/dist/index.js"],
      "env": {
        "TASKGUARD_STATE_DIR": "/absolute/path/to/.taskguard"
      }
    }
  }
}

On Windows, use escaped backslashes in JSON paths:

{
  "mcpServers": {
    "taskguard": {
      "command": "node",
      "args": ["C:\\Users\\VK\\Desktop\\mcp-skill\\dist\\index.js"],
      "env": {
        "TASKGUARD_STATE_DIR": "C:\\Users\\VK\\Desktop\\mcp-skill\\.taskguard"
      }
    }
  }
}

State storage

TaskGuard stores local state as JSON.

Default:

${process.cwd()}/.taskguard/taskguard-state.json

Environment overrides:

Variable

Meaning

TASKGUARD_STATE_FILE

Exact state file path

TASKGUARD_STATE_DIR

Directory containing taskguard-state.json

Runtime state is intentionally excluded from git via .gitignore.

Tools

taskguard_define_goal

Call before meaningful work starts. Defines the task contract.

{
  "title": "Implement login form",
  "goal": "Create a login form with validation using existing UI components",
  "nonGoals": ["Do not modify backend APIs"],
  "doneCriteria": [
    { "description": "Login form renders", "required": true },
    { "description": "Validation works", "required": true },
    { "description": "Tests pass", "required": true }
  ]
}

taskguard_add_checkpoint

Adds measurable work steps.

{
  "sessionId": "session_abc123",
  "checkpoints": [
    { "label": "Build form UI" },
    { "label": "Add validation" },
    { "label": "Run tests" }
  ]
}

taskguard_update_checkpoint

Updates checkpoint status and can attach evidence.

{
  "sessionId": "session_abc123",
  "checkpointId": "checkpoint_abc123",
  "status": "completed",
  "evidence": {
    "kind": "test",
    "summary": "Vitest suite passed",
    "command": "npm test"
  }
}

taskguard_check_scope_drift

Checks whether proposed work appears outside the recorded task contract.

{
  "sessionId": "session_abc123",
  "proposedAction": "Also refactor the whole auth backend while here",
  "changedFiles": ["src/server/auth.ts"]
}

Returns in_scope, possible_drift, or out_of_scope with reasons and a suggested next step.

taskguard_add_evidence

Records proof of progress or verification.

{
  "sessionId": "session_abc123",
  "kind": "typecheck",
  "summary": "TypeScript typecheck passed",
  "command": "npm run typecheck",
  "doneCriterionIds": ["criterion_abc123"]
}

taskguard_update_criterion

Marks done criteria as pending, met, not_met, or waived.

{
  "sessionId": "session_abc123",
  "criterionId": "criterion_abc123",
  "status": "met",
  "evidenceIds": ["evidence_abc123"]
}

taskguard_add_blocker / taskguard_update_blocker

Tracks blockers that prevent completion until resolved or waived.

taskguard_verify_done

Call before final response, commit, push, PR, or handoff.

{
  "sessionId": "session_abc123",
  "strict": true
}

Strict mode requires met required criteria to have linked evidence.

taskguard_get_status

Returns the current ledger for one session or all non-archived sessions.

taskguard_reset_session

Archives or deletes a session. Prefer archive for auditability.

Resources

TaskGuard exposes read-only MCP resources:

  • taskguard://sessions

  • taskguard://sessions/{sessionId}

  • taskguard://sessions/{sessionId}/summary

  • taskguard://sessions/{sessionId}/done-report

Prompts

TaskGuard includes prompts that guide agents into the recommended workflow:

  • taskguard_plan_task

  • taskguard_checkpoint_review

  • taskguard_done_review

  1. User asks for a task.

  2. Agent calls taskguard_define_goal.

  3. Agent calls taskguard_add_checkpoint.

  4. Before adjacent or broad work, agent calls taskguard_check_scope_drift.

  5. After each step, agent calls taskguard_update_checkpoint and records evidence.

  6. Before saying “done”, agent calls taskguard_verify_done.

  7. If ready is false, agent reports what remains instead of claiming completion.

Development

npm install
npm run lint
npm run typecheck
npm test
npm run build

Privacy and security

TaskGuard is local-first. It does not call external APIs and does not use an LLM internally. State is written to the configured local JSON file.

Do not store secrets, API keys, passwords, or sensitive personal data in TaskGuard evidence or decision logs.

License

MIT

Available Tools

12 tools
taskguard_add_blockerB

Call this when progress is blocked by missing input, failing dependencies, permissions, unclear requirements, or external failures.

Inputs: sessionId (required), description (required), status, resolution.

taskguard_add_checkpointA

Call this when breaking a task into measurable implementation or research steps. Checkpoints make progress auditable instead of relying on vague status updates.

Inputs: sessionId (required), checkpoints (required).

taskguard_add_evidenceA

Call this whenever you have proof of progress: tests, typecheck, lint, review, manual verification, artifacts, paths, or URLs. Link evidence to done criteria when possible.

Inputs: kind (required), summary (required), sessionId (required), url, +4 more.

taskguard_check_scope_driftB

Call this before doing adjacent cleanup, broad refactors, extra features, or work that may not map to the recorded goal. It warns when the proposed action appears outside the task contract.

Inputs: sessionId (required), proposedAction (required), changedFiles.

taskguard_define_goalA

Call this before starting meaningful work. Defines the task contract: goal, non-goals, and explicit done criteria that later tools use to detect scope drift and verify completion.

Inputs: goal (required), title (required), doneCriteria (required), nonGoals, +1 more.

taskguard_get_statusA

Call this when resuming work or when the user asks what remains. Returns the active task ledger or a specific session.

Inputs: sessionId, includeArchived.

taskguard_record_decisionA

Call this when choosing an implementation approach, rejecting an alternative, or deciding whether a requested change is in scope. Records rationale for later review.

Inputs: decision (required), sessionId (required), rationale, alternativesConsidered.

taskguard_reset_sessionA

Call this only when the user abandons, restarts, archives, or deletes a TaskGuard session. Prefer archive over delete to preserve audit history.

Inputs: mode (required), sessionId (required).

taskguard_update_blockerA

Call this when a blocker is resolved or waived. Open blockers prevent taskguard_verify_done from returning ready.

Inputs: status (required), blockerId (required), sessionId (required), resolution.

taskguard_update_checkpointA

Call this after starting, completing, or intentionally skipping a checkpoint. Attach evidence such as test output, files, or notes whenever possible.

Inputs: status (required), sessionId (required), checkpointId (required), evidence, +1 more.

taskguard_update_criterionC

Call this when a done criterion becomes met, not met, pending, or explicitly waived. In strict verification, met criteria should have linked evidence.

Inputs: status (required), sessionId (required), criterionId (required), rationale, +1 more.

taskguard_verify_doneB

Call this before final response, commit, PR, or handoff. It checks done criteria, checkpoints, blockers, and optional evidence requirements so the agent does not falsely claim completion.

Inputs: sessionId (required), strict.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 12 tools

    Disambiguation5/5

    Every tool has a clearly distinct role: goal definition, checkpoint management, evidence, criteria, decisions, scope checks, blockers, verification, status, and session reset. No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent pattern: 'taskguard_' + verb_noun (e.g., add_checkpoint, update_criterion, verify_done). Naming is uniform and predictable.

    Tool Count5/5

    12 tools is an ideal number for a task management server. Each tool serves a necessary function without redundancy or bloat.

    Completeness5/5

    The toolset covers the full task lifecycle: definition, execution tracking (checkpoints, evidence, blockers), verification, and status retrieval. No obvious gaps.

    Related MCP Connectors

    Related MCP Servers