io.github.RohitYajee8076/backburner
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BACKBURNER_DENY | No | Regex pattern for commands that are denied. Multiple patterns can be comma-separated. Deny always wins. | |
| BACKBURNER_ALLOW | No | Regex pattern for commands that are allowed to run. Multiple patterns can be comma-separated. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_taskA | Start a shell command as a background task and return immediately. Args: command: The shell command to run (e.g. "pytest -q" or "npm run build"). cwd: Working directory for the command. Defaults to the server's cwd. timeout_seconds: If set, the task is killed and marked 'timed_out' when it runs longer than this. Recommended for unattended jobs. Returns the new task's id and initial status. The command keeps running after this call returns — use task_status / task_result to follow it. |
| task_statusC | Check on a task: working, completed, failed, cancelled, timed_out, or interrupted. |
| task_resultA | Get a task's captured output (stdout+stderr merged). Args: task_id: The task to inspect. Works for finished AND still-running tasks, so you can peek at live progress. tail_lines: How many trailing lines of output to return. |
| cancel_taskA | Cancel a running task, killing its whole process tree. |
| list_tasksB | List recent tasks, newest first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct lifecycle stage: start_task initiates, task_status reports state, task_result retrieves output, cancel_task terminates, and list_tasks enumerates. No two tools overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case: start_task, task_status, task_result, cancel_task, list_tasks. There are no deviations or mixed conventions.
Five tools is a perfect scope for a background task manager: create, monitor, retrieve output, cancel, and list. Each tool has a clear role, and no redundant or missing entries.
The tool set covers the full lifecycle of a background task: start, poll status, fetch output, cancel, and list. The timeout behavior in start_task also handles timed-out tasks. No obvious gaps.