A Model Context Protocol (MCP) server for process management.
Procm MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Procm MCP directly instead of describing what you should do. A Model Context Protocol (MCP) server for process management.
Once Procm MCP is connected, these are the calls the assistant has available:
allow-start — process Allow specific processes to be createdstart — process Start a new process with specified script and argumentsdelete — 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 processrestart — process Restart an existing process by IDget-process — info Get detailed information about a processlist — processes List all currently managed processesSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Procm MCP's toolset — allow-start, start, delete and 3 more — is a fair guide to whether it matches your workflow. It is maintained by coder-ka; 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.
| Tool | What it does |
|---|---|
| allow-start | process Allow specific processes to be created |
| start | process Start a new process with specified script and arguments |
| 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. |
| restart | process Restart an existing process by ID |
| get-process | info Get detailed information about a process |
| list | processes List all currently managed processes |
`.mcp.json`
```json
{
"mcpServers": {
"procm-mcp": {
"command": "node",
"args": ["./node_modules/procm-mcp/build/index.js"],
"env": {}
}
}
}Configuration as documented by the project. Restart the client after saving.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.