Instatus MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INSTATUS_API_KEY | Yes | Your Instatus API key | |
| INSTATUS_BASE_URL | No | Override for testing | https://api.instatus.com |
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_current_userA | Get the Instatus user that owns the API key (id, name, email). |
| list_status_pagesA | List the user's Instatus status pages (id, name, subdomain, custom domain, overall status). |
| get_status_overviewA | One-call answer to 'is anything down right now?' for a status page: overall state, components grouped by status, open incidents with their latest update, and upcoming or in-progress maintenance. |
| list_componentsB | List the components (services) shown on a status page with their current status and group. |
| get_componentA | Get one component with its description, status, group and uptime settings. |
| set_component_statusA | Change a component's status on the public status page without opening an incident (e.g. mark the API as DEGRADEDPERFORMANCE, or back to OPERATIONAL). This is visible to customers. |
| list_incidentsA | List incidents on a status page, newest first, with their updates and affected components. Use status to filter, e.g. 'INVESTIGATING,IDENTIFIED,MONITORING' for open incidents. |
| get_incidentA | Get one incident with its full update timeline and affected components. |
| create_incidentA | Publish a new incident on the public status page. Affected components are set to componentStatus (default PARTIALOUTAGE). Draft the wording with the user before publishing. |
| post_incident_updateA | Add a public update to an incident (e.g. move from INVESTIGATING to IDENTIFIED with a new message). If componentStatus is given it is applied to the incident's components. |
| resolve_incidentA | Resolve an incident in one step: posts a RESOLVED update and sets every affected component back to OPERATIONAL. |
| delete_incidentA | Permanently delete an incident and its history from the status page. Cannot be undone, so confirm first. |
| list_maintenancesA | List scheduled, in-progress and past maintenance windows on a status page. |
| schedule_maintenanceA | Announce a planned maintenance window. By default it starts and ends automatically, and affected components show UNDERMAINTENANCE while it runs. |
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 14 tools
Most tools have clearly distinct purposes: user/page/component/incident/maintenance operations are separated by resource and action. The main mild ambiguity is between post_incident_update and resolve_incident, since both can update incident wording/status, but resolve_incident's one-step RESOLVED + component-reset behavior makes it distinguishable.
All tool names are snake_case and consistently lead with a verb: get_, list_, set_, create_, post_, resolve_, delete_, schedule_. The pattern is predictable across every tool, with no mixing of conventions.
14 tools is well-scoped for a status-page operations server. The set covers user context, page viewing, component status, incident lifecycle, and maintenance without obvious bloat.
Incident lifecycle coverage is strong: list/get/create/update/resolve/delete. Component and maintenance surfaces are thinner (no create/update/delete component, no update/cancel maintenance), but the core public status-page workflows are covered and these gaps are likely administrative or out of scope.