procm-mcp
Allows managing Docker Compose processes and other development servers by starting, stopping, and monitoring them via process management tools.
Click on "Install 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-mcpstart 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: Terminal Controller for 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
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/coder-ka/procm-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server