Integration

Better Stack integration

Better Stack (formerly Better Uptime) is an observability platform for uptime monitoring, incident management, on-call scheduling, and public status pages. The Uptime API (https://uptime.betterstack.com/api/v2) lets you programmatically manage monitors, monitor groups, heartbeats, status pages, on-call calendars, escalation policies, metadata, and incidents (incidents endpoints live under /api/v3). Logs and Telemetry features are exposed by a separate API at https://telemetry.betterstack.com and are not covered by this integration.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Better Stack.Built from the 24 Better Stack tools below, on the connection you add once.

Common Better Stack use cases

  • Audit recent outages
  • Add website monitoring
  • Rename a monitor group
  • Monitor a scheduled job
  • Filter monitors by label
  • Inspect a single monitor
  • Remove an obsolete group
  • Audit configured monitors
  • Group monitors by service
  • Inspect a single incident

What you can do with Better Stack

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.

Monitor, 5 operations

  • create_monitorCreate monitorPOSTCreate monitor
  • delete_monitorDelete monitorDELETEDelete monitor
  • get_monitorGet monitorGETGet monitor
  • list_monitorsList monitorsGETList all monitors
  • update_monitorUpdate monitorPATCHUpdate monitor

Heartbeat, 4 operations

  • create_heartbeatCreate heartbeatPOSTCreate heartbeat
  • delete_heartbeatDelete heartbeatDELETEDelete heartbeat
  • list_heartbeatsList heartbeatsGETList heartbeats
  • update_heartbeatUpdate heartbeatPATCHUpdate heartbeat

Incident, 4 operations

  • acknowledge_incidentAcknowledge incidentPOSTAcknowledge incident
  • get_incidentGet incidentGETGet incident
  • list_incidentsList incidentsGETList incidents
  • resolve_incidentResolve incidentPOSTResolve incident

Monitor group, 4 operations

  • create_monitor_groupCreate monitor groupPOSTCreate monitor group
  • delete_monitor_groupDelete monitor groupDELETEDelete monitor group
  • list_monitor_groupsList monitor groupsGETList monitor groups
  • update_monitor_groupUpdate monitor groupPATCHUpdate monitor group

Status page, 4 operations

  • create_status_pageCreate status pagePOSTCreate status page
  • delete_status_pageDelete status pageDELETEDelete status page
  • list_status_pagesList status pagesGETList status pages
  • update_status_pageUpdate status pagePATCHUpdate status page

Escalation policy, 1 operation

  • list_escalation_policiesList escalation policiesGETList escalation policies

Metadata, 1 operation

  • list_metadataList metadataGETList metadata

On call calendar, 1 operation

  • list_on_call_calendarsList on call calendarsGETList on-call calendars

Better Stack API rate limits

Authenticated requests are rate limited per team. HTTP 429 is returned when the limit is exceeded.

These are the limits Better Stack documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Better Stack documentation for current values.

Use Better Stack from Claude Code, Cursor or Codex

Connect Better Stack in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Better Stack 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 Better Stack

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Better Stack once

    Add your Better Stack 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.

Better Stack integration FAQ

What can you do with the Better Stack integration?

LiveContext exposes 24 operations on Better Stack, covering monitor, heartbeat, incident and monitor group. Common uses include Audit recent outages, Add website monitoring and Rename a monitor group.

What are the Better Stack API rate limits?

Authenticated requests are rate limited per team. HTTP 429 is returned when the limit is exceeded. Limits are set by Better Stack and can depend on your plan.

Popular integrations

Browse the whole catalog