Background Process Manager
Background Process MCP provides AI assistants with the ability to start, stop, and monitor long-running command-line processes through a server-centric architecture built by Joel (waylaidwanderer). The implementation uses a standalone WebSocket server that manages child processes via node-pty, maintaining complete process state including output history, with both an MCP client for LLM integration and an optional terminal UI for human monitoring. It addresses the limitation that many AI agents like Google's Gemini CLI cannot manage background processes natively, offering tools for process lifecycle management, output retrieval with head/tail options, and real-time monitoring, making it valuable for agents that need to run servers, watchers, build processes, or other long-running tasks while maintaining visibility into their execution status.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.
Scan details: Circle-IR · 2026-09-28 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- ai-ml
- Source
- PulseMCP
- Author type
- human
- Last scanned
- 2026-09-28
- Updated
- 2026-09-28
Use via MCP
Resolve Background Process Manager from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.