procm-mcp
Allows managing Docker Compose processes and other development servers by starting, stopping, and monitoring them via process management tools.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@procm-mcp start npm run dev in /home/user/project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
procm-mcp
A Model Context Protocol (MCP) server for process management.
Supported features
Secure and automatable process creation
Cleanup created processes automatically on termination (e.g. exiting claude code)
Common process management features supported, restarting, deleting, checking status or retreving stdout/stderr of processes
Using these features, LLMs start processes like development servers, docker-compose, or test watchers and check their outputs to fix bugs automatically.
Related MCP server: interactive-process-mcp
Installation
npm i -D procm-mcp.mcp.json
{
"mcpServers": {
"procm-mcp": {
"command": "node",
"args": ["./node_modules/procm-mcp/build/index.js"],
"env": {}
}
}
}Secure process creation
You can permit LLMs to use start-process tool without confirmation, because procm-mcp only allow whitelisted process creations.
LLMs will ask you to use allow-start-process tool to add specific process creation to the whitelist.
Once you allow a process creation, you don't have to confirming it anymore as long as the command and the working directory are the same.
I call it "allow-x pattern", which can balances security and usability in MCP.
Warning: Do not permit LLMs to use allow-start-process without confirmation.That means "Do anything you want to".
Tools
allow-start-processAllow specific processes to be createdscript(required): The script/command to allowargs(optional): Array of argumentscwd(optional): Working directory
start-processStart a new process with specified script and argumentsscript(required): The script/command to executename(optional): A friendly name for the processargs(optional): Array of arguments to pass to the scriptcwd(required): Working directory for the processenvs(optional): Environment variables to set for the process
delete-processStop and remove a process by ID.The default signal is SIGTERM, but SIGKILL(force killing) will be sent after 10 seconds unless the process exits.id(required): The process ID
restart-processRestart an existing process by IDid(required): The process ID
get-process-infoGet detailed information about a processid(required): The process ID
list-processesList all currently managed processesNo parameters required
get-process-stdoutRetrieve stdout logs from a processid(required): The process IDchunkCount(optional): Number of recent log entries to retrieve (default: 10)
get-process-stderrRetrieve stderr logs from a processid(required): The process IDchunkCount(optional): Number of recent log entries to retrieve (default: 10)
License
MIT
Available Tools
11 toolsallow-start-processD
Allow process creation
Inputs: script (required), args, cwd.
delete-allowed-processC
Delete an allowed process
Inputs: script (required), args, cwd.
delete-processC
Delete a process by ID
Inputs: id (required).
get-process-infoC
Get information about a process by ID
Inputs: id (required).
get-process-stderrC
Get the stderr of a process by ID
Inputs: id (required), chunkCount.
get-process-stdoutC
Get the stdout of a process by ID
Inputs: id (required), chunkCount.
get-server-idB
Get server id
Inputs: no named parameters.
list-allowed-processes-in-cwdC
List allowed processes in current working directory
Inputs: cwd.
list-processesB
List all running processes
Inputs: no named parameters.
restart-processC
Restart a process by ID
Inputs: id (required).
start-processB
Start a new process. Warning: Do not invoke background processes that will not exit automatically, and stdout/stderr will not be captured.
Inputs: script (required), cwd (required), name, args, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Each tool targets a distinct action or resource: starting, allowing, deleting, listing, retrieving info, stdout, stderr. No two tools have overlapping purposes; descriptions clearly differentiate them.
All tool names follow a consistent verb-noun pattern in snake_case (e.g., start-process, get-process-info). Naming is predictable and uniform.
With 11 tools, the server covers process lifecycle management comprehensively without redundancy. The count feels appropriate for the domain.
Core operations (start, list, info, restart, delete, output retrieval) are covered. Missing tools like graceful stop or sending input, but the set is sufficient for basic management.
Maintenance
Related MCP Connectors
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
Related MCP Servers
- AlicenseBqualityDmaintenanceA secure MCP server for executing whitelisted shell commands with resource and timeout controls, designed for integration with Claude and other MCP-compatible LLMs.20389 npm7MIT
- AlicenseAqualityDmaintenanceMCP server for managing interactive processes, enabling AI agents to start, interact with, and terminate long-running programs like SSH sessions, REPLs, and installers via read/write operations.88MIT
- AlicenseBqualityCmaintenanceA secure MCP server for shell operations, terminal management, and process control, enabling AI assistants to safely execute commands and manage interactive sessions.13158 npm6MIT
- AlicenseNot gradedqualityCmaintenanceA lightweight, cross-platform MCP server for managing background processes. Enables AI coding agents to spawn, monitor, and interact with long-lived processes.MIT