What can you do with the Instatus integration?

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

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.

98 toolsTokenAPI docs

Connect Instatus How integrations work

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

POSTcreate_incident
Add an incident.
POSTcreate_incident_from_template
Opens a new incident from a saved incident template.
DELETEdelete_incident
Delete incident.
GETget_incident
Get an incident.
GETlist_incidents
Get all page incidents.
POSTresolve_incident_with_template
Resolves an open incident using a saved template.
PUTupdate_incident
Update incident.

Monitor, 6 operations

POSTadd_monitors_to_group
Add Monitors to Group.
PUTassign_monitor_to_group
Moves an uptime monitor into a monitor group.
POSTcreate_monitor
Create a Monitor.
DELETEdelete_monitor
Delete a Monitor.
GETlist_monitors
Get Monitors.
PUTupdate_monitor
Update a Monitor.

Audience group, 5 operations

POSTcreate_audience_group
Create an audience group.
DELETEdelete_audience_group
Delete an audience group.
GETget_audience_group
Get an audience group.
GETlist_audience_groups
Get all your status page audience groups.
PUTupdate_audience_group
Update an audience group.

Component, 5 operations

POSTcreate_component
Create a component.
DELETEdelete_component
Delete a component.
GETget_component
Get a component.
GETlist_components
Get all your status page components.
PUTupdate_component
Update a component.

Maintenance, 5 operations

POSTcreate_maintenance
Add a maintenance.
DELETEdelete_maintenance
Delete maintenance.
GETget_maintenance
Get a maintenance.
GETlist_maintenances
Get all page maintenances.
PUTupdate_maintenance
Update maintenance.

Metric, 5 operations

POSTcreate_metric
Add a metric.
DELETEdelete_metric
Delete a metric.
GETget_metric
Get a metric.
GETlist_metrics
Get all metrics.
PUTupdate_metric
Update a metric.

Template, 5 operations

POSTcreate_template
Add a template.
DELETEdelete_template
Delete template.
GETget_template
Get a template.
GETlist_templates
Get all page templates.
PUTupdate_template
Update template.

Cron, 4 operations

POSTcreate_cron_monitor
Create a Cron Monitor.
DELETEdelete_cron_monitor
Delete a Cron Monitor.
GETlist_cron_monitors
Get Cron Monitors.
PUTupdate_cron_monitor
Update a Cron Monitor.

Escalation policie, 4 operations

POSTcreate_escalation_policy
Create Escalation Policy.
DELETEdelete_escalation_policy
Delete Escalation Policy.
GETlist_escalation_policies
Get Escalation Policies.
PUTupdate_escalation_policy
Update Escalation Policy.

Incident update, 4 operations

POSTcreate_incident_update
Add an incident update.
DELETEdelete_incident_update
Delete an incident update.
GETget_incident_update
Get an incident update.
PUTupdate_incident_update
Edit an incident update.

Maintenance update, 4 operations

POSTcreate_maintenance_update
Add a maintenance update.
DELETEdelete_maintenance_update
Delete a maintenance update.
GETget_maintenance_update
Get a maintenance update.
PUTupdate_maintenance_update
Edit a maintenance update.

Monitor alert, 4 operations

POSTcreate_monitor_alert
Create Monitor Alert.
DELETEdelete_monitor_alert
Delete Monitor Alert.
GETlist_monitor_alerts
Get Monitor Alerts.
PUTupdate_monitor_alert
Update Monitor Alert.

Routing rule, 4 operations

POSTcreate_routing_rule
Create Routing Rule.
DELETEdelete_routing_rule
Delete Routing Rule.
GETlist_routing_rules
Get Routing Rules.
PUTupdate_routing_rule
Update Routing Rule.

Subscriber, 4 operations

POSTcreate_subscriber
Add a subscriber.
DELETEdelete_subscriber
Remove a subscriber.
GETlist_subscribers
Get subscribers.
GETlist_subscribers_v1
Lists the subscribers of a status page over the older v1 route.

Cron monitor ping, 3 operations

GETping_cron_monitor_failure
Reports a failed cron job run and marks the monitor down immediately.
GETping_cron_monitor_start
Records that a cron job started, so the duration of the run can be measured.
GETping_cron_monitor_success
Records a successful cron job run and resets the missed-ping timer of the monitor.

Metric datapoint, 3 operations

POSTadd_metric_datapoint
Appends a single datapoint to a metric.
POSTadd_metric_datapoints
Appends several datapoints to a metric in one request.
DELETEdelete_metric_datapoints
Deletes every datapoint recorded on a metric, keeping the metric.

Monitors group, 3 operations

POSTcreate_monitor_group
Create Monitor Group.
DELETEdelete_monitor_group
Delete Monitor Group.
PUTupdate_monitor_group
Update Monitor Group.

On call schedule, 3 operations

POSTcreate_on_call_schedule
Create On-call Schedule.
DELETEdelete_on_call_schedule
Delete On-call Schedule.
PUTupdate_on_call_schedule
Update On-call Schedule.

Team, 3 operations

POSTadd_teammate
Add a team member.
GETlist_teammates
Get teammates.
DELETEremove_teammate
Delete a team member.

Team group, 3 operations

POSTadd_team_group_member
Add a team group member.
GETlist_team_group_members
Get team group members.
DELETEremove_team_group_member
Delete a team group member.

Workspace, 3 operations

POSTcreate_workspace
Create a workspace.
DELETEdelete_workspace
Delete a workspace.
GETlist_workspaces
Get your workspaces.

Page, 2 operations

POSTcreate_status_page
Create a status page.
GETlist_status_pages
Get your status pages.

V2, 2 operations

DELETEdelete_status_page
Delete a status page.
PUTupdate_status_page
Update a status page.

Bulk, 1 operation

POSTcreate_subscribers_bulk
Add multiple subscribers.

Log, 1 operation

GETlist_cron_monitor_logs
Get Cron Monitor Logs.

Member, 1 operation

GETlist_on_call_schedule_members
Get On-call Schedule Members.

Monitor group, 1 operation

GETrun_monitor_group_check
Runs every monitor in a group immediately.

Secure link, 1 operation

POSTregenerate_secure_link
Issues a new secure link for a private status page and invalidates the previous one.

Summary, 1 operation

GETget_cron_monitor_summary
Get Cron Monitor Summary.

User, 1 operation

GETget_user_profile
Reads 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

Create your workspace
Sign up free. Nothing to install.
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.
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.