A
licenseA
qualityA
maintenanceA fire-and-poll MCP server that lets Claude Code run long background jobs without hitting tool-call timeouts.
3
MIT
MCP Background Task Server
by nanoseil
Related Servers
Alternatives to MCP Background Task Server
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityFmaintenanceMCP server for running external coding agents as background tasks inside Claude Code. Supports multiple backends including Codex, Grok, GLM, DeepSeek, and more.7MIT
- FlicenseNot gradedqualityDmaintenanceA 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.-
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that provides a bridge to Anthropic's Claude CLI. It allows MCP-compliant clients like Claude Desktop or Gemini to start new chat sessions or continue existing ones.218ISC
- AlicenseNot gradedqualityDmaintenanceA custom Model Context Protocol server that gives Claude Desktop and other LLMs access to file system operations and command execution capabilities through standardized tool interfaces.23Apache 2.0
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 issues