Skip to main content
Glama
Sign In
MCP Background Task Server

MCP Background Task Server

by nanoseil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Background Task Server

No user-submitted related servers found.

    Related Servers

    • mcp-sidecar

      lsequeiraa
      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

    • claude-hermes-bridge

      Osford1
      A
      license
      Not graded
      quality
      C
      maintenance
      A local stdio MCP server that lets Claude Desktop hand tasks to a Hermes Agent on the same machine and read the raw output and files back, job by job. Long work runs as background jobs that are polled by id, so Claude can plan, verify against the filesystem, and resume earlier sessions without blocking on tool timeouts.
      MIT

    • Claude MCP Command Server

      kimjungyeol
      F
      license
      Not graded
      quality
      D
      maintenance
      A server implementation for the Model Context Protocol (MCP) that allows Claude AI to execute commands through a command-line interface, enabling direct system interactions from within Claude.
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources