procm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-server-idB | Get server id |
| allow-start-processD | Allow process creation |
| list-allowed-processes-in-cwdC | List allowed processes in current working directory |
| delete-allowed-processC | Delete an allowed process |
| start-processB | Start a new process. Warning: Do not invoke background processes that will not exit automatically, and stdout/stderr will not be captured. |
| delete-processC | Delete a process by ID |
| restart-processC | Restart a process by ID |
| get-process-infoC | Get information about a process by ID |
| list-processesB | List all running processes |
| get-process-stdoutC | Get the stdout of a process by ID |
| get-process-stderrC | Get the stderr of a process by ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
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.
All tool names follow a consistent verb-noun pattern in snake_case (e.g., start-process, get-process-info). Naming is predictable and uniform.
With 11 tools, the server covers process lifecycle management comprehensively without redundancy. The count feels appropriate for the domain.
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.