
waylaidwanderer/background-process-mcp
Developer toolsA Model Context Protocol (MCP) server that provides background process management capabilities. This server enables LLMs to start, stop, and monitor long-running command-line processes.
Overview
A Model Context Protocol (MCP) server that provides background process management capabilities. This server enables LLMs to start, stop, and monitor long-running command-line processes. Some AI agents, like Claude Code, can manage background processes natively, but many others can't. This project provides that capability as a standard tool for other agents like Google's Gemini CLI. It works as a separate service, making long-running task management available to a wider range of agents. I also added a TUI because I wanted to be able to monitor the processes myself. To get started, install the Background Process MCP server in your preferred client. This configuration works for most MCP clients: To connect to a standalone server, add the --port argument to the args array (e.g., ...mcp@latest", "--port", "31337"]). Use the Claude Code CLI to add the Background Process MCP server: Follow the MCP install guide, use the standard config above. Create or edit the configuration file ~/.
README
Background Process MCP
A Model Context Protocol (MCP) server that provides background process management capabilities. This server enables LLMs to start, stop, and monitor long-running command-line processes.
Motivation
Some AI agents, like Claude Code, can manage background processes natively, but many others can’t. This project provides that capability as a standard tool for other agents like Google’s Gemini CLI. It works as a separate service, making long-running task management available to a wider range of agents. I also added a TUI because I wanted to be able to monitor the processes myself.
Screenshot
Getting Started
To get started, install the Background Process MCP server in your preferred client.
Standard Config
This configuration works for most MCP clients:
{
"mcpServers": {
"backgroundProcess": {
"command": "npx",
"args": [
"@waylaidwanderer/background-process-mcp@latest"
]
}
}
}
To connect to a standalone server, add the --port argument to the args array (e.g., ...mcp@latest", "--port", "31337"]).
Tools
The following tools are exposed by the MCP server.
Architecture
The project has three components:
-
Core Service (
src/server.ts): A standalone WebSocket server that usesnode-ptyto manage child process lifecycles. It is the single source of truth for all process states. It is designed to be standalone so that other clients beyond the official TUI and MCP can be built for it. -
MCP Client (
src/mcp.ts): Exposes the Core Service functionality as a set of tools for an LLM agent. It can connect to an existing service or spawn a new one. -
TUI Client (
src/tui.ts): Anink-based terminal UI that connects to the Core Service to display process information and accept user commands.
Manual Usage
If you wish to run the server and TUI manually outside of an MCP client, you can use the following commands.
For a shorter command, you can install the package globally:
pnpm add -g @waylaidwanderer/background-process-mcp
This will give you access to the bgpm command.
1. Run the Core Service
Start the background service manually:
# With npx
npx @waylaidwanderer/background-process-mcp server
# Or, if installed globally
bgpm server
The server will listen on an available port (defaulting to 31337) and output a JSON handshake with the connection details.
2. Use the TUI
Connect the TUI to a running server via its port:
# With npx
npx @waylaidwanderer/background-process-mcp ui --port
# Or, if installed globally
bgpm ui --port
Install
npx @waylaidwanderer/background-process-mcp@latestConfiguration
{
"mcpServers": {
"backgroundProcess": {
"command": "npx",
"args": [
"@waylaidwanderer/background-process-mcp@latest"
]
}
}
}