irskep/persistproc
MCP server to allow LLMs to manage and inspect long-running processes
Platform-specific configuration:
{
"mcpServers": {
"persistproc": {
"command": "npx",
"args": [
"-y",
"persistproc"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
A shared process layer for multi-agent development workflows
[](https://badge.fury.io/py/persistproc) [](https://www.python.org/downloads/) [](https://opensource.org/licenses/MIT)
---
> Full docs: steveasleep.com/persistproc.
persistproc?Persistproc is an MCP server and command line tool which lets agents and humans see and control long-running processes like web servers. The goal is to reduce the amount of copying and pasting you need to do while coding with AI, make it easier for you to use multiple agents, and be tool-agnostic.
There is no config file. Processes are managed entirely at runtime. This is not a replacement for supervisord.
Suppose you're working on a todo list app, and it has a dev server you normally start with npm run dev. This server watches your code for changes, typechecks it, lints it, and hot-reloads the page. When there's an error, it prints the error to your terminal.
If you're working with an LLM agent such as Cursor or Claude Code, if you see an error, you might copy/paste it from your terminal to the agent and ask how to fix it. Then the agent might make some changes, and maybe you hit another error, so you copy/paste again, and the agent makes another change…etc.
If the agent could see the changes directly, you wouldn't need to do anything! With persistproc, that's possible. Instead of saying npm run dev, say persistproc npm run dev, and the agent can instantly read its output or even restart it. Otherwise, you can still see its output in your original terminal, and kill it with Ctrl+C, like your normally do.
graph TB
User[User] -->|"persistproc npm run dev"| PP[persistproc server]
PP <-->|"manages / loLoading reviews...