MCP Background Job Server
Related Servers
Alternatives to MCP Background Job Server
- AlicenseAqualityAmaintenanceLocal-first MCP server and CLI wrapper for AI coding agents. SAGE routes shell commands through a tracked local runner, stores command history on the user’s machine, and returns compressed terminal output to reduce noisy context.1610MIT
Related Servers
- AlicenseBqualityAmaintenanceA secure MCP server for shell operations, terminal management, and process control, enabling AI assistants to safely execute commands and manage interactive sessions.13704 npm6MIT
- FlicenseAqualityAmaintenanceAn MCP server providing stable, composable bash command execution and file operations for agents, with planned persistent PTY-based Shell tools for long-running and incremental commands.7-
- AlicenseNot gradedqualityBmaintenanceAn MCP server that allows AI assistants to manage background processes, enabling start, stop, monitoring, and querying of long-running shell commands without blocking the conversation.MIT
- AlicenseAqualityCmaintenanceMCP server for managing interactive processes, enabling AI agents to start, interact with, and terminate long-running programs like SSH sessions, REPLs, and installers via read/write operations.88MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server that enables LLMs to execute shell commands on remote Linux and Windows systems via SSH with configurable timeout and authentication options.6,170 npmMIT
- AlicenseNot gradedqualityCmaintenanceA lightweight, cross-platform MCP server for managing background processes. Enables AI coding agents to spawn, monitor, and interact with long-lived processes.MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no ambiguity: execute_command starts jobs, get_job_output retrieves full output, get_job_status checks status, interact_with_job sends input, kill_job terminates jobs, list_jobs enumerates all jobs, and tail_job_output gets recent output. The tools cover different aspects of job management without overlap.
All tools follow a consistent verb_noun pattern with snake_case: execute_command, get_job_output, get_job_status, interact_with_job, kill_job, list_jobs, and tail_job_output. The naming is predictable and readable throughout the set.
With 7 tools, the count is well-scoped for a background job server. Each tool earns its place by covering essential operations like starting, monitoring, interacting with, and managing jobs, without being overly sparse or bloated.
The tool set provides complete lifecycle coverage for background jobs: execute_command (create), get_job_status/get_job_output/tail_job_output/interact_with_job (read/update), kill_job (delete), and list_jobs (list). No obvious gaps exist for the domain, enabling full agent workflows.