The task manager for Goose

Give Block's Goose a real task queue. Goose is built on MCP — its extensions are MCP servers — so TaskPrio plugs straight in. Goose pulls the highest-priority task with get_next_task, works it, reports a result, and grabs the next one. You set the order; it runs the list on autopilot — and you watch it work in a live cockpit.

Why Goose is a natural fit

Most agents bolt MCP on. Goose is the opposite: every Goose capability is an extension, and extensions speak the Model Context Protocol. Adding TaskPrio isn't a workaround — it's exactly how Goose is meant to gain new tools. Once it's in, TaskPrio's queue tools sit alongside Goose's built-ins.

Connect in three steps

1. Open the board, then the sidebar foot, and Copy token. 2. Download the bundled server. 3. Add it to Goose:

# download the MCP server
curl -fsSL https://taskprio.com/mcp-server.js -o ~/.taskprio-mcp.js

# add it to Goose as a command-line (stdio) extension
goose configure
#   → Add Extension → Command-line Extension
#   → command:  node ~/.taskprio-mcp.js
#   → env var:  PROMPTPRIO_API_TOKEN = pp_your_token
#   → env var:  PROMPTPRIO_API_URL   = https://taskprio.com

Prefer the config file? The same extension goes in ~/.config/goose/config.yaml as a type: stdio entry running node ~/.taskprio-mcp.js with those two env vars. Either way, start Goose and the tools are live. (Full details in the docs.)

The autopilot loop

Once connected, point Goose at your queue and it runs top to bottom — auto-scoping to the project your terminal is in (it reads the working directory, no manual setup):

1. get_next_task     → top unblocked task + merged project context
2. (Goose does the work in your repo)
3. complete_task     → short result, logged as an audit trail
4. repeat            → until the queue returns no task

Hit a blocker? Goose calls flag_needs_human and moves on, so one stuck task never stalls the whole run.

Why a queue beats a prompt dump

• One priority order — Goose always knows the single next thing, even across 1,000+ tasks and many projects.
• Context comes with the task — each task carries its project's merged instructions, so you stop re-pasting setup into the session.
• Parallelise across sessions (Pro) — run up to 5 Goose sessions on the same project and the queue divides itself: each session leases the next unclaimed task, so five work the top five in parallel — no partitioning, no two agents on one task.
• You stay in control — capture tasks in the Inbox, rank what matters, and Goose only works what you've ranked.

Frequently asked questions

Does Goose support TaskPrio's MCP server?

Yes. Goose is built on the Model Context Protocol — its extensions are MCP servers — so TaskPrio plugs in as a command-line (stdio) extension. Add node ~/.taskprio-mcp.js via goose configure and Goose gains TaskPrio's tools.

How do I give Goose a task queue?

Download the MCP server, add it as a Command-line Extension (goose configure), and Goose can call get_next_task, complete_task and friends to pull from and complete tasks in your TaskPrio queue.

Can Goose work tasks on autopilot?

Yes — it loops get_next_task → work → complete_task until the queue is empty, a task is blocked, or you stop it.

Is it free?

Yes. Free includes 1 MCP session and 50 completions/day; Pro ($10/mo) gives 5 sessions and unlimited completions.

Start free — no card →   Using Claude Code? →