tasks-mcp

Name: tasks-mcp
Availability: InStock
Author: Arthur

Track persistent tasks on a shared UI-backed task board during agent runs.

8|3|Updated Jun 12, 2026

Search Tags:#planning #progress tracking #handoff #tasks #scratchpad #task board

Ready to run

npx skills add https://github.com/arthur0n/xenodot-forge --skill tasks-mcp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tasks-mcp
Source: https://github.com/arthur0n/xenodot-forge/tree/main/plugin/skills/tasks-mcp
Command: npx skills add https://github.com/arthur0n/xenodot-forge --skill tasks-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of losing track of work during an agent run by providing a persistent task board that keeps plans, progress, and open items visible.

Core Features & Use Cases

Persistent Planning: Add a full plan at the start of a run so work is captured before execution begins.
Live Progress Tracking: Mark tasks in progress and done as you work, keeping the board aligned with reality.
Clean Handoffs: Close all remaining tasks in one call before returning or handing off, ensuring no open work is left behind.
Use Case: An agent can map a multi-step fix, update each step as it completes, and finish by closing the scratchpad so the next session starts clean.

Quick Start

Use the tasks-mcp skill to add my current plan as tasks, update them as I work, and close any remaining open tasks before handoff.

Frequently Asked Questions about tasks-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track planning and progress for an agent run?▼

Track planning and progress for an agent run by using a persistent task board to add plans, update task statuses as work completes, and execute a final close call for clean handoffs.

What is the best way to manage agent workflow handoffs without losing open tasks?▼

Managing agent workflow handoffs requires closing all remaining open tasks in one call before returning, ensuring the scratchpad is clean and no open work is left behind for the next session.

How does a persistent task board work with live progress tracking?▼

A persistent task board works with live progress tracking by requiring task IDs to update individual task statuses to in progress or done, keeping the board aligned with reality throughout the workflow.

Can I map a multi-step fix and update each step as it completes?▼

You can map a multi-step fix by adding the full plan as tasks at the start of a run, then marking each step in progress or done as you work, and finishing by closing the scratchpad.

Do I need task IDs to update progress on a shared task board?▼

Task IDs are required to update progress on the shared task board, and a final complete_open call must be executed to close all owned tasks before returning or handing off the workflow.