otherapi_key

Instatus

Instatus is a status page and incident communication platform for managing service health, incidents, maintenance, monitors, and subscribers.

Integration

Vendor
Instatus
Category
other
Auth
API_KEY
Tools
15
Composio slug
instatus

Tools

  • Add Incident Update

    Post a public lifecycle update to an Instatus incident and change affected component states. This can send external notifications to page and affected-component subscribers when notify is true.

  • Add Maintenance Update

    Post a public progress update to an Instatus maintenance, optionally changing its lifecycle, timing, and affected component states. This can send external notifications to page and affected-component subscribers when notify is true.

  • Create Component

    Create a component on an Instatus status page. This changes the page's component configuration and can make the new component and its initial health status publicly visible.

  • Create Incident

    Create an incident on an Instatus status page with optional affected component states. The incident is published publicly by default; notify=true can send notifications to page and affected-component subscribers.

  • Create Maintenance

    Schedule or start a maintenance on an Instatus status page. The required notification controls are side-effecting: notify can contact subscribers immediately, while notify_start, notify_end, and notify_early schedule later subscriber notifi

  • Get Component

    Get the current health and configuration of one component on an Instatus status page.

  • Get Incident

    Get one Instatus incident with its affected components and update history.

  • Get Maintenance

    Get one Instatus maintenance with its schedule, affected components, automation settings, and update history.

  • List Components

    List components and their current health for one Instatus status page, including child components where present. Pass the response's next_cursor back unchanged to fetch another page.

  • List Incidents

    List incidents for an Instatus status page, optionally including or excluding lifecycle statuses.

  • List Maintenances

    List scheduled and historical maintenances for an Instatus status page.

  • List Status Pages

    List status pages available to the connected Instatus account so an agent can discover page IDs for component, incident, and maintenance operations.

  • Update Component

    Change a component's health or presentation on an Instatus status page.

  • Update Incident

    Edit an existing Instatus incident's name, timing, lifecycle status, affected components, or component states. Setting notify to true sends notifications to page and affected-component subscribers.

  • Update Maintenance

    Fully replace an Instatus maintenance's public message, schedule, lifecycle state, affected components and states, and automation settings. Call INSTATUS_GET_MAINTENANCE first and preserve unchanged values; setting notify to true sends subs

Setup

  1. Create or open a Switchy Project.
  2. Open Integrations and connect Instatus.
  3. Authorise through api_key. Switchy stores the connection against your org.
  4. Everyone in the Project can now @-mention the Instatus tools in chat.

What teammates see: by default, memories from Instatus are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Projects have used this MCP together with a given model.

How Switchy teams use it

Not enough Projects yet to publish anonymised usage stats (we require ≥ 50 Projects per week).

Starter prompts

Starter prompts for this model will land here soon.

More other MCPs

See all other MCPs

Data last verified 7 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.