Skip to main content
Glama
dylan-gluck

MCP Background Job Server

by dylan-gluck

Related Servers

Alternatives to MCP Background Job Server

  • A
    license
    A
    quality
    A
    maintenance
    Local-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.
    16
    10
    MIT

Related Servers

  • A
    license
    B
    quality
    A
    maintenance
    A secure MCP server for shell operations, terminal management, and process control, enabling AI assistants to safely execute commands and manage interactive sessions.
    13
    704 npm
    6
    MIT
  • F
    license
    A
    quality
    A
    maintenance
    An 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
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    An 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
  • A
    license
    A
    quality
    C
    maintenance
    MCP 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.
    8
    8
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    A 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 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    A lightweight, cross-platform MCP server for managing background processes. Enables AI coding agents to spawn, monitor, and interact with long-lived processes.
    MIT

TDQS

A4.2/5.0

Scored across 7 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness5/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues