Agent Tasks

Name: Agent Tasks
Author: keshrath

by keshrathversion 2.1.0i★ –iRuns on your computer

Registry nameio.github.keshrath/agent-tasks

Install

Overview

Description from the maker (original English)

Pipeline task management for AI agents - stages, dependencies, artifacts, claiming

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Docs, sheets & office work

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "agent-tasks": {
      "command": "npx",
      "args": [
        "-y",
        "agent-tasks"
      ]
    }
  }
}

Run this in your terminal

claude mcp add agent-tasks -- npx -y agent-tasks

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "agent-tasks": {
      "command": "npx",
      "args": [
        "-y",
        "agent-tasks"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "agent-tasks": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "agent-tasks"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account keshrath, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

More stars than 0% of the other 2186 servers in this category
Published to the registry more recently than 70% of the other 2186 servers in this category
Basic checks equal to or better than 100% of the other 2186 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Agent Tasks safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.1.0) reached the registry 13 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Calendar

by BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago

Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 6 days ago

Install

MCP Server for Excel

by sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 3 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

agent-tasks

Pipeline-driven task management for AI coding agents. An MCP server with stage-gated pipelines, multi-agent collaboration, and a native Claude Code /pipeline pane. Tasks flow through configurable stages — backlog, spec, plan, implement, test, review, done — with dependency tracking, stage gates, artifact versioning, and threaded comments.

Built for AI coding agents (Claude Code, Codex CLI, Gemini CLI, Aider) but works equally well with any MCP client or REST consumer.

The user manual shows every view and action of the pane, with screenshots and short clips from the real CLI.

2.0 replaced the web dashboard with the /pipeline pane inside Claude Code; there is no browser UI, WebSocket or agent-desk plugin any more.

From 1.x

The dashboard on http://localhost:3422 is gone: open the board with /pipeline in Claude Code (install the plugin, below). The agent-desk Tasks tab is gone with it.
REST: GET /api/overview and PUT /api/tasks/:id/stage are gone (use GET /api/board and POST /api/tasks/:id/stage with {"action": "advance"}), and so are the routes nothing called; see the REST API.
A 1.x process still holding port 3422 is named by the pane (An older agent-tasks (1.10.13) holds the port) and in the status line (old server 1.10.13 on the port): end the Claude Code sessions still running it (or kill the old agent-tasks process) so a 2.x process takes the port, then Refresh.

Why agent-tasks?

When you run multiple AI agents on the same codebase, they need a shared task pipeline — not just a flat todo list. They need stages, dependencies, stage gates, and visibility.

Features

Pipeline stages — configurable per project: backlog > spec > plan > implement > test > review > done
Task dependencies — DAG with automatic cycle detection; blocks advancement until resolved
Multi-agent claiming — claim, assign, send back to an earlier stage with a reason
Subtask hierarchies — parent/child task trees with progress tracking
Threaded comments — async discussions between agents on any task
Artifact versioning — per-stage document attachments with automatic versioning
Full-text search — FTS5 search across task titles and descriptions
Claude Code `/pipeline` pane — the board beside the conversation, keyboard-first: tasks by stage, task detail with artifacts and comments, advance, send back, complete, fail, cancel, comment and delete, a status line entry
2 transport layers — MCP (stdio) and a loopback REST API (HTTP) that the pane reads
TodoWrite bridge — intercepts Claude Code's built-in TodoWrite and syncs to the pipeline
Stage gates — configurable per-project gates with per-stage rules: require named artifacts, minimum artifact counts or a comment before advancing (the schema also has require_approval, but no MCP tool or REST route records an approval, so a stage with it set cannot be left; keep it off)
Decisions log — structured decision artifacts (chose X over Y because Z) via task_artifact(type: "decision")
Learnings propagation — task_artifact(type: "learning") captures insights (technique, pitfall, decision, pattern); auto-propagated to parent and sibling tasks on completion
Agent affinity — task_list(next: true) prefers routing tasks to agents with related history (parent, dependency, project) as a tie-breaker
Heartbeat-based cleanup — auto-fails tasks from dead agents using agent-comm heartbeat data
Task cleanup hooks — auto-fails orphaned tasks on session stop and cleans up stale tasks on session start
Agent bridge — notifies connected agents on task events (claim, advance, comment)
Knowledge bridge — auto-pushes learning and decision artifacts to agent-knowledge on task completion, with embedding indexing and auto-linking

Quick Start

Install from npm

npm install -g agent-tasks

Or clone from source

git clone https://github.com/keshrath/agent-tasks.git

cd agent-tasks npm install npm run build

Option 1: MCP server (for AI agents)

Add to your MCP client config (Claude Code, Cline, etc.):

"mcpServers": { "agent-tasks": { "command": "npx", "args": ["agent-tasks"] } } }

The first MCP process to start also serves the REST API on http://localhost:3422; the others retry every 5 s and take over when it exits.

Option 2: Claude Code plugin (MCP server + `/pipeline` pane)

claude plugin marketplace add keshrath/agent-tasks

claude plugin install agent-tasks@agent-tasks

The plugin runs the MCP server and adds a Claude Code mod (function hooks, Claude Code 2.1.289+): /pipeline opens the board beside the conversation. The tutorial walks through it. Remove any hand-written agent-tasks entry from ~/.claude.json so tools do not appear twice.

Option 3: Standalone REST server

node dist/server.js --port 3422

Claude Code Integration

Once configured (see Quick Start above), Claude Code can use all 8 MCP tools directly — creating tasks, advancing stages, adding artifacts, commenting, and more. With the plugin installed, /pipeline opens the board in a pane beside the conversation (Claude Code 2.1.289+). See the Setup Guide for detailed integration steps.

MCP Tools (8)

Category	Tools
Task CRUD (4)	`task_create`, `task_get` (include subtasks/artifacts/comments/transitive_deps), `task_list` (search, next), `task_delete`
Metadata (1)	`task_update` (title, description, priority, tags, project, assignment, dependencies)
Lifecycle (1)	`task_stage` (claim, assign, advance, regress, complete, fail, cancel)
Artifacts (1)	`task_artifact` (general, decision, learning, comment)
Config & utils (1)	`task_config` (pipeline, session, cleanup, rules)

See full API reference for detailed descriptions of every tool and endpoint.

REST API (8 endpoints)

All endpoints return JSON. Loopback only: a foreign Host gets 403, so does any request carrying an Origin header (no browser calls this API), and request bodies must be application/json. Everything else goes through the MCP tools. See full API reference for details.

GET    /health                        Health check with version + uptime

GET /api/tasks/:id One task, as task_get (?include=subtasks,comments,transitive_deps) GET /api/pipeline Pipeline stage configuration GET /api/board Open and recently closed tasks (what the pane polls)

POST /api/tasks Create a task POST /api/tasks/:id/stage Lifecycle action (claim, assign, advance, regress, complete, fail, cancel) POST /api/tasks/:id/comments Add a comment DELETE /api/tasks/:id Delete a task

Testing

npm test              # vitest: 472 tests across 25 files

npm run test:watch # Watch mode npm run test:coverage # Coverage report npm run check # Full CI: typecheck + lint + format + test npm run plugin:check # the /pipeline pane: claude plugin validate + its tests (needs the claude CLI) npm run e2e:claude # the pane in the real Claude Code CLI (see CONTRIBUTING.md)

Environment variables

Variable	Default	Description
`AGENT_TASKS_DB`	`~/.agent-tasks/agent-tasks.db`	SQLite database file path
`AGENT_TASKS_PORT`	`3422`	REST API port (the `/pipeline` pane reads it)
`AGENT_TASKS_HOST`	`127.0.0.1`	REST bind address (`0.0.0.0` exposes it to the network)
`AGENT_TASKS_USER`	the OS user	Who the `/pipeline` pane acts as (`created_by`, comment author, `by`)
`AGENT_TASKS_INSTRUCTIONS`	enabled	Set to `0` to disable response-embedded instructions
`AGENT_TASKS_RETENTION_DAYS`	`30`	Days the cleanup keeps resolved approval records
`AGENT_TASKS_COMPLETED_RETENTION_DAYS`	`7`	Days a completed task is kept (and listed under the pane's Done) before purge
`AGENT_TASKS_FAILED_RETENTION_DAYS`	`7`	Days a failed task is kept before purge
`AGENT_TASKS_CANCELLED_RETENTION_DAYS`	`1`	Days a cancelled task is kept before purge
`AGENT_TASKS_ORPHAN_TIMEOUT_MINUTES`	`360`	Minutes before an in-progress task with no assignee is cancelled
`AGENT_TASKS_COMM_TIMEOUT_MS`	`5000`	Timeout of the cleanup's agent-comm requests
`AGENT_TASKS_DEAD_SESSION_GRACE_MINUTES`	`60`	`task-cleanup-start.js`: idle minutes before a dead session's task is failed
`AGENT_TASKS_HEARTBEAT_FRESH_MINUTES`	`15`	`task-cleanup-start.js`: an agent with a heartbeat this recent counts as alive
`AGENT_COMM_URL`	`http://localhost:3421`	Agent-comm REST URL for bridge notifications
`AGENT_KNOWLEDGE_URL`	`http://localhost:3423`	Agent-knowledge REST URL for knowledge bridge

Dependencies

Required: Node.js >= 20.11, better-sqlite3 (bundled)

Optional (soft dependencies — fail-open, HTTP-only, no npm dep):

agent-comm — Heartbeat-based task cleanup and event notifications. agent-comm tracks heartbeats → agent-tasks checks heartbeats → auto-fails tasks from dead agents. Also sends direct messages on claim/advance and posts to a channel on comments. Without agent-comm, stale agent detection and notifications are skipped gracefully.

agent-knowledge — Knowledge persistence for task learnings and decisions. On task completi

Only the beginning is shown; read the rest in the repo

Agent Tasks

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Docs, sheets & office worki

Common questions

Alternatives

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

README from the maker

agent-tasks

From 1.x

Why agent-tasks?

Features

Quick Start

Install from npm

Or clone from source

Option 1: MCP server (for AI agents)

Option 2: Claude Code plugin (MCP server + /pipeline pane)

Option 3: Standalone REST server

Claude Code Integration

MCP Tools (8)

REST API (8 endpoints)

Testing

Environment variables

Dependencies

Option 2: Claude Code plugin (MCP server + `/pipeline` pane)