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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/RohitYajee8076/backburner'
If you have feedback or need assistance with the MCP directory API, please join our Discord server