Triage MCP Server
by fazalrshah
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRIAGE_PORT | No | Port for the MCP server | 9500 |
| TRIAGE_LABEL | Yes | Friendly name used in messages | |
| TRIAGE_PROCS | No | Optional: in-container processes to watch (comma-separated) | |
| TRIAGE_COMPOSE | Yes | Path to docker-compose.yaml file | |
| TRIAGE_DB_PING | No | Optional: command to ping database dependency | |
| TRIAGE_SERVICE | Yes | The main container/service name | |
| TRIAGE_PROC_MGR | No | Process manager type | |
| TRIAGE_RISKY_CMD | No | Optional: guarded recovery command | |
| TRIAGE_RISKY_DESC | No | Optional: description of the risky command |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityInactive
ResponsivenessNo issues