Pm MCP Server

Process Manager MCP Server - Manage long-running bash processes via MCP. Exposed over MCP by the pm mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A Model Context Protocol (MCP) server that allows Claude and other LLMs to manage long-running bash processes. Perfect for managing development servers, build processes, and other background tasks during development sessions.

• Start Processes — Launch long-running bash commands with names and descriptions
• Process Management — Terminate individual processes or all processes at once
• Log Management — Capture, retrieve, and search through stdout/stderr logs
• Process Interaction — Send input to running processes
• Failure Detection — Immediate error reporting for processes that fail to start
• CLI Tool — Standalone command-line interface for process management

Adding it to your client

The server ships on npm as pm-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• Name — "react-dev"
• Command — "npm run dev"
• Description — "React development server on port 3000"

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the pm mcp mcp server does with a few real requests.

When to reach for it

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pm MCP's toolset — Name, Command, Description — is a fair guide to whether it matches your workflow. It is maintained by patrickjm; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.