Get started free
All integrations

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.

24 toolsTokenAPI docs

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

  • POSTcreate_monitor

    Create monitor

  • DELETEdelete_monitor

    Delete monitor

  • GETget_monitor

    Get monitor

  • GETlist_monitors

    List all monitors

  • PATCHupdate_monitor

    Update monitor

Heartbeat, 4 operations

  • POSTcreate_heartbeat

    Create heartbeat

  • DELETEdelete_heartbeat

    Delete heartbeat

  • GETlist_heartbeats

    List heartbeats

  • PATCHupdate_heartbeat

    Update heartbeat

Incident, 4 operations

  • POSTacknowledge_incident

    Acknowledge incident

  • GETget_incident

    Get incident

  • GETlist_incidents

    List incidents

  • POSTresolve_incident

    Resolve incident

Monitor group, 4 operations

  • POSTcreate_monitor_group

    Create monitor group

  • DELETEdelete_monitor_group

    Delete monitor group

  • GETlist_monitor_groups

    List monitor groups

  • PATCHupdate_monitor_group

    Update monitor group

Status page, 4 operations

  • POSTcreate_status_page

    Create status page

  • DELETEdelete_status_page

    Delete status page

  • GETlist_status_pages

    List status pages

  • PATCHupdate_status_page

    Update status page

Escalation policy, 1 operation

  • GETlist_escalation_policies

    List escalation policies

Metadata, 1 operation

  • GETlist_metadata

    List metadata

On call calendar, 1 operation

  • GETlist_on_call_calendars

    List 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