Skip to content
actionlake
Start free

Connectors · Service desk & support

Better Stack Uptime MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Better Stack Uptime and the rest of your systems. It gives your agent 220 Better Stack Uptime actions (91 reads, 87 writes and 42 that wait for a confirmation) and holds the Better Stack Uptime credential itself, so the agent never does. It paces Better Stack Uptime's limits and records every call.

Connect Better Stack Uptime freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "better_stack_uptime.monitors.list",  intent: "check which Better Stack Uptime account is connected"}# List monitors · read · 1 upstream call
  • 220actionsin one signed file
  • 91readlook, never change
  • 87writecreate and update
  • 42wait for a yesdestructive, confirmed first

Set up

Connect Better Stack Uptime in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Better Stack Uptime.

    Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • access_tokenBetter Stack API token: a team-scoped Incidents API token (Settings > API tokens > your team > Incidents API tokens)…
    account { op: "connections.requirements", service: "better_stack_uptime" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "better_stack_uptime.monitors.list" }# list monitors · read · 1 upstream callcheck { action: "better_stack_uptime.monitors.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Better Stack Uptime at a glance

Sign-in
Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
access_token
Limits we pace to
50 calls per 10 seconds, per connection
API covered
Better Stack Incidents (Uptime) API v2/v3, JSON:APIincidents.betterstack.com
Built from
Better Stack Uptime's documentation, read 22 October 2026betterstack.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
91 of 91 reads, for up to 5 minutes; a write clears what it affects
Shared entities
3, so ask can line Better Stack Uptime up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Better Stack Uptime.

220 actions in 47 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 91readlook, never change
  • 87writecreate and update
  • 42destructivewait for a confirmation

  1. Catalog records

    9

    2 read · 5 write · 2 destructive

    Batch create catalog records · Create a catalog record · List catalog records · Batch replace catalog records

  2. Incidents

    8

    2 read · 5 write · 1 destructive

    List incidents · Create an incident · Get an incident · Delete an incident

  3. Monitors

    7

    4 read · 2 write · 1 destructive

    List monitors · Create a monitor · Get a monitor · Update a monitor

  4. Heartbeats

    6

    3 read · 2 write · 1 destructive

    Create a heartbeat · List heartbeats · Get a heartbeat's availability summary · Get a heartbeat

  5. On call events

    6

    2 read · 3 write · 1 destructive

    List on-call calendar events · Create an on-call calendar event · Get an on-call calendar event · Update an on-call calendar event

  6. Status page subscribers

    6

    2 read · 2 write · 2 destructive

    Create a status page subscriber · List status page subscribers · Get a status page subscriber · Update a status page subscriber

  7. Team members

    6

    2 read · 2 write · 2 destructive

    List team members · Invite a team member · Get a team member · Delete a team member

  8. Amazon SNS integrations

    5

    2 read · 2 write · 1 destructive

    Create an Amazon SNS integration · List Amazon SNS integrations · Get an Amazon SNS integration · Update an Amazon SNS integration

39 more areas · 167 actions
  • Aws cloudwatch integrations 5
  • Azure integrations 5
  • Catalog attributes 5
  • Catalog relations 5
  • Datadog integrations 5
  • Elastic integrations 5
  • Email integrations 5
  • Escalation policies 5
  • Escalation policy groups 5
  • Google monitoring integrations 5
  • Grafana integrations 5
  • Heartbeat groups 5
  • Incident comments 5
  • Incoming webhooks 5
  • Monitor groups 5
  • New relic integrations 5
  • On call calendars 5
  • Outgoing email integrations 5
  • Outgoing webhook integrations 5
  • Pagerduty integrations 5
  • Prometheus integrations 5
  • Severities 5
  • Severity groups 5
  • Splunk on call integrations 5
  • Status page groups 5
  • Status page resources 5
  • Status page sections 5
  • Status pages 5
  • Status reports 5
  • Status updates 5
  • Jira integrations 3
  • On call rotations 3
  • Slack integrations 3
  • Metadata 2
  • Usage 2
  • Incident timeline 1
  • Monitor group monitors 1
  • Roles 1
  • Status page group pages 1

Top actions

The Better Stack Uptime API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 52 of Better Stack Uptime's 52 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
better_stack_uptime.monitors.listList monitorsReturns list of all your monitors.readmonitoring.monitor.list32 connectors
better_stack_uptime.incidents.listList incidentsList all incidents with the option to filter incidents by monitor.readmonitoring.incident.list19 connectors
better_stack_uptime.team_members.listList team membersList all team members and pending invitations.readidentity.user.list474 connectors
better_stack_uptime.monitors.createCreate a monitorReturns a newly created monitor or validation errors.writemonitoring.monitor.create27 connectors
better_stack_uptime.incidents.createCreate an incidentThis will create a new incident and alert the current on-call person.writemonitoring.incident.create13 connectors
better_stack_uptime.team_members.inviteInvite a team memberInvites a new user to your organization. Invites existing team members to more teams.writeidentity.user.create262 connectors
better_stack_uptime.monitors.deleteDelete a monitorPermanently deletes an existing monitor.destructivemonitoring.monitor.delete31 connectors
better_stack_uptime.on_call_calendars.listList on-call calendarsList all on-call schedules.readhr.on_call_schedule.list11 connectors
better_stack_uptime.on_call_calendars.createCreate an on-call calendarCreate a new on-call schedule. Returns either the new schedule, or validation errors.writehr.on_call_schedule.create11 connectors
better_stack_uptime.roles.listList organization rolesLists all roles in your organization — the five built-in roles (`admin`, `billing_admin`, `team_lead`, `responder`, `member`) and any custom roles. Use a…readidentity.role.list184 connectors
better_stack_uptime.escalation_policies.createCreate an escalation policyReturns either a newly created escalation policy, or validation errors.writehr.escalation_policy.create11 connectors
better_stack_uptime.escalation_policies.listList escalation policysReturns a list of existing escalation policies.readhr.escalation_policy.list10 connectors

Try it

Prompts to paste into Claude.

Each one names the Better Stack Uptime actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Which Better Stack Uptime incidents are open, and how long has each been open?

    callsbetter_stack_uptime.incidents.list

  2. Writewrite

    Create a monitor in Better Stack Uptime. Show me exactly what you will send before you save it.

    callsbetter_stack_uptime.monitors.create

Governance for Better Stack Uptime

Destructive actions wait for a yes.

42 Better Stack Uptime actions are destructive. The first 10:

  • Delete a monitorbetter_stack_uptime.monitors.delete
  • Delete a team memberbetter_stack_uptime.team_members.delete
  • Delete an incidentbetter_stack_uptime.incidents.delete
  • Delete an on-call calendarbetter_stack_uptime.on_call_calendars.delete
  • Delete an escalation policybetter_stack_uptime.escalation_policies.delete
  • Delete an on-call calendar eventbetter_stack_uptime.on_call_events.delete
  • Remove an on-call calendar rotationbetter_stack_uptime.on_call_rotations.delete
  • Delete an incident commentbetter_stack_uptime.incident_comments.delete
  • Delete a status pagebetter_stack_uptime.status_pages.delete
  • Delete a heartbeatbetter_stack_uptime.heartbeats.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dobetter_stack_uptime.monitors.deleteconfirm_policy: human

Delete a monitor?

intent: the user asked me to delete a monitor

run suspended · waiting for a named person · key better-stack-uptime-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "better-stack-uptime-agent",  allowed_actions: ["better_stack_uptime.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "better_stack_uptime.monitors.delete", approver: "[email protected]" },    { match: "better_stack_uptime.team_members.delete", approver: "[email protected]" },    { match: "better_stack_uptime.incidents.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Better Stack Uptime only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Better Stack Uptime costs on actionlake.

Every Better Stack Uptime action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Better Stack Uptime refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 220 Better Stack Uptime actions
  • 220actions pageeach page of a long list is one call
  • 91reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Better Stack Uptime action.

220 actions by area: the id your agent calls, what it does, and its effect.

Catalog records9
  • better_stack_uptime.catalog_records.batch_createBatch create catalog recordswrite
  • better_stack_uptime.catalog_records.batch_replaceBatch replace catalog recordswrite
  • better_stack_uptime.catalog_records.batch_upsertBatch upsert catalog recordswrite
  • better_stack_uptime.catalog_records.createCreate a catalog recordwrite
  • better_stack_uptime.catalog_records.deleteDelete a catalog recorddestructive
  • better_stack_uptime.catalog_records.delete_allDelete all catalog records of a relationdestructive
  • better_stack_uptime.catalog_records.getGet a catalog recordread
  • better_stack_uptime.catalog_records.listList catalog recordsread
  • better_stack_uptime.catalog_records.updateUpdate a catalog recordwrite
Incidents8
  • better_stack_uptime.incidents.acknowledgeAcknowledge an ongoing incidentwrite
  • better_stack_uptime.incidents.createCreate an incidentwrite
  • better_stack_uptime.incidents.deleteDelete an incidentdestructive
  • better_stack_uptime.incidents.escalateEscalate an ongoing incidentwrite
  • better_stack_uptime.incidents.getGet an incidentread
  • better_stack_uptime.incidents.listList incidentsread
  • better_stack_uptime.incidents.reopenReopen a resolved incidentwrite
  • better_stack_uptime.incidents.resolveResolve an ongoing incidentwrite
Monitors7
  • better_stack_uptime.monitors.availabilityGet a monitor's availability summaryread
  • better_stack_uptime.monitors.createCreate a monitorwrite
  • better_stack_uptime.monitors.deleteDelete a monitordestructive
  • better_stack_uptime.monitors.getGet a monitorread
  • better_stack_uptime.monitors.listList monitorsread
  • better_stack_uptime.monitors.response_timesGet a monitor's response timesread
  • better_stack_uptime.monitors.updateUpdate a monitorwrite
Heartbeats6
  • better_stack_uptime.heartbeats.availabilityGet a heartbeat's availability summaryread
  • better_stack_uptime.heartbeats.createCreate a heartbeatwrite
  • better_stack_uptime.heartbeats.deleteDelete a heartbeatdestructive
  • better_stack_uptime.heartbeats.getGet a heartbeatread
  • better_stack_uptime.heartbeats.listList heartbeatsread
  • better_stack_uptime.heartbeats.updateUpdate a heartbeatwrite
On call events6
  • better_stack_uptime.on_call_events.createCreate an on-call calendar eventwrite
  • better_stack_uptime.on_call_events.deleteDelete an on-call calendar eventdestructive
  • better_stack_uptime.on_call_events.getGet an on-call calendar eventread
  • better_stack_uptime.on_call_events.listList on-call calendar eventsread
  • better_stack_uptime.on_call_events.replace_futureBulk replace future on-call calendar eventswrite
  • better_stack_uptime.on_call_events.updateUpdate an on-call calendar eventwrite
Status page subscribers6
  • better_stack_uptime.status_page_subscribers.createCreate a status page subscriberwrite
  • better_stack_uptime.status_page_subscribers.deleteDelete a status page subscriberdestructive
  • better_stack_uptime.status_page_subscribers.delete_by_emailRemove a status page subscriber by emaildestructive
  • better_stack_uptime.status_page_subscribers.getGet a status page subscriberread
  • better_stack_uptime.status_page_subscribers.listList status page subscribersread
  • better_stack_uptime.status_page_subscribers.updateUpdate a status page subscriberwrite
Team members6
  • better_stack_uptime.team_members.change_roleChange a team member's rolewrite
  • better_stack_uptime.team_members.deleteDelete a team memberdestructive
  • better_stack_uptime.team_members.delete_by_emailRemove a team member or invitation by emaildestructive
  • better_stack_uptime.team_members.getGet a team memberread
  • better_stack_uptime.team_members.inviteInvite a team memberwrite
  • better_stack_uptime.team_members.listList team membersread
Amazon SNS integrations5
  • better_stack_uptime.amazon_sns_integrations.createCreate an Amazon SNS integrationwrite
  • better_stack_uptime.amazon_sns_integrations.deleteDelete an Amazon SNS integrationdestructive
  • better_stack_uptime.amazon_sns_integrations.getGet an Amazon SNS integrationread
  • better_stack_uptime.amazon_sns_integrations.listList Amazon SNS integrationsread
  • better_stack_uptime.amazon_sns_integrations.updateUpdate an Amazon SNS integrationwrite
Aws cloudwatch integrations5
  • better_stack_uptime.aws_cloudwatch_integrations.createCreate an AWS CloudWatch integrationwrite
  • better_stack_uptime.aws_cloudwatch_integrations.deleteDelete an AWS CloudWatch integrationdestructive
  • better_stack_uptime.aws_cloudwatch_integrations.getGet an AWS CloudWatch integrationread
  • better_stack_uptime.aws_cloudwatch_integrations.listList AWS CloudWatch integrationsread
  • better_stack_uptime.aws_cloudwatch_integrations.updateUpdate an AWS CloudWatch integrationwrite
Azure integrations5
  • better_stack_uptime.azure_integrations.createCreate an Azure integrationwrite
  • better_stack_uptime.azure_integrations.deleteDelete an Azure integrationdestructive
  • better_stack_uptime.azure_integrations.getGet an Azure integrationread
  • better_stack_uptime.azure_integrations.listList Azure integrationsread
  • better_stack_uptime.azure_integrations.updateUpdate an Azure integrationwrite
Catalog attributes5
  • better_stack_uptime.catalog_attributes.createCreate a catalog attributewrite
  • better_stack_uptime.catalog_attributes.deleteDelete a catalog attributedestructive
  • better_stack_uptime.catalog_attributes.getGet a catalog attributeread
  • better_stack_uptime.catalog_attributes.listList catalog attributesread
  • better_stack_uptime.catalog_attributes.updateUpdate a catalog attributewrite
Catalog relations5
  • better_stack_uptime.catalog_relations.createCreate a catalog relationwrite
  • better_stack_uptime.catalog_relations.deleteDelete a catalog relationdestructive
  • better_stack_uptime.catalog_relations.getGet a catalog relationread
  • better_stack_uptime.catalog_relations.listList catalog relationsread
  • better_stack_uptime.catalog_relations.updateUpdate a catalog relationwrite
Datadog integrations5
  • better_stack_uptime.datadog_integrations.createCreate a Datadog integrationwrite
  • better_stack_uptime.datadog_integrations.deleteDelete a Datadog integrationdestructive
  • better_stack_uptime.datadog_integrations.getGet a Datadog integrationread
  • better_stack_uptime.datadog_integrations.listList Datadog integrationsread
  • better_stack_uptime.datadog_integrations.updateUpdate a Datadog integrationwrite
Elastic integrations5
  • better_stack_uptime.elastic_integrations.createCreate an Elastic integrationwrite
  • better_stack_uptime.elastic_integrations.deleteDelete an Elastic integrationdestructive
  • better_stack_uptime.elastic_integrations.getGet an Elastic integrationread
  • better_stack_uptime.elastic_integrations.listList Elastic integrationsread
  • better_stack_uptime.elastic_integrations.updateUpdate an Elastic integrationwrite
Email integrations5
  • better_stack_uptime.email_integrations.createCreate an email integrationwrite
  • better_stack_uptime.email_integrations.deleteDelete an email integrationdestructive
  • better_stack_uptime.email_integrations.getGet an email integrationread
  • better_stack_uptime.email_integrations.listList email integrationsread
  • better_stack_uptime.email_integrations.updateUpdate an email integrationwrite
Escalation policies5
  • better_stack_uptime.escalation_policies.createCreate an escalation policywrite
  • better_stack_uptime.escalation_policies.deleteDelete an escalation policydestructive
  • better_stack_uptime.escalation_policies.getGet an escalation policyread
  • better_stack_uptime.escalation_policies.listList escalation policysread
  • better_stack_uptime.escalation_policies.updateUpdate an escalation policywrite
Escalation policy groups5
  • better_stack_uptime.escalation_policy_groups.createCreate an escalation policy groupwrite
  • better_stack_uptime.escalation_policy_groups.deleteDelete an escalation policy groupdestructive
  • better_stack_uptime.escalation_policy_groups.getGet an escalation policy groupread
  • better_stack_uptime.escalation_policy_groups.listList escalation policy groupsread
  • better_stack_uptime.escalation_policy_groups.updateUpdate an escalation policy groupwrite
Google monitoring integrations5
  • better_stack_uptime.google_monitoring_integrations.createCreate a Google Monitoring integrationwrite
  • better_stack_uptime.google_monitoring_integrations.deleteDelete a Google Monitoring integrationdestructive
  • better_stack_uptime.google_monitoring_integrations.getGet a Google Monitoring integrationread
  • better_stack_uptime.google_monitoring_integrations.listList Google Monitoring integrationsread
  • better_stack_uptime.google_monitoring_integrations.updateUpdate a Google Monitoring integrationwrite
Grafana integrations5
  • better_stack_uptime.grafana_integrations.createCreate a Grafana integrationwrite
  • better_stack_uptime.grafana_integrations.deleteDelete a Grafana integrationdestructive
  • better_stack_uptime.grafana_integrations.getGet a Grafana integrationread
  • better_stack_uptime.grafana_integrations.listList Grafana integrationsread
  • better_stack_uptime.grafana_integrations.updateUpdate a Grafana integrationwrite
Heartbeat groups5
  • better_stack_uptime.heartbeat_groups.createCreate a heartbeat groupwrite
  • better_stack_uptime.heartbeat_groups.deleteDelete a heartbeat groupdestructive
  • better_stack_uptime.heartbeat_groups.getGet a heartbeat groupread
  • better_stack_uptime.heartbeat_groups.listList heartbeat groupsread
  • better_stack_uptime.heartbeat_groups.updateUpdate a heartbeat groupwrite
Incident comments5
  • better_stack_uptime.incident_comments.createCreate an incident commentwrite
  • better_stack_uptime.incident_comments.deleteDelete an incident commentdestructive
  • better_stack_uptime.incident_comments.getGet an incident commentread
  • better_stack_uptime.incident_comments.listList incident commentsread
  • better_stack_uptime.incident_comments.updateUpdate an incident commentwrite
Incoming webhooks5
  • better_stack_uptime.incoming_webhooks.createCreate an incoming webhook integrationwrite
  • better_stack_uptime.incoming_webhooks.deleteDelete an incoming webhook integrationdestructive
  • better_stack_uptime.incoming_webhooks.getGet an incoming webhook integrationread
  • better_stack_uptime.incoming_webhooks.listList incoming webhook integrationsread
  • better_stack_uptime.incoming_webhooks.updateUpdate an incoming webhook integrationwrite
Monitor groups5
  • better_stack_uptime.monitor_groups.createCreate a monitor groupwrite
  • better_stack_uptime.monitor_groups.deleteDelete a monitor groupdestructive
  • better_stack_uptime.monitor_groups.getGet a monitor groupread
  • better_stack_uptime.monitor_groups.listList monitor groupsread
  • better_stack_uptime.monitor_groups.updateUpdate a monitor groupwrite
New relic integrations5
  • better_stack_uptime.new_relic_integrations.createCreate a New Relic integrationwrite
  • better_stack_uptime.new_relic_integrations.deleteDelete a New Relic integrationdestructive
  • better_stack_uptime.new_relic_integrations.getGet a New Relic integrationread
  • better_stack_uptime.new_relic_integrations.listList New Relic integrationsread
  • better_stack_uptime.new_relic_integrations.updateUpdate a New Relic integrationwrite
On call calendars5
  • better_stack_uptime.on_call_calendars.createCreate an on-call calendarwrite
  • better_stack_uptime.on_call_calendars.deleteDelete an on-call calendardestructive
  • better_stack_uptime.on_call_calendars.getGet an on-call calendarread
  • better_stack_uptime.on_call_calendars.listList on-call calendarsread
  • better_stack_uptime.on_call_calendars.updateUpdate an on-call calendarwrite
Outgoing email integrations5
  • better_stack_uptime.outgoing_email_integrations.createCreate an outgoing email integrationwrite
  • better_stack_uptime.outgoing_email_integrations.deleteDelete an outgoing email integrationdestructive
  • better_stack_uptime.outgoing_email_integrations.getGet an outgoing email integrationread
  • better_stack_uptime.outgoing_email_integrations.listList outgoing email integrationsread
  • better_stack_uptime.outgoing_email_integrations.updateUpdate an outgoing email integrationwrite
Outgoing webhook integrations5
  • better_stack_uptime.outgoing_webhook_integrations.createCreate an outgoing webhook integrationwrite
  • better_stack_uptime.outgoing_webhook_integrations.deleteDelete an outgoing webhook integrationdestructive
  • better_stack_uptime.outgoing_webhook_integrations.getGet an outgoing webhook integrationread
  • better_stack_uptime.outgoing_webhook_integrations.listList outgoing webhook integrationsread
  • better_stack_uptime.outgoing_webhook_integrations.updateUpdate an outgoing webhook integrationwrite
Pagerduty integrations5
  • better_stack_uptime.pagerduty_integrations.createCreate a PagerDuty integrationwrite
  • better_stack_uptime.pagerduty_integrations.deleteDelete a PagerDuty integrationdestructive
  • better_stack_uptime.pagerduty_integrations.getGet a PagerDuty integrationread
  • better_stack_uptime.pagerduty_integrations.listList PagerDuty integrationsread
  • better_stack_uptime.pagerduty_integrations.updateUpdate a PagerDuty integrationwrite
Prometheus integrations5
  • better_stack_uptime.prometheus_integrations.createCreate a Prometheus integrationwrite
  • better_stack_uptime.prometheus_integrations.deleteDelete a Prometheus integrationdestructive
  • better_stack_uptime.prometheus_integrations.getGet a Prometheus integrationread
  • better_stack_uptime.prometheus_integrations.listList Prometheus integrationsread
  • better_stack_uptime.prometheus_integrations.updateUpdate a Prometheus integrationwrite
Severities5
  • better_stack_uptime.severities.createCreate a severitywrite
  • better_stack_uptime.severities.deleteDelete a severitydestructive
  • better_stack_uptime.severities.getGet a severityread
  • better_stack_uptime.severities.listList severitysread
  • better_stack_uptime.severities.updateUpdate a severitywrite
Severity groups5
  • better_stack_uptime.severity_groups.createCreate a severity groupwrite
  • better_stack_uptime.severity_groups.deleteDelete a severity groupdestructive
  • better_stack_uptime.severity_groups.getGet a severity groupread
  • better_stack_uptime.severity_groups.listList severity groupsread
  • better_stack_uptime.severity_groups.updateUpdate a severity groupwrite
Splunk on call integrations5
  • better_stack_uptime.splunk_on_call_integrations.createCreate a Splunk On-Call integrationwrite
  • better_stack_uptime.splunk_on_call_integrations.deleteDelete a Splunk On-Call integrationdestructive
  • better_stack_uptime.splunk_on_call_integrations.getGet a Splunk On-Call integrationread
  • better_stack_uptime.splunk_on_call_integrations.listList Splunk On-Call integrationsread
  • better_stack_uptime.splunk_on_call_integrations.updateUpdate a Splunk On-Call integrationwrite
Status page groups5
  • better_stack_uptime.status_page_groups.createCreate a status page groupwrite
  • better_stack_uptime.status_page_groups.deleteDelete a status page groupdestructive
  • better_stack_uptime.status_page_groups.getGet a status page groupread
  • better_stack_uptime.status_page_groups.listList status page groupsread
  • better_stack_uptime.status_page_groups.updateUpdate a status page groupwrite
Status page resources5
  • better_stack_uptime.status_page_resources.createCreate a status page resourcewrite
  • better_stack_uptime.status_page_resources.deleteDelete a status page resourcedestructive
  • better_stack_uptime.status_page_resources.getGet a status page resourceread
  • better_stack_uptime.status_page_resources.listList status page resourcesread
  • better_stack_uptime.status_page_resources.updateUpdate a status page resourcewrite
Status page sections5
  • better_stack_uptime.status_page_sections.createCreate a status page sectionwrite
  • better_stack_uptime.status_page_sections.deleteDelete a status page sectiondestructive
  • better_stack_uptime.status_page_sections.getGet a status page sectionread
  • better_stack_uptime.status_page_sections.listList status page sectionsread
  • better_stack_uptime.status_page_sections.updateUpdate a status page sectionwrite
Status pages5
  • better_stack_uptime.status_pages.createCreate a status pagewrite
  • better_stack_uptime.status_pages.deleteDelete a status pagedestructive
  • better_stack_uptime.status_pages.getGet a status pageread
  • better_stack_uptime.status_pages.listList status pagesread
  • better_stack_uptime.status_pages.updateUpdate a status pagewrite
Status reports5
  • better_stack_uptime.status_reports.createCreate a status reportwrite
  • better_stack_uptime.status_reports.deleteDelete a status reportdestructive
  • better_stack_uptime.status_reports.getGet a status reportread
  • better_stack_uptime.status_reports.listList status reportsread
  • better_stack_uptime.status_reports.updateUpdate a status reportwrite
Status updates5
  • better_stack_uptime.status_updates.createCreate a status updatewrite
  • better_stack_uptime.status_updates.deleteDelete a status updatedestructive
  • better_stack_uptime.status_updates.getGet a status updateread
  • better_stack_uptime.status_updates.listList status updatesread
  • better_stack_uptime.status_updates.updateUpdate a status updatewrite
Jira integrations3
  • better_stack_uptime.jira_integrations.getGet a Jira integrationread
  • better_stack_uptime.jira_integrations.listList Jira integrationsread
  • better_stack_uptime.jira_integrations.updateUpdate a Jira integrationwrite
On call rotations3
  • better_stack_uptime.on_call_rotations.createCreate an on-call calendar rotationwrite
  • better_stack_uptime.on_call_rotations.deleteRemove an on-call calendar rotationdestructive
  • better_stack_uptime.on_call_rotations.getGet an on-call calendar rotationread
Slack integrations3
  • better_stack_uptime.slack_integrations.getGet a Slack integrationread
  • better_stack_uptime.slack_integrations.listList Slack integrationsread
  • better_stack_uptime.slack_integrations.updateUpdate a Slack integrationwrite
Metadata2
  • better_stack_uptime.metadata.listList metadata recordsread
  • better_stack_uptime.metadata.upsertCreate, update or delete a metadata recordwrite
Usage2
  • better_stack_uptime.usage.get_productGet usage of one productread
  • better_stack_uptime.usage.overviewGet usage overview across productsread
Incident timeline1
  • better_stack_uptime.incident_timeline.listList incident timeline eventsread
Monitor group monitors1
  • better_stack_uptime.monitor_group_monitors.listList monitor of a monitor groupsread
Roles1
  • better_stack_uptime.roles.listList organization rolesread
Status page group pages1
  • better_stack_uptime.status_page_group_pages.listList status page in a status page groupsread

Questions

The Better Stack Uptime MCP server, answered.

Is there a Better Stack Uptime MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 220 Better Stack Uptime actions across catalog records, incidents, monitors and heartbeats, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Better Stack Uptime.

What do I need to connect Better Stack Uptime?

Better Stack API token: a team-scoped Incidents API token (Settings > API tokens > your team > Incidents API tokens)…. The free call account { op: "connections.requirements", service: "better_stack_uptime" } lists exactly what to paste.

Can an AI agent delete or change things in Better Stack Uptime?

Only if its key allows it, and only with an explicit confirmation. 42 Better Stack Uptime actions are destructive, including delete a monitor, delete a team member and delete an incident. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Better Stack Uptime API limit?

actionlake paces every call to the limits in the Better Stack Uptime service file: 50 calls per 10 seconds per connection. Repeated reads are answered from cache (91 Better Stack Uptime actions can be), which never reaches Better Stack Uptime.

What does a Better Stack Uptime action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (220 Better Stack Uptime actions page). Cache hits, searches, dry runs and calls Better Stack Uptime refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Better Stack Uptime API does it cover?

The Better Stack Incidents (Uptime) API v2/v3, JSON:API at incidents.betterstack.com. It is built from Better Stack Uptime's documentation as read on 22 October 2026. 220 actions in 47 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Better Stack Uptime data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Better Stack Uptime credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Better Stack Uptime

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Better Stack Uptime; the name is the vendor's own. Counts are from the Better Stack Uptime service file, version 1.0.0.

Give your agent Better Stack Uptime today.

Connect Better Stack Uptime freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.