Skip to main content
Glama
procm-mcp

procm-mcp

by coder-ka

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-process Allow specific processes to be created

    • script (required): The script/command to allow

    • args (optional): Array of arguments

    • cwd (optional): Working directory

  • start-process Start a new process with specified script and arguments

    • script (required): The script/command to execute

    • name (optional): A friendly name for the process

    • args (optional): Array of arguments to pass to the script

    • cwd (required): Working directory for the process

    • envs (optional): Environment variables to set for the process

  • delete-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 ID

  • restart-process Restart an existing process by ID

    • id (required): The process ID

  • get-process-info Get detailed information about a process

    • id (required): The process ID

  • list-processes List all currently managed processes

    • No parameters required

  • get-process-stdout Retrieve stdout logs from a process

    • id (required): The process ID

    • chunkCount (optional): Number of recent log entries to retrieve (default: 10)

  • get-process-stderr Retrieve stderr logs from a process

    • id (required): The process ID

    • chunkCount (optional): Number of recent log entries to retrieve (default: 10)

License

MIT

Available Tools

11 tools
allow-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

    C2.8/5.0

    Scored across 11 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All tool names follow a consistent verb-noun pattern in snake_case (e.g., start-process, get-process-info). Naming is predictable and uniform.

    Tool Count5/5

    With 11 tools, the server covers process lifecycle management comprehensively without redundancy. The count feels appropriate for the domain.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A secure MCP server for executing whitelisted shell commands with resource and timeout controls, designed for integration with Claude and other MCP-compatible LLMs.
      20
      389 npm
      7
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP 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.
      8
      8
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      A secure MCP server for shell operations, terminal management, and process control, enabling AI assistants to safely execute commands and manage interactive sessions.
      13
      158 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight, cross-platform MCP server for managing background processes. Enables AI coding agents to spawn, monitor, and interact with long-lived processes.
      MIT