Integration

Instatus integration

Instatus hosted status pages and uptime monitoring. Create and maintain status pages, the components shown on them, incidents and their timeline of updates, scheduled maintenance windows with their own updates, and the reusable templates an incident or a resolution can be opened from. Publish metrics and push datapoints onto them, manage teammates, team groups, subscribers (one at a time or up to 100 per request) and the audience groups subscribers are segmented into, rotate the secure link of a private page, and read the authenticated user profile and the workspaces the key can reach. The monitoring half covers uptime monitors, monitor groups, monitor alerts, routing rules, escalation policies and on-call schedules, plus cron (heartbeat) monitors with their start, success and failure pings, their ping logs and their availability summary. Authentication is an API key from Instatus user settings, sent as a bearer token in the Authorization header.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Instatus.Built from the 98 Instatus tools below, on the connection you add once.

What you can do with Instatus

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Incident, 7 operations

  • create_incidentCreate incidentPOSTAdd an incident.
  • create_incident_from_templateCreate incident from templatePOSTOpens a new incident from a saved incident template.
  • delete_incidentDelete incidentDELETEDelete incident.
  • get_incidentGet incidentGETGet an incident.
  • list_incidentsList incidentsGETGet all page incidents.
  • resolve_incident_with_templateResolve incident with templatePOSTResolves an open incident using a saved template.
  • update_incidentUpdate incidentPUTUpdate incident.

Monitor, 6 operations

  • add_monitors_to_groupAdd monitors to groupPOSTAdd Monitors to Group.
  • assign_monitor_to_groupAssign monitor to groupPUTMoves an uptime monitor into a monitor group.
  • create_monitorCreate monitorPOSTCreate a Monitor.
  • delete_monitorDelete monitorDELETEDelete a Monitor.
  • list_monitorsList monitorsGETGet Monitors.
  • update_monitorUpdate monitorPUTUpdate a Monitor.

Audience group, 5 operations

  • create_audience_groupCreate audience groupPOSTCreate an audience group.
  • delete_audience_groupDelete audience groupDELETEDelete an audience group.
  • get_audience_groupGet audience groupGETGet an audience group.
  • list_audience_groupsList audience groupsGETGet all your status page audience groups.
  • update_audience_groupUpdate audience groupPUTUpdate an audience group.

Component, 5 operations

  • create_componentCreate componentPOSTCreate a component.
  • delete_componentDelete componentDELETEDelete a component.
  • get_componentGet componentGETGet a component.
  • list_componentsList componentsGETGet all your status page components.
  • update_componentUpdate componentPUTUpdate a component.

Maintenance, 5 operations

  • create_maintenanceCreate maintenancePOSTAdd a maintenance.
  • delete_maintenanceDelete maintenanceDELETEDelete maintenance.
  • get_maintenanceGet maintenanceGETGet a maintenance.
  • list_maintenancesList maintenancesGETGet all page maintenances.
  • update_maintenanceUpdate maintenancePUTUpdate maintenance.

Metric, 5 operations

  • create_metricCreate metricPOSTAdd a metric.
  • delete_metricDelete metricDELETEDelete a metric.
  • get_metricGet metricGETGet a metric.
  • list_metricsList metricsGETGet all metrics.
  • update_metricUpdate metricPUTUpdate a metric.

Template, 5 operations

  • create_templateCreate templatePOSTAdd a template.
  • delete_templateDelete templateDELETEDelete template.
  • get_templateGet templateGETGet a template.
  • list_templatesList templatesGETGet all page templates.
  • update_templateUpdate templatePUTUpdate template.

Cron, 4 operations

  • create_cron_monitorCreate cron monitorPOSTCreate a Cron Monitor.
  • delete_cron_monitorDelete cron monitorDELETEDelete a Cron Monitor.
  • list_cron_monitorsList cron monitorsGETGet Cron Monitors.
  • update_cron_monitorUpdate cron monitorPUTUpdate a Cron Monitor.

Escalation policie, 4 operations

  • create_escalation_policyCreate escalation policyPOSTCreate Escalation Policy.
  • delete_escalation_policyDelete escalation policyDELETEDelete Escalation Policy.
  • list_escalation_policiesList escalation policiesGETGet Escalation Policies.
  • update_escalation_policyUpdate escalation policyPUTUpdate Escalation Policy.

Incident update, 4 operations

  • create_incident_updateCreate incident updatePOSTAdd an incident update.
  • delete_incident_updateDelete incident updateDELETEDelete an incident update.
  • get_incident_updateGet incident updateGETGet an incident update.
  • update_incident_updateUpdate incident updatePUTEdit an incident update.

Maintenance update, 4 operations

  • create_maintenance_updateCreate maintenance updatePOSTAdd a maintenance update.
  • delete_maintenance_updateDelete maintenance updateDELETEDelete a maintenance update.
  • get_maintenance_updateGet maintenance updateGETGet a maintenance update.
  • update_maintenance_updateUpdate maintenance updatePUTEdit a maintenance update.

Monitor alert, 4 operations

  • create_monitor_alertCreate monitor alertPOSTCreate Monitor Alert.
  • delete_monitor_alertDelete monitor alertDELETEDelete Monitor Alert.
  • list_monitor_alertsList monitor alertsGETGet Monitor Alerts.
  • update_monitor_alertUpdate monitor alertPUTUpdate Monitor Alert.

Routing rule, 4 operations

  • create_routing_ruleCreate routing rulePOSTCreate Routing Rule.
  • delete_routing_ruleDelete routing ruleDELETEDelete Routing Rule.
  • list_routing_rulesList routing rulesGETGet Routing Rules.
  • update_routing_ruleUpdate routing rulePUTUpdate Routing Rule.

Subscriber, 4 operations

  • create_subscriberCreate subscriberPOSTAdd a subscriber.
  • delete_subscriberDelete subscriberDELETERemove a subscriber.
  • list_subscribersList subscribersGETGet subscribers.
  • list_subscribers_v1List subscribers v1GETLists the subscribers of a status page over the older v1 route.

Cron monitor ping, 3 operations

  • ping_cron_monitor_failurePing cron monitor failureGETReports a failed cron job run and marks the monitor down immediately.
  • ping_cron_monitor_startPing cron monitor startGETRecords that a cron job started, so the duration of the run can be measured.
  • ping_cron_monitor_successPing cron monitor successGETRecords a successful cron job run and resets the missed-ping timer of the monitor.

Metric datapoint, 3 operations

  • add_metric_datapointAdd metric datapointPOSTAppends a single datapoint to a metric.
  • add_metric_datapointsAdd metric datapointsPOSTAppends several datapoints to a metric in one request.
  • delete_metric_datapointsDelete metric datapointsDELETEDeletes every datapoint recorded on a metric, keeping the metric.

Monitors group, 3 operations

  • create_monitor_groupCreate monitor groupPOSTCreate Monitor Group.
  • delete_monitor_groupDelete monitor groupDELETEDelete Monitor Group.
  • update_monitor_groupUpdate monitor groupPUTUpdate Monitor Group.

On call schedule, 3 operations

  • create_on_call_scheduleCreate on call schedulePOSTCreate On-call Schedule.
  • delete_on_call_scheduleDelete on call scheduleDELETEDelete On-call Schedule.
  • update_on_call_scheduleUpdate on call schedulePUTUpdate On-call Schedule.

Team, 3 operations

  • add_teammateAdd teammatePOSTAdd a team member.
  • list_teammatesList teammatesGETGet teammates.
  • remove_teammateRemove teammateDELETEDelete a team member.

Team group, 3 operations

  • add_team_group_memberAdd team group memberPOSTAdd a team group member.
  • list_team_group_membersList team group membersGETGet team group members.
  • remove_team_group_memberRemove team group memberDELETEDelete a team group member.

Workspace, 3 operations

  • create_workspaceCreate workspacePOSTCreate a workspace.
  • delete_workspaceDelete workspaceDELETEDelete a workspace.
  • list_workspacesList workspacesGETGet your workspaces.

Page, 2 operations

  • create_status_pageCreate status pagePOSTCreate a status page.
  • list_status_pagesList status pagesGETGet your status pages.

V2, 2 operations

  • delete_status_pageDelete status pageDELETEDelete a status page.
  • update_status_pageUpdate status pagePUTUpdate a status page.

Bulk, 1 operation

  • create_subscribers_bulkCreate subscribers bulkPOSTAdd multiple subscribers.

Log, 1 operation

  • list_cron_monitor_logsList cron monitor logsGETGet Cron Monitor Logs.

Member, 1 operation

  • list_on_call_schedule_membersList on call schedule membersGETGet On-call Schedule Members.

Monitor group, 1 operation

  • run_monitor_group_checkRun monitor group checkGETRuns every monitor in a group immediately.

Secure link, 1 operation

  • regenerate_secure_linkRegenerate secure linkPOSTIssues a new secure link for a private status page and invalidates the previous one.

Summary, 1 operation

  • get_cron_monitor_summaryGet cron monitor summaryGETGet Cron Monitor Summary.

User, 1 operation

  • get_user_profileGet user profileGETReads the profile of the user the API key belongs to.

Use Instatus from Claude Code, Cursor or Codex

Connect Instatus in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Instatus operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Instatus

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Instatus once

    Add your Instatus connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Instatus integration FAQ

What can you do with the Instatus integration?

LiveContext exposes 98 operations on Instatus, covering incident, monitor, audience group and component.

Popular integrations

Browse the whole catalog