Task MCP Server

MCP server for agent task workflows with phases, prompts, gates, and multi-agent coordination. That is what the task mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

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.

• 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

The tools it exposes

The server publishes 6 tools. What each one is for:

• Dependencies — The Dependencies tool exposed by this server
• Tracking — The Tracking tool exposed by this server
• Attachments — The Attachments tool exposed by this server
• Advanced — The Advanced tool exposed by this server
• Phases — Tasks can have a phase to categorize the type of work being performed:
• Gates — Gates are requirements that must be satisfied before status or phase transitions:

What it needs from you

Configuration is passed through the environment: TASK_GRAPH_CONFIG_PATH, TASK_GRAPH_DB_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

How it compares

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Task's toolset — Dependencies, Tracking, Attachments and 3 more — is a fair guide to whether it matches your workflow. It is maintained by Oortonaut; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Task's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.