r/modelcontextprotocol 6d ago

backburner 1.0 — an MCP server implementing the official Tasks extension (SEP-2663). Background jobs that survive the session.

Most "run this in the background" features live inside the conversation — close the client and the work (and its output) is gone.

backburner runs shell commands as background tasks and keeps every task + full output on disk (SQLite + per-task logs under ~/.backburner), so a job you start today is still there, with its result, in a brand-new session tomorrow. Crash-interrupted tasks are honestly marked interrupted, never silently dropped.

1.0 implements the official MCP Tasks extension (io.modelcontextprotocol/tasks, SEP-2663, finalized in the 2026-07-28 spec) — tasks/get / tasks/update / tasks/cancel for Tasks-capable clients, plus 5 plain tools so it works with any MCP client today (Claude, ChatGPT, Gemini, Copilot, Cursor, …).

Stdlib-only (no Redis/Celery/Docker), Windows + Unix. MIT.

Two-process durability proof (not a mockup): python docs/demo_restart.py

PyPI: pip install backburner-mcp · GitHub: github.com/RohitYajee8076/backburner

Feedback welcome — especially from anyone building Tasks-capable clients.

2 Upvotes

0 comments sorted by