clear_finished
Clear all finished (terminated/failed) processes from the list and delete their logs
LABSCO SUMMARY
Background processes that outlive the turn.
Running a dev server through an ordinary shell call either blocks or dies with the call. Here it is named, kept alive, and its log is on disk — so 'why did the build fail' becomes a grep instead of a re-run.
What it is
A process manager exposed over MCP. Long-running bash commands are started under a name, keep running while the conversation continues, and their stdout and stderr are written to disk — so the log outlives the process and can be searched later. A CLI ships alongside for the same operations.
What you get
- A named long-running bash command started, with a description and a working directory
- Every process listed, running and terminated, with its state
- Logs retrieved, with the number of recent lines you ask for
- Logs searched by regular expression
- Input sent to a running process, as if typed at it
- One process terminated, or all of them at once
- Finished processes cleared and their logs deleted
- A failure reported immediately when a process does not start
Requirements
Node — npm install -g pm-mcp, or run it through npx. No account, no key. Commands run in your own shell with your permissions, so give it the same trust you would give a terminal.
Setup effort
One command — npx pm-mcp
USE CASES
01
Getting a dev server up and leaving it up
Start it under a name, and it keeps running while you carry on working.
02
Finding the error in a noisy log
Search the process log by regular expression instead of reading all of it.
03
Running an API and a front end together
Each process is named and listed separately, so the right log is easy to reach.
04
Answering a prompt the process is waiting on
Send input to it as if typed at the terminal.
05
Shutting the session down
Terminate one process, or all of them at once.
06
Starting from a clean slate
Clear the finished processes and delete their logs.
8 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_logs
Get logs from a process (both stdout and stderr)
grep_logs
Search process logs using a regex pattern
list_processes
List all processes (running and terminated) with their info
send_input
Send input to a running process (simulates typing into the process)
start_process
Start a long-running bash process with a given name and optional description. IMPORTANT: Always use list_processes first to check if a similar process is already running to avoid duplicates.
terminate_all_processes
Terminate all processes managed by this MCP server
terminate_process
Terminate a specific process by ID
BEFORE YOU INSTALL
What to know first
Tools you get
8 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"pm-mcp": {
"command": "npx",
"args": [
"pm-mcp"
]
}
}
}npx
TERMINAL
npx pm-mcp
