Task Graph MCP

MCP server for agent task workflows with phases, prompts, gates, and multi-agent coordination

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.

Manual Client & Custom JSON ConfigExpand JSON ▾

No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for task-graph-mcp, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.

Documentation Overview

Task Graph MCP Server

Agent task workflows that actually work.

When you have AI agents working on complex tasks, things go wrong fast. Agents lose context, skip steps, forget to coordinate. Task Graph solves this with structured workflows: phases to guide work, prompts for automatic guidance, gates to enforce quality, and coordination primitives for multi-agent scenarios—all through the Model Context Protocol.

Why Task Graph?

The problem: You've got complex tasks that need structured execution. Maybe a single agent working through phases, or multiple agents coordinating in parallel. Without proper workflows, agents lose track, skip steps, and produce inconsistent results.

What you get:

Structured workflows — Phases (explore, implement, review, test) guide agents through work. Transition prompts provide automatic guidance at each step.
Quality gates — Require tests to pass, code to be committed, or reviews to complete before transitions. Enforce your standards automatically.
Ready-to-use topologies — Pre-built workflows for solo work, parallel swarms, specialist relays, or hierarchical delegation. Start immediately, customize later.
Configurable workflows — Define your own states, phases, prompts, and gates. Match your process, not ours.
Multi-agent coordination — Advisory file locks, DAG dependencies, atomic claiming. No more conflicts or duplicate work.
Token-efficient — Designed for LLM context limits. Compact queries, minimal round-trips, structured outputs.
Built-in accounting — Track tokens, cost, and time per task. Know exactly what your agents are spending.
Zero infrastructure — SQLite with WAL mode. No database server to run. Just point at a file.

Features

Feature	Description
Task Hierarchy	Unlimited nesting with parent/child relationships
DAG Dependencies	Typed edges (blocks, follows, contains) with cycle detection
Phases	Categorize work type (explore, implement, review, test, deploy)
Workflows	Named workflow topologies (solo, swarm, relay, hierarchical)
Transition Prompts	Automatic agent guidance on status/phase changes
Gates	Exit requirements for status/phase transitions
Atomic Claiming	Strict locking with limits and tag-based routing
File Coordination	Advisory locks with reasons and change polling
Cost Tracking	Token usage and USD cost per task
Time Tracking	Automatic accumulation from state transitions
Live Status	Real-time "current thought" visible to other agents
Full-text Search	FTS5-powered search across tasks and attachments
Attachments	Inline content, file references, or media storage
Agent Feedback	Inter-agent communication with categorized feedback (conditional on config)
Dynamic Overlays	Runtime workflow customization via add/remove overlay tools

Quick Start

bash

# Install
cargo install task-graph-mcp

# Add to your MCP client (Claude Code, etc.)

config.json

{
  "mcpServers": {
    "task-graph": {
      "command": "task-graph-mcp"
    }
  }
}

Code

# Agent workflow (worker_id auto-generated if omitted)
connect(workflow="swarm", tags=["code"])                 → "bright-lunar-swift-fox"
list_tasks(ready=true, agent="bright-lunar-swift-fox")   → claimable work
claim(worker_id="bright-lunar-swift-fox", task="add-auth")  → you own it
update(..., phase="implement")                           → enter implementation phase
thinking(agent="bright-lunar-swift-fox", thought="Adding JWT...")  → visible to others
update(worker_id="bright-lunar-swift-fox", task="add-auth",
       status="completed",
       attachments=[{type:"commit", content:"abc123"}])  → done

Installation

From crates.io (Recommended)

bash

cargo install task-graph-mcp

Pre-built Binaries

Download the latest release for your platform from GitHub Releases:

Platform	Download
Linux (x64)	`task-graph-mcp-x86_64-unknown-linux-gnu.tar.gz`
macOS (Intel)	`task-graph-mcp-x86_64-apple-darwin.tar.gz`
macOS (Apple Silicon)	`task-graph-mcp-aarch64-apple-darwin.tar.gz`
Windows (x64)	`task-graph-mcp-x86_64-pc-windows-msvc.zip`

Extract and place the binary in your PATH.

From Source

bash

git clone https://github.com/Oortonaut/task-graph-mcp.git
cd task-graph-mcp
cargo build --release

The binary will be at target/release/task-graph-mcp.

Usage

As an MCP Server

Add to your MCP client configuration:

config.json

{
  "mcpServers": {
    "task-graph": {
      "command": "task-graph-mcp",
      "args": []
    }
  }
}

CLI Options

Code

task-graph-mcp [OPTIONS]

Options:
  -c, --config <FILE>     Path to configuration file
  -d, --database <FILE>   Path to database file (overrides config)
  -v, --verbose           Enable verbose logging
  -h, --help              Print help
  -V, --version           Print version

Configuration

Full reference: See docs/CONFIGURATION.md for complete configuration documentation including workflows, prompts, gates, roles, and tags.

Create .task-graph/config.yaml:

yaml

server:
  db_path: .task-graph/tasks.db
  media_dir: .task-graph/media  # Directory for file attachments
  skills_dir: .task-graph/skills  # Custom skill overrides
  stale_timeout_seconds: 900
  default_format: json  # or markdown

paths:
  style: relative  # or project_prefixed

auto_advance:
  enabled: false        # Auto-transition unblocked tasks
  target_state: ready   # Target state (requires custom state in states config)

States Configuration

Task states are configurable. Default states: pending, working, completed, failed, cancelled.

To add a ready state for auto-advance:

yaml

states:
  initial: pending
  disconnect_state: pending  # State for tasks when owner disconnects (must be untimed)
  blocking_states: [pending, working]
  definitions:
    pending:
      exits: [ready, working, cancelled]
    ready:
      exits: [working, cancelled]
    working:
      exits: [completed, failed, pending]
      timed: true    # Time in this state counts toward time_actual_ms
    completed:
      exits: []
    failed:
      exits: [pending]
    cancelled:
      exits: []

auto_advance:
  enabled: true
  target_state: ready

See SCHEMA.md for full documentation on state definitions.

Dependencies Configuration

Dependency types define how tasks relate to each other. Default types: blocks, follows, contains, duplicate, see-also, relates-to.

yaml

dependencies:
  definitions:
    blocks:
      display: horizontal  # Same-level relationship
      blocks: start        # Blocks claiming the dependent task
    follows:
      display: horizontal
      blocks: start
    contains:
      display: vertical    # Parent-child relationship
      blocks: completion   # Blocks completing the parent
    duplicate:
      display: horizontal
      blocks: none         # Informational only
    see-also:
      display: horizontal
      blocks: none
    relates-to:
      display: horizontal
      blocks: none

Property	Values	Description
`display`	`horizontal`, `vertical`	Visual relationship (same-level vs parent-child)
`blocks`	`none`, `start`, `completion`	What the dependency blocks

Attachments Configuration

Preconfigured attachment keys provide default MIME types and modes, reducing boilerplate when attaching common content types.

yaml

attachments:
  unknown_key: warn  # allow | warn (default) | reject
  definitions:
    commit:
      mime: text/git.hash
      mode: append
    checkin:
      mime: text/p4.changelist
      mode: append
    meta:
      mime: application/json
      mode: replace
    note:
      mime: text/plain
      mode: append

Property	Values	Description
`unknown_key`	`allow`, `warn`, `reject`	Behavior for undefined attachment keys
`definitions.<key>.mime`	MIME type string	Default MIME type for this key
`definitions.<key>.mode`	`append`, `replace`	Default mode (append keeps existing, replace overwrites)

Built-in defaults:

Key	MIME Type	Mode	Use Case
`commit`	text/git.hash	append	Git commit hashes
`checkin`	text/p4.changelist	append	Perforce changelists
`changelist`	text/plain	append	Files changed
`meta`	application/json	replace	Structured metadata
`note`	text/plain	append	General notes
`log`	text/plain	append	Log output
`error`	text/plain	append	Error messages
`output`	text/plain	append	Command/tool output
`diff`	text/x-diff	append	Patches and diffs
`plan`	text/markdown	replace	Plans and specs
`result`	application/json	replace	Structured results
`context`	text/plain	replace	Current context/state

Usage:

Code

# MIME and mode auto-filled from config:
attach(task="123", name="commit", content="abc1234")
# → mime=text/git.hash, mode=append

attach(task="123", name="meta", content='{"v":1}')
# → mime=application/json, mode=replace (overwrites existing meta)

# Explicit values override defaults:
attach(task="123", name="commit", mime="text/plain", content="override")

Environment variables:

TASK_GRAPH_CONFIG_PATH: Path to configuration file (takes precedence over .task-graph/config.yaml)
TASK_GRAPH_DB_PATH: Database file path (fallback if no config file)
TASK_GRAPH_MEDIA_DIR: Media directory for file attachments (fallback if no config file)
TASK_GRAPH_LOG_DIR: Log directory path (fallback if no config file)

MCP Tools

Worker Management

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

6mo ago

Most recent push to the default branch.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Task Graph MCP

We don't have a confirmed install command for task-graph-mcp yet, so we don't publish a generated one — a guessed package name would point at the wrong package or none at all. Follow the project's own README or setup instructions (https://github.com/Oortonaut/task-graph-mcp) for the current steps.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/task-graph-mcp?style=directory)](https://allmcps.com/mcp/task-graph-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/task-graph-mcp"><img src="https://allmcps.com/api/badge/task-graph-mcp?style=directory" alt="Task Graph MCP on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

5/9 checks healthy over the last 45d

29Quality signal: Emerging · 29/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Task Graph MCP →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients

Task Graph MCP

MCP server for agent task workflows with phases, prompts, gates, and multi-agent coordination

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Manual Client & Custom JSON ConfigExpand JSON ▾

Documentation Overview

Task Graph MCP Server

Agent task workflows that actually work.

Why Task Graph?

What you get:

Structured workflows — Phases (explore, implement, review, test) guide agents through work. Transition prompts provide automatic guidance at each step.
Quality gates — Require tests to pass, code to be committed, or reviews to complete before transitions. Enforce your standards automatically.
Ready-to-use topologies — Pre-built workflows for solo work, parallel swarms, specialist relays, or hierarchical delegation. Start immediately, customize later.
Configurable workflows — Define your own states, phases, prompts, and gates. Match your process, not ours.
Multi-agent coordination — Advisory file locks, DAG dependencies, atomic claiming. No more conflicts or duplicate work.
Token-efficient — Designed for LLM context limits. Compact queries, minimal round-trips, structured outputs.
Built-in accounting — Track tokens, cost, and time per task. Know exactly what your agents are spending.
Zero infrastructure — SQLite with WAL mode. No database server to run. Just point at a file.

Features

Feature	Description
Task Hierarchy	Unlimited nesting with parent/child relationships
DAG Dependencies	Typed edges (blocks, follows, contains) with cycle detection
Phases	Categorize work type (explore, implement, review, test, deploy)
Workflows	Named workflow topologies (solo, swarm, relay, hierarchical)
Transition Prompts	Automatic agent guidance on status/phase changes
Gates	Exit requirements for status/phase transitions
Atomic Claiming	Strict locking with limits and tag-based routing
File Coordination	Advisory locks with reasons and change polling
Cost Tracking	Token usage and USD cost per task
Time Tracking	Automatic accumulation from state transitions
Live Status	Real-time "current thought" visible to other agents
Full-text Search	FTS5-powered search across tasks and attachments
Attachments	Inline content, file references, or media storage
Agent Feedback	Inter-agent communication with categorized feedback (conditional on config)
Dynamic Overlays	Runtime workflow customization via add/remove overlay tools

Quick Start

bash

# Install
cargo install task-graph-mcp

# Add to your MCP client (Claude Code, etc.)

config.json

{
  "mcpServers": {
    "task-graph": {
      "command": "task-graph-mcp"
    }
  }
}

Code

# Agent workflow (worker_id auto-generated if omitted)
connect(workflow="swarm", tags=["code"])                 → "bright-lunar-swift-fox"
list_tasks(ready=true, agent="bright-lunar-swift-fox")   → claimable work
claim(worker_id="bright-lunar-swift-fox", task="add-auth")  → you own it
update(..., phase="implement")                           → enter implementation phase
thinking(agent="bright-lunar-swift-fox", thought="Adding JWT...")  → visible to others
update(worker_id="bright-lunar-swift-fox", task="add-auth",
       status="completed",
       attachments=[{type:"commit", content:"abc123"}])  → done

Installation

From crates.io (Recommended)

bash

cargo install task-graph-mcp

Pre-built Binaries

Download the latest release for your platform from GitHub Releases:

Platform	Download
Linux (x64)	`task-graph-mcp-x86_64-unknown-linux-gnu.tar.gz`
macOS (Intel)	`task-graph-mcp-x86_64-apple-darwin.tar.gz`
macOS (Apple Silicon)	`task-graph-mcp-aarch64-apple-darwin.tar.gz`
Windows (x64)	`task-graph-mcp-x86_64-pc-windows-msvc.zip`

Extract and place the binary in your PATH.

From Source

bash

git clone https://github.com/Oortonaut/task-graph-mcp.git
cd task-graph-mcp
cargo build --release

The binary will be at target/release/task-graph-mcp.

Usage

As an MCP Server

Add to your MCP client configuration:

config.json

{
  "mcpServers": {
    "task-graph": {
      "command": "task-graph-mcp",
      "args": []
    }
  }
}

CLI Options

Code

task-graph-mcp [OPTIONS]

Options:
  -c, --config <FILE>     Path to configuration file
  -d, --database <FILE>   Path to database file (overrides config)
  -v, --verbose           Enable verbose logging
  -h, --help              Print help
  -V, --version           Print version

Configuration

Full reference: See docs/CONFIGURATION.md for complete configuration documentation including workflows, prompts, gates, roles, and tags.

Create .task-graph/config.yaml:

yaml

server:
  db_path: .task-graph/tasks.db
  media_dir: .task-graph/media  # Directory for file attachments
  skills_dir: .task-graph/skills  # Custom skill overrides
  stale_timeout_seconds: 900
  default_format: json  # or markdown

paths:
  style: relative  # or project_prefixed

auto_advance:
  enabled: false        # Auto-transition unblocked tasks
  target_state: ready   # Target state (requires custom state in states config)

States Configuration

Task states are configurable. Default states: pending, working, completed, failed, cancelled.

To add a ready state for auto-advance:

yaml

states:
  initial: pending
  disconnect_state: pending  # State for tasks when owner disconnects (must be untimed)
  blocking_states: [pending, working]
  definitions:
    pending:
      exits: [ready, working, cancelled]
    ready:
      exits: [working, cancelled]
    working:
      exits: [completed, failed, pending]
      timed: true    # Time in this state counts toward time_actual_ms
    completed:
      exits: []
    failed:
      exits: [pending]
    cancelled:
      exits: []

auto_advance:
  enabled: true
  target_state: ready

See SCHEMA.md for full documentation on state definitions.

Dependencies Configuration

Dependency types define how tasks relate to each other. Default types: blocks, follows, contains, duplicate, see-also, relates-to.

yaml

dependencies:
  definitions:
    blocks:
      display: horizontal  # Same-level relationship
      blocks: start        # Blocks claiming the dependent task
    follows:
      display: horizontal
      blocks: start
    contains:
      display: vertical    # Parent-child relationship
      blocks: completion   # Blocks completing the parent
    duplicate:
      display: horizontal
      blocks: none         # Informational only
    see-also:
      display: horizontal
      blocks: none
    relates-to:
      display: horizontal
      blocks: none

Property	Values	Description
`display`	`horizontal`, `vertical`	Visual relationship (same-level vs parent-child)
`blocks`	`none`, `start`, `completion`	What the dependency blocks

Attachments Configuration

Preconfigured attachment keys provide default MIME types and modes, reducing boilerplate when attaching common content types.

yaml

attachments:
  unknown_key: warn  # allow | warn (default) | reject
  definitions:
    commit:
      mime: text/git.hash
      mode: append
    checkin:
      mime: text/p4.changelist
      mode: append
    meta:
      mime: application/json
      mode: replace
    note:
      mime: text/plain
      mode: append

Property	Values	Description
`unknown_key`	`allow`, `warn`, `reject`	Behavior for undefined attachment keys
`definitions.<key>.mime`	MIME type string	Default MIME type for this key
`definitions.<key>.mode`	`append`, `replace`	Default mode (append keeps existing, replace overwrites)

Built-in defaults:

Key	MIME Type	Mode	Use Case
`commit`	text/git.hash	append	Git commit hashes
`checkin`	text/p4.changelist	append	Perforce changelists
`changelist`	text/plain	append	Files changed
`meta`	application/json	replace	Structured metadata
`note`	text/plain	append	General notes
`log`	text/plain	append	Log output
`error`	text/plain	append	Error messages
`output`	text/plain	append	Command/tool output
`diff`	text/x-diff	append	Patches and diffs
`plan`	text/markdown	replace	Plans and specs
`result`	application/json	replace	Structured results
`context`	text/plain	replace	Current context/state

Usage:

Code

# MIME and mode auto-filled from config:
attach(task="123", name="commit", content="abc1234")
# → mime=text/git.hash, mode=append

attach(task="123", name="meta", content='{"v":1}')
# → mime=application/json, mode=replace (overwrites existing meta)

# Explicit values override defaults:
attach(task="123", name="commit", mime="text/plain", content="override")

Environment variables:

TASK_GRAPH_CONFIG_PATH: Path to configuration file (takes precedence over .task-graph/config.yaml)
TASK_GRAPH_DB_PATH: Database file path (fallback if no config file)
TASK_GRAPH_MEDIA_DIR: Media directory for file attachments (fallback if no config file)
TASK_GRAPH_LOG_DIR: Log directory path (fallback if no config file)

MCP Tools

Worker Management

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

6mo ago

Most recent push to the default branch.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Task Graph MCP

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/task-graph-mcp?style=directory)](https://allmcps.com/mcp/task-graph-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/task-graph-mcp"><img src="https://allmcps.com/api/badge/task-graph-mcp?style=directory" alt="Task Graph MCP on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

5/9 checks healthy over the last 45d

29Quality signal: Emerging · 29/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Task Graph MCP →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients