MCP.Market

Backburner MCP server

by RohitYajee8076·io.github.RohitYajee8076/backburner·v1.0.0·2 stars
No reviews yet

Run long shell commands as background tasks: start them, keep working, collect the results later

B80/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

2 stars

Reviews

Write one

Nobody has reviewed Backburner yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Backburner tools (5, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • cancel_taskwrite action

    Cancel a running task, killing its whole process tree.

  • list_tasks

    List recent tasks, newest first.

  • start_task

    Start a shell command as a background task and return immediately.

  • task_result

    Get a task's captured output (stdout+stderr merged).

  • task_status

    Check on a task: working, completed, failed, cancelled, timed_out, or interrupted.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

1 medium
  • Code scan6 source files scanned20/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 53 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • mediumsubprocess with shell=Trueexec.shell-true
    backburner_mcp-1.0.0/backburner/jobs.py: …rocess.Popen( command, shell=True, cwd=cwd, env=env, std…
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Backburner compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
2
more than 75% of 28,688 servers

What its tools let an agent do: 3 read · 1 delete · 1 run or deploy

Install Backburner in Claude Code, Cursor or VS Code

claude mcp add backburner -- uvx backburner-mcp
Add to Cursor

What the publisher says

From the Backburner repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.RohitYajee8076/backburner -->

Put your AI agent's slow work on the back burner. Keep cooking.

Background tasks for AI agents that outlive the conversation — start a long job, close the client, and the result is still waiting when you come back.

Durable &amp; Restart-Proof&nbsp; ◦ &nbsp;Zero Infrastructure&nbsp; ◦ &nbsp;MCP Tasks (2026-07-28)&nbsp; ◦ &nbsp;Windows &amp; Unix

📦 PyPI&nbsp; • &nbsp;🗂️ MCP Registry&nbsp; • &nbsp;🐛 Issues&nbsp; • &nbsp;📄 MIT

📢 Updates

(SEP-2663, io.modelcontextprotocol/tasks). A Tasks-capable client can turn a starttask call into a durable task and drive it with tasks/get, tasks/update, and tasks/cancel — the standard async-job protocol — while the five plain tools keep working for every other client. Built against the 2026-07-28** spec (mcp 2.0).

  • v1.0 — implements the official MCP Tasks extension

longer crashes tasks on Windows.

  • v0.2.1 — output with non-ASCII characters (✓, emoji, any non-English text) no

(it was an artifact of the kill, not a real result); new animated demo below.

  • v0.2.0 — exit_code is no longer reported for cancelled/timed-out tasks

Listed on the official MCP Registry as io.github.RohitYajee8076/backburner.

  • v0.1.x — first release: 5 tools, task timeouts, command allow/deny policy.

backburner is an MCP server that gives any AI assistant — Claude, ChatGPT, Gemini, GitHub Copilot, Cursor, and any other MCP client — the ability to run long shell commands as background tasks — start a test suite, a build, a scrape, a batch job — then keep working and check back for the results, instead of sitting frozen until it finishes.

🔥 Why not just use my client's built-in background mode?

Because that lives inside the conversation — it disappears the moment the session ends. Close the chat, restart the client, reboot the laptop, and any in-session background work (and its output) is gone.

backburner keeps every task and its full output on disk (SQLite + per-task log files under ~/.backburner/), so your work outlives the session that started it:

today is still listed, with its result, in a brand-new session tomorrow.

  • Start now, collect later — even in a different chat. A task you launch

restarting. Finished tasks keep their output; a task cut off by a crash is honestly marked interrupted, never silently dropped.

  • Restart-proof. State survives the server, the client, and the machine

conversation or times out and loses the work.

  • No waiting, no blocking. A 10-minute tool call no longer freezes the

See it for yourself — a real two-process proof (no mock-ups):

python docs/demo_restart.py

It starts a job in one process, exits, then a separate process — which never saw the task id — finds the finished work waiting on disk.

Built on the MCP Tasks pattern, formalized in the 2026-07-28 spec release (SEP-2663): backburner speaks it natively (tasks/get / tasks/update / tasks/cancel) and exposes the same engine as plain tools, so it works with every client today.

🧰 Tools

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Backburner: common questions

Is Backburner MCP server safe?
Mostly: it is graded B (80/100). Read the Backburner safety report
How do I install Backburner?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Backburner need an API key?
No secret keys are declared. It reads 3 settings from the environment.
Is Backburner maintained?
The last commit was 94 days ago (2026-08-02). The latest release is v1.0.0.
How does Backburner compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.