CHIM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHIM_API_KEY | Yes | API key sent as Authorization: Api-Key …. | |
| CHIM_API_BASE_URL | No | Base URL for the CHIM API | https://api.chim.umbrella.com |
| CHIM_API_USER_AGENT | No | Overrides the User-Agent header | chim-mcp/0.1.0 |
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 |
|---|---|
| chim_save_api_keyB | Stores the CHIM API key in the user config file (~/.config/chim-mcp/config.json). |
| chim_get_change_freeze_statusA | Returns the change-freeze status for CHIM and each product suite (GET /api/status/). |
| chim_list_changesA | Lists change notifications (GET /api/v1/changes/). Supports pagination query params. |
| chim_create_changeB | Creates a Change notification (POST /api/v1/changes/). Provide the payload documented in the CHIM API guide. |
| chim_list_outagesA | Lists incident/outage notifications (GET /api/v1/outages/). Supports pagination query params. |
| chim_create_outageA | Creates an Incident/Outage notification (POST /api/v1/outages/). Provide the payload documented in the CHIM API guide. |
| chim_list_retrosA | Lists retrospectives created in CHIM (GET /api/v1/retros/). Supports pagination query params. |
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 7 tools
Each tool targets a clearly distinct resource and action: status, API key, change list/create, outage list/create, and retro list. There is no meaningful overlap between any pair of tools.
All tools follow a consistent chim_ prefix and use a verb_noun pattern (get, save, list, create). The only minor inconsistency is that 'get' is used for status while separate list operations are used for resources, but this is understandable and not chaotic.
Seven tools is a well-scoped size for a CHIM notification server covering status, authentication, and three resource types. Each tool serves a distinct purpose without bloat or obvious omissions.
The tool surface is incomplete for the apparent domain: changes and outages only have list and create, lacking update, delete, and get single. Retrospectives are only listable, with no create or management. This leaves significant operational gaps.