--- title: "Better Stack Uptime MCP server for AI agents - actionlake" description: "Give Claude 220 Better Stack Uptime actions through one MCP server: catalog records. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/better-stack-uptime updated: 2026-10-22 --- 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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/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 ``` - 220 actions in one signed file - 91 read look, never change - 87 write create and update - 42 wait for a yes destructive, 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_token` Better 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 call check { 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:API`incidents.betterstack.com` **Built from** Better Stack Uptime's documentation, read 22 October 2026[betterstack.com](https://betterstack.com/docs/uptime/api/getting-started-with-uptime-api/) **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. - **91** read look, never change - **87** write create and update - **42** destructive wait 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. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `better_stack_uptime.monitors.list` List monitors | Returns list of all your monitors. | read | `monitoring.monitor.list` 32 connectors | | `better_stack_uptime.incidents.list` List incidents | List all incidents with the option to filter incidents by monitor. | read | `monitoring.incident.list` 19 connectors | | `better_stack_uptime.team_members.list` List team members | List all team members and pending invitations. | read | `identity.user.list` 474 connectors | | `better_stack_uptime.monitors.create` Create a monitor | Returns a newly created monitor or validation errors. | write | `monitoring.monitor.create` 27 connectors | | `better_stack_uptime.incidents.create` Create an incident | This will create a new incident and alert the current on-call person. | write | `monitoring.incident.create` 13 connectors | | `better_stack_uptime.team_members.invite` Invite a team member | Invites a new user to your organization. Invites existing team members to more teams. | write | `identity.user.create` 262 connectors | | `better_stack_uptime.monitors.delete` Delete a monitor | Permanently deletes an existing monitor. | destructive | `monitoring.monitor.delete` 31 connectors | | `better_stack_uptime.on_call_calendars.list` List on-call calendars | List all on-call schedules. | read | `hr.on_call_schedule.list` 11 connectors | | `better_stack_uptime.on_call_calendars.create` Create an on-call calendar | Create a new on-call schedule. Returns either the new schedule, or validation errors. | write | `hr.on_call_schedule.create` 11 connectors | | `better_stack_uptime.roles.list` List organization roles | Lists all roles in your organization — the five built-in roles (`admin`, `billing_admin`, `team_lead`, `responder`, `member`) and any custom roles. Use a… | read | `identity.role.list` 184 connectors | | `better_stack_uptime.escalation_policies.create` Create an escalation policy | Returns either a newly created escalation policy, or validation errors. | write | `hr.escalation_policy.create` 11 connectors | | `better_stack_uptime.escalation_policies.list` List escalation policys | Returns a list of existing escalation policies. | read | `hr.escalation_policy.list` 10 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. Read read Which Better Stack Uptime incidents are open, and how long has each been open? calls `better_stack_uptime.incidents.list` 2. Write write Create a monitor in Better Stack Uptime. Show me exactly what you will send before you save it. calls `better_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 monitor `better_stack_uptime.monitors.delete` - Delete a team member `better_stack_uptime.team_members.delete` - Delete an incident `better_stack_uptime.incidents.delete` - Delete an on-call calendar `better_stack_uptime.on_call_calendars.delete` - Delete an escalation policy `better_stack_uptime.escalation_policies.delete` - Delete an on-call calendar event `better_stack_uptime.on_call_events.delete` - Remove an on-call calendar rotation `better_stack_uptime.on_call_rotations.delete` - Delete an incident comment `better_stack_uptime.incident_comments.delete` - Delete a status page `better_stack_uptime.status_pages.delete` - Delete a heartbeat `better_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. do better_stack_uptime.monitors.delete confirm_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: "lead@example.com" }, { match: "better_stack_uptime.team_members.delete", approver: "lead@example.com" }, { match: "better_stack_uptime.incidents.delete", approver: "lead@example.com" } ] } ``` 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. - 1 upstream call per action all 220 Better Stack Uptime actions - 220 actions page each page of a long list is one call - 91 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Better Stack Uptime action. 220 actions by area: the id your agent calls, what it does, and its effect. **Catalog records 9** - `better_stack_uptime.catalog_records.batch_create` Batch create catalog records write - `better_stack_uptime.catalog_records.batch_replace` Batch replace catalog records write - `better_stack_uptime.catalog_records.batch_upsert` Batch upsert catalog records write - `better_stack_uptime.catalog_records.create` Create a catalog record write - `better_stack_uptime.catalog_records.delete` Delete a catalog record destructive - `better_stack_uptime.catalog_records.delete_all` Delete all catalog records of a relation destructive - `better_stack_uptime.catalog_records.get` Get a catalog record read - `better_stack_uptime.catalog_records.list` List catalog records read - `better_stack_uptime.catalog_records.update` Update a catalog record write **Incidents 8** - `better_stack_uptime.incidents.acknowledge` Acknowledge an ongoing incident write - `better_stack_uptime.incidents.create` Create an incident write - `better_stack_uptime.incidents.delete` Delete an incident destructive - `better_stack_uptime.incidents.escalate` Escalate an ongoing incident write - `better_stack_uptime.incidents.get` Get an incident read - `better_stack_uptime.incidents.list` List incidents read - `better_stack_uptime.incidents.reopen` Reopen a resolved incident write - `better_stack_uptime.incidents.resolve` Resolve an ongoing incident write **Monitors 7** - `better_stack_uptime.monitors.availability` Get a monitor's availability summary read - `better_stack_uptime.monitors.create` Create a monitor write - `better_stack_uptime.monitors.delete` Delete a monitor destructive - `better_stack_uptime.monitors.get` Get a monitor read - `better_stack_uptime.monitors.list` List monitors read - `better_stack_uptime.monitors.response_times` Get a monitor's response times read - `better_stack_uptime.monitors.update` Update a monitor write **Heartbeats 6** - `better_stack_uptime.heartbeats.availability` Get a heartbeat's availability summary read - `better_stack_uptime.heartbeats.create` Create a heartbeat write - `better_stack_uptime.heartbeats.delete` Delete a heartbeat destructive - `better_stack_uptime.heartbeats.get` Get a heartbeat read - `better_stack_uptime.heartbeats.list` List heartbeats read - `better_stack_uptime.heartbeats.update` Update a heartbeat write **On call events 6** - `better_stack_uptime.on_call_events.create` Create an on-call calendar event write - `better_stack_uptime.on_call_events.delete` Delete an on-call calendar event destructive - `better_stack_uptime.on_call_events.get` Get an on-call calendar event read - `better_stack_uptime.on_call_events.list` List on-call calendar events read - `better_stack_uptime.on_call_events.replace_future` Bulk replace future on-call calendar events write - `better_stack_uptime.on_call_events.update` Update an on-call calendar event write **Status page subscribers 6** - `better_stack_uptime.status_page_subscribers.create` Create a status page subscriber write - `better_stack_uptime.status_page_subscribers.delete` Delete a status page subscriber destructive - `better_stack_uptime.status_page_subscribers.delete_by_email` Remove a status page subscriber by email destructive - `better_stack_uptime.status_page_subscribers.get` Get a status page subscriber read - `better_stack_uptime.status_page_subscribers.list` List status page subscribers read - `better_stack_uptime.status_page_subscribers.update` Update a status page subscriber write **Team members 6** - `better_stack_uptime.team_members.change_role` Change a team member's role write - `better_stack_uptime.team_members.delete` Delete a team member destructive - `better_stack_uptime.team_members.delete_by_email` Remove a team member or invitation by email destructive - `better_stack_uptime.team_members.get` Get a team member read - `better_stack_uptime.team_members.invite` Invite a team member write - `better_stack_uptime.team_members.list` List team members read **Amazon SNS integrations 5** - `better_stack_uptime.amazon_sns_integrations.create` Create an Amazon SNS integration write - `better_stack_uptime.amazon_sns_integrations.delete` Delete an Amazon SNS integration destructive - `better_stack_uptime.amazon_sns_integrations.get` Get an Amazon SNS integration read - `better_stack_uptime.amazon_sns_integrations.list` List Amazon SNS integrations read - `better_stack_uptime.amazon_sns_integrations.update` Update an Amazon SNS integration write **Aws cloudwatch integrations 5** - `better_stack_uptime.aws_cloudwatch_integrations.create` Create an AWS CloudWatch integration write - `better_stack_uptime.aws_cloudwatch_integrations.delete` Delete an AWS CloudWatch integration destructive - `better_stack_uptime.aws_cloudwatch_integrations.get` Get an AWS CloudWatch integration read - `better_stack_uptime.aws_cloudwatch_integrations.list` List AWS CloudWatch integrations read - `better_stack_uptime.aws_cloudwatch_integrations.update` Update an AWS CloudWatch integration write **Azure integrations 5** - `better_stack_uptime.azure_integrations.create` Create an Azure integration write - `better_stack_uptime.azure_integrations.delete` Delete an Azure integration destructive - `better_stack_uptime.azure_integrations.get` Get an Azure integration read - `better_stack_uptime.azure_integrations.list` List Azure integrations read - `better_stack_uptime.azure_integrations.update` Update an Azure integration write **Catalog attributes 5** - `better_stack_uptime.catalog_attributes.create` Create a catalog attribute write - `better_stack_uptime.catalog_attributes.delete` Delete a catalog attribute destructive - `better_stack_uptime.catalog_attributes.get` Get a catalog attribute read - `better_stack_uptime.catalog_attributes.list` List catalog attributes read - `better_stack_uptime.catalog_attributes.update` Update a catalog attribute write **Catalog relations 5** - `better_stack_uptime.catalog_relations.create` Create a catalog relation write - `better_stack_uptime.catalog_relations.delete` Delete a catalog relation destructive - `better_stack_uptime.catalog_relations.get` Get a catalog relation read - `better_stack_uptime.catalog_relations.list` List catalog relations read - `better_stack_uptime.catalog_relations.update` Update a catalog relation write **Datadog integrations 5** - `better_stack_uptime.datadog_integrations.create` Create a Datadog integration write - `better_stack_uptime.datadog_integrations.delete` Delete a Datadog integration destructive - `better_stack_uptime.datadog_integrations.get` Get a Datadog integration read - `better_stack_uptime.datadog_integrations.list` List Datadog integrations read - `better_stack_uptime.datadog_integrations.update` Update a Datadog integration write **Elastic integrations 5** - `better_stack_uptime.elastic_integrations.create` Create an Elastic integration write - `better_stack_uptime.elastic_integrations.delete` Delete an Elastic integration destructive - `better_stack_uptime.elastic_integrations.get` Get an Elastic integration read - `better_stack_uptime.elastic_integrations.list` List Elastic integrations read - `better_stack_uptime.elastic_integrations.update` Update an Elastic integration write **Email integrations 5** - `better_stack_uptime.email_integrations.create` Create an email integration write - `better_stack_uptime.email_integrations.delete` Delete an email integration destructive - `better_stack_uptime.email_integrations.get` Get an email integration read - `better_stack_uptime.email_integrations.list` List email integrations read - `better_stack_uptime.email_integrations.update` Update an email integration write **Escalation policies 5** - `better_stack_uptime.escalation_policies.create` Create an escalation policy write - `better_stack_uptime.escalation_policies.delete` Delete an escalation policy destructive - `better_stack_uptime.escalation_policies.get` Get an escalation policy read - `better_stack_uptime.escalation_policies.list` List escalation policys read - `better_stack_uptime.escalation_policies.update` Update an escalation policy write **Escalation policy groups 5** - `better_stack_uptime.escalation_policy_groups.create` Create an escalation policy group write - `better_stack_uptime.escalation_policy_groups.delete` Delete an escalation policy group destructive - `better_stack_uptime.escalation_policy_groups.get` Get an escalation policy group read - `better_stack_uptime.escalation_policy_groups.list` List escalation policy groups read - `better_stack_uptime.escalation_policy_groups.update` Update an escalation policy group write **Google monitoring integrations 5** - `better_stack_uptime.google_monitoring_integrations.create` Create a Google Monitoring integration write - `better_stack_uptime.google_monitoring_integrations.delete` Delete a Google Monitoring integration destructive - `better_stack_uptime.google_monitoring_integrations.get` Get a Google Monitoring integration read - `better_stack_uptime.google_monitoring_integrations.list` List Google Monitoring integrations read - `better_stack_uptime.google_monitoring_integrations.update` Update a Google Monitoring integration write **Grafana integrations 5** - `better_stack_uptime.grafana_integrations.create` Create a Grafana integration write - `better_stack_uptime.grafana_integrations.delete` Delete a Grafana integration destructive - `better_stack_uptime.grafana_integrations.get` Get a Grafana integration read - `better_stack_uptime.grafana_integrations.list` List Grafana integrations read - `better_stack_uptime.grafana_integrations.update` Update a Grafana integration write **Heartbeat groups 5** - `better_stack_uptime.heartbeat_groups.create` Create a heartbeat group write - `better_stack_uptime.heartbeat_groups.delete` Delete a heartbeat group destructive - `better_stack_uptime.heartbeat_groups.get` Get a heartbeat group read - `better_stack_uptime.heartbeat_groups.list` List heartbeat groups read - `better_stack_uptime.heartbeat_groups.update` Update a heartbeat group write **Incident comments 5** - `better_stack_uptime.incident_comments.create` Create an incident comment write - `better_stack_uptime.incident_comments.delete` Delete an incident comment destructive - `better_stack_uptime.incident_comments.get` Get an incident comment read - `better_stack_uptime.incident_comments.list` List incident comments read - `better_stack_uptime.incident_comments.update` Update an incident comment write **Incoming webhooks 5** - `better_stack_uptime.incoming_webhooks.create` Create an incoming webhook integration write - `better_stack_uptime.incoming_webhooks.delete` Delete an incoming webhook integration destructive - `better_stack_uptime.incoming_webhooks.get` Get an incoming webhook integration read - `better_stack_uptime.incoming_webhooks.list` List incoming webhook integrations read - `better_stack_uptime.incoming_webhooks.update` Update an incoming webhook integration write **Monitor groups 5** - `better_stack_uptime.monitor_groups.create` Create a monitor group write - `better_stack_uptime.monitor_groups.delete` Delete a monitor group destructive - `better_stack_uptime.monitor_groups.get` Get a monitor group read - `better_stack_uptime.monitor_groups.list` List monitor groups read - `better_stack_uptime.monitor_groups.update` Update a monitor group write **New relic integrations 5** - `better_stack_uptime.new_relic_integrations.create` Create a New Relic integration write - `better_stack_uptime.new_relic_integrations.delete` Delete a New Relic integration destructive - `better_stack_uptime.new_relic_integrations.get` Get a New Relic integration read - `better_stack_uptime.new_relic_integrations.list` List New Relic integrations read - `better_stack_uptime.new_relic_integrations.update` Update a New Relic integration write **On call calendars 5** - `better_stack_uptime.on_call_calendars.create` Create an on-call calendar write - `better_stack_uptime.on_call_calendars.delete` Delete an on-call calendar destructive - `better_stack_uptime.on_call_calendars.get` Get an on-call calendar read - `better_stack_uptime.on_call_calendars.list` List on-call calendars read - `better_stack_uptime.on_call_calendars.update` Update an on-call calendar write **Outgoing email integrations 5** - `better_stack_uptime.outgoing_email_integrations.create` Create an outgoing email integration write - `better_stack_uptime.outgoing_email_integrations.delete` Delete an outgoing email integration destructive - `better_stack_uptime.outgoing_email_integrations.get` Get an outgoing email integration read - `better_stack_uptime.outgoing_email_integrations.list` List outgoing email integrations read - `better_stack_uptime.outgoing_email_integrations.update` Update an outgoing email integration write **Outgoing webhook integrations 5** - `better_stack_uptime.outgoing_webhook_integrations.create` Create an outgoing webhook integration write - `better_stack_uptime.outgoing_webhook_integrations.delete` Delete an outgoing webhook integration destructive - `better_stack_uptime.outgoing_webhook_integrations.get` Get an outgoing webhook integration read - `better_stack_uptime.outgoing_webhook_integrations.list` List outgoing webhook integrations read - `better_stack_uptime.outgoing_webhook_integrations.update` Update an outgoing webhook integration write **Pagerduty integrations 5** - `better_stack_uptime.pagerduty_integrations.create` Create a PagerDuty integration write - `better_stack_uptime.pagerduty_integrations.delete` Delete a PagerDuty integration destructive - `better_stack_uptime.pagerduty_integrations.get` Get a PagerDuty integration read - `better_stack_uptime.pagerduty_integrations.list` List PagerDuty integrations read - `better_stack_uptime.pagerduty_integrations.update` Update a PagerDuty integration write **Prometheus integrations 5** - `better_stack_uptime.prometheus_integrations.create` Create a Prometheus integration write - `better_stack_uptime.prometheus_integrations.delete` Delete a Prometheus integration destructive - `better_stack_uptime.prometheus_integrations.get` Get a Prometheus integration read - `better_stack_uptime.prometheus_integrations.list` List Prometheus integrations read - `better_stack_uptime.prometheus_integrations.update` Update a Prometheus integration write **Severities 5** - `better_stack_uptime.severities.create` Create a severity write - `better_stack_uptime.severities.delete` Delete a severity destructive - `better_stack_uptime.severities.get` Get a severity read - `better_stack_uptime.severities.list` List severitys read - `better_stack_uptime.severities.update` Update a severity write **Severity groups 5** - `better_stack_uptime.severity_groups.create` Create a severity group write - `better_stack_uptime.severity_groups.delete` Delete a severity group destructive - `better_stack_uptime.severity_groups.get` Get a severity group read - `better_stack_uptime.severity_groups.list` List severity groups read - `better_stack_uptime.severity_groups.update` Update a severity group write **Splunk on call integrations 5** - `better_stack_uptime.splunk_on_call_integrations.create` Create a Splunk On-Call integration write - `better_stack_uptime.splunk_on_call_integrations.delete` Delete a Splunk On-Call integration destructive - `better_stack_uptime.splunk_on_call_integrations.get` Get a Splunk On-Call integration read - `better_stack_uptime.splunk_on_call_integrations.list` List Splunk On-Call integrations read - `better_stack_uptime.splunk_on_call_integrations.update` Update a Splunk On-Call integration write **Status page groups 5** - `better_stack_uptime.status_page_groups.create` Create a status page group write - `better_stack_uptime.status_page_groups.delete` Delete a status page group destructive - `better_stack_uptime.status_page_groups.get` Get a status page group read - `better_stack_uptime.status_page_groups.list` List status page groups read - `better_stack_uptime.status_page_groups.update` Update a status page group write **Status page resources 5** - `better_stack_uptime.status_page_resources.create` Create a status page resource write - `better_stack_uptime.status_page_resources.delete` Delete a status page resource destructive - `better_stack_uptime.status_page_resources.get` Get a status page resource read - `better_stack_uptime.status_page_resources.list` List status page resources read - `better_stack_uptime.status_page_resources.update` Update a status page resource write **Status page sections 5** - `better_stack_uptime.status_page_sections.create` Create a status page section write - `better_stack_uptime.status_page_sections.delete` Delete a status page section destructive - `better_stack_uptime.status_page_sections.get` Get a status page section read - `better_stack_uptime.status_page_sections.list` List status page sections read - `better_stack_uptime.status_page_sections.update` Update a status page section write **Status pages 5** - `better_stack_uptime.status_pages.create` Create a status page write - `better_stack_uptime.status_pages.delete` Delete a status page destructive - `better_stack_uptime.status_pages.get` Get a status page read - `better_stack_uptime.status_pages.list` List status pages read - `better_stack_uptime.status_pages.update` Update a status page write **Status reports 5** - `better_stack_uptime.status_reports.create` Create a status report write - `better_stack_uptime.status_reports.delete` Delete a status report destructive - `better_stack_uptime.status_reports.get` Get a status report read - `better_stack_uptime.status_reports.list` List status reports read - `better_stack_uptime.status_reports.update` Update a status report write **Status updates 5** - `better_stack_uptime.status_updates.create` Create a status update write - `better_stack_uptime.status_updates.delete` Delete a status update destructive - `better_stack_uptime.status_updates.get` Get a status update read - `better_stack_uptime.status_updates.list` List status updates read - `better_stack_uptime.status_updates.update` Update a status update write **Jira integrations 3** - `better_stack_uptime.jira_integrations.get` Get a Jira integration read - `better_stack_uptime.jira_integrations.list` List Jira integrations read - `better_stack_uptime.jira_integrations.update` Update a Jira integration write **On call rotations 3** - `better_stack_uptime.on_call_rotations.create` Create an on-call calendar rotation write - `better_stack_uptime.on_call_rotations.delete` Remove an on-call calendar rotation destructive - `better_stack_uptime.on_call_rotations.get` Get an on-call calendar rotation read **Slack integrations 3** - `better_stack_uptime.slack_integrations.get` Get a Slack integration read - `better_stack_uptime.slack_integrations.list` List Slack integrations read - `better_stack_uptime.slack_integrations.update` Update a Slack integration write **Metadata 2** - `better_stack_uptime.metadata.list` List metadata records read - `better_stack_uptime.metadata.upsert` Create, update or delete a metadata record write **Usage 2** - `better_stack_uptime.usage.get_product` Get usage of one product read - `better_stack_uptime.usage.overview` Get usage overview across products read **Incident timeline 1** - `better_stack_uptime.incident_timeline.list` List incident timeline events read **Monitor group monitors 1** - `better_stack_uptime.monitor_group_monitors.list` List monitor of a monitor groups read **Roles 1** - `better_stack_uptime.roles.list` List organization roles read **Status page group pages 1** - `better_stack_uptime.status_page_group_pages.list` List status page in a status page groups read 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 - [Opsgenie 39](https://actionlake.com/connectors/opsgenie) - [FireHydrant 30](https://actionlake.com/connectors/firehydrant) - [ilert 28](https://actionlake.com/connectors/ilert) - [Squadcast 25](https://actionlake.com/connectors/squadcast) - [Rootly 23](https://actionlake.com/connectors/rootly) - [incident.io 21](https://actionlake.com/connectors/incident-io) Joins with, on shared entities - [Dynatrace 2](https://actionlake.com/connectors/dynatrace) - [Datadog 2](https://actionlake.com/connectors/datadog) - [Site24x7 2](https://actionlake.com/connectors/site24x7) - [Sumo Logic 2](https://actionlake.com/connectors/sumo-logic) - [Mitti 2](https://actionlake.com/connectors/mitti) - [Grafana 2](https://actionlake.com/connectors/grafana) Browse - [All Service desk & support connectors](https://actionlake.com/connectors/category/service-desk-and-support) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) 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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/better-stack-uptime More: https://actionlake.com/llms.txt