Server data from the Official MCP Registry
A Model Context Protocol (MCP) server for process management.
A Model Context Protocol (MCP) server for process management.
procm-mcp is a process management MCP server with a reasonable security design centered on an allow-list pattern for process execution. The architecture properly restricts what processes can be spawned through a whitelist mechanism and requires explicit user approval via the allow-start-process tool. However, there are notable concerns: the allow-list comparison logic is brittle and vulnerable to bypass (args array comparison is shallow and order-sensitive), environment variable handling in spawned processes could leak sensitive values, and there is insufficient validation of the cwd parameter which could enable directory traversal attacks. The code quality is generally good with proper error handling and logging, but these security gaps require attention before production use. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 4 high severity). Package verification found 1 issue.
7 files analyzed · 11 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-coder-ka-procm-mcp": {
"args": [
"-y",
"procm-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
A Model Context Protocol (MCP) server for process management.
Using these features, LLMs start processes like development servers, docker-compose, or test watchers and check their outputs to fix bugs automatically.
npm i -D procm-mcp
.mcp.json
{
"mcpServers": {
"procm-mcp": {
"command": "node",
"args": ["./node_modules/procm-mcp/build/index.js"],
"env": {}
}
}
}
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".
allow-start-process Allow specific processes to be created
script (required): The script/command to allowargs (optional): Array of argumentscwd (optional): Working directorystart-process Start a new process with specified script and arguments
script (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 processdelete-process Stop 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 IDrestart-process Restart an existing process by ID
id (required): The process IDget-process-info Get detailed information about a process
id (required): The process IDlist-processes List all currently managed processes
get-process-stdout Retrieve stdout logs from a process
id (required): The process IDchunkCount (optional): Number of recent log entries to retrieve (default: 10)get-process-stderr Retrieve stderr logs from a process
id (required): The process IDchunkCount (optional): Number of recent log entries to retrieve (default: 10)MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.