start_processLABSCO SUMMARY
One process table shared by your agents and your terminal.
An agent-launched process normally dies with the tool call and its output goes with it; mcproc keeps it running, persists the logs, and lets both the agent and you reach it afterwards. Wait-for-log is the detail that saves the most time — the start call returns when the readiness pattern appears, not after a fixed sleep.
What it is
A Rust server and CLI pair for background processes: an agent starts and stops long-running processes through MCP, and you inspect and control those same processes from the shell.
What you get
- Processes started, stopped and restarted as named background jobs
- Every process listed with its status, visible to the CLI and to other agents alike
- Logs captured and persisted, then read back or searched with regex, with time filtering and context lines
- Wait-for-log at start, so a process is reported ready only once the pattern you named appears
- Processes grouped automatically by project context
- Commands executed through version managers — mise, asdf, nvm, rbenv
- Child processes cleaned up automatically when the parent is stopped
Requirements
brew tap neptaco/tap && brew install mcproc, or build from source with the Rust toolchain and a protobuf compiler. Files follow the XDG Base Directory specification.
Setup effort
One command — brew install mcproc
USE CASES
01
Getting a dev server up and knowing it is actually ready
Start it and wait for the log line that means ready, instead of sleeping and hoping.
02
Debugging something that failed twenty minutes ago
The logs were captured and persisted, so search them by regex with context lines rather than rerunning.
03
Sorting out what is already running
List the processes with their status before starting a second copy of the same thing.
04
Restarting after a config change
Restart the named process and read the new logs, without hunting for a PID.
05
Cleaning up at the end of a session
Stop the processes by name; child processes go with the parent.
06
Running under the toolchain version the project expects
Start the process through mise, asdf, nvm or rbenv rather than whatever is on the PATH.
7 tools
Listed in project docs. Your client may show a different list.
stop_processrestart_processlist_processesget_process_logssearch_process_logsget_process_statusBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
mcproc on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
brew install mcprocMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add mcproc mcproc mcp serveAny MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"mcproc": {
"command": "mcproc",
"args": [
"mcp",
"serve"
]
}
}
}
