mcp-allquiet
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLQUIET_API_KEY | Yes | Organization API key or personal access token for All Quiet. | |
| ALLQUIET_BASE_URL | No | Base URL for the All Quiet API. Use https://allquiet.eu for the EU region. Must be https:// | https://allquiet.app |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_operationsA | List All Quiet API operations as |
| describe_operationA | Show an operation's parameters and JSON request body schema, with all $refs inlined. A schema used more than once appears in full once, tagged "$name", then as {"$see": name}. |
| call_readA | GET any All Quiet API operation. Find it first with list_operations. |
| call_writeB | Create or change something through any All Quiet API operation (JSON bodies only). |
| call_deleteA | DELETE through any All Quiet API operation. Irreversible. |
| list_incidentsA | List incidents as compact summaries. Use get_incident for the full timeline. |
| get_incidentA | Full incident as markdown (timeline, attributes, assignees) plus the intents update_incident can record on it now. |
| create_incidentC | Open an incident in one of the key's teams. |
| update_incidentB | Record an action (resolve, acknowledge, comment...) and/or change severity. |
| who_is_on_callC | Who is on call, per team, with escalation tier. |
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 10 tools
The generic call_read/call_write/call_delete tools overlap somewhat with the specific incident tools, but their descriptions clearly distinguish them as raw API access versus curated workflows. The incident-specific tools are distinct and well-scoped.
Most tools follow a consistent verb_noun pattern (list_operations, describe_operation, call_read, list_incidents, get_incident, create_incident, update_incident). The generic call_* tools deviate slightly but still follow a predictable verb style.
10 tools is a reasonable count for an API wrapper server. The generic call_* tools plus specific incident tools create slight redundancy but the count is well within acceptable range.
The server covers incident lifecycle (list, get, create, update) plus on-call lookup and raw API access for anything else. Minor gaps exist (no explicit delete_incident tool) but the generic call_delete covers that.