MCP Background Task Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run-background-taskA | Runs a long-running command (like 'npm run dev') in background. When the command is running, you can interact with it using other tools. |
| stop-background-taskC | Stops a running background task by its name. |
| list-background-tasksA | Lists all currently running background tasks. |
| get-task-stdoutB | Retrieves the stdout of a running background task. |
| get-task-stderrB | Retrieves the stderr of a running background task. |
| send-to-task-stdinB | Sends data to the stdin of a running background task. |
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 6 tools
Each tool has a clearly distinct purpose with no ambiguity. The tools cover different aspects of background task management: listing, running, stopping, and interacting with stdin/stdout/stderr. There is no overlap in functionality.
All tools follow a consistent verb_noun pattern with hyphens (e.g., run-background-task, list-background-tasks). The naming is predictable and readable throughout the set.
With 6 tools, the count is well-scoped for managing background tasks. Each tool earns its place by covering essential operations like starting, stopping, monitoring, and interacting with tasks.
The tool set provides complete lifecycle coverage for background tasks: creation (run-background-task), monitoring (list-background-tasks, get-task-stdout, get-task-stderr), interaction (send-to-task-stdin), and termination (stop-background-task). No obvious gaps exist.