Skip to content

Connectors · Observability & analytics

Better Stack Telemetry MCP server for AI agents.

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

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.alerts.list",  intent: "check which Better Stack Telemetry account is connected"}# List alerts · read · 1 upstream call
  • 92actionsin one signed file
  • 40readlook, never change
  • 35writecreate and update
  • 17wait for a yesdestructive, confirmed first

Set up

Connect Better Stack Telemetry 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 Telemetry.

    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 Telemetry API token: a team-scoped Telemetry API token (Settings > API tokens > your team > Telemetry…
    account { op: "connections.requirements", service: "better_stack" }
    # 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.alerts.list" }# list alerts · read · 1 upstream callcheck { action: "better_stack.alerts.delete", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Better Stack Telemetry 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 Telemetry API v1/v2, JSON:APItelemetry.betterstack.com
Built from
Better Stack Telemetry's documentation, read 23 October 2026betterstack.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
40 of 40 reads, for up to 5 minutes; a write clears what it affects
Shared entities
1, so ask can line Better Stack Telemetry 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 Telemetry.

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

  • 40readlook, never change
  • 35writecreate and update
  • 17destructivewait for a confirmation
  1. Dashboards

    8

    4 read · 3 write · 1 destructive

    List dashboards · Create a dashboard · Get a dashboard · Update a dashboard

  2. Collectors

    7

    4 read · 2 write · 1 destructive

    Create a collector · List collectors · List databases monitored by a collector · List hosts where a collector is running

  3. Sources

    7

    2 read · 4 write · 1 destructive

    Create a source · List sources · Connect a source to an AWS account · Connect a source to a Google Cloud project

  4. Dashboard groups

    6

    3 read · 2 write · 1 destructive

    Create a dashboard group · List dashboard groups · List dashboards in a dashboard group · Get a dashboard group

  5. Exploration groups

    6

    3 read · 2 write · 1 destructive

    Create an exploration group · List exploration groups · List explorations in an exploration group · Get an exploration group

  6. Source groups

    6

    3 read · 2 write · 1 destructive

    Create a source group · List source groups · List sources in a source group · Get a source group

  7. Aws log group subscriptions

    5

    2 read · 2 write · 1 destructive

    Create an AWS log group subscription · List AWS log group subscriptions · Get an AWS log group subscription · Update an AWS log group subscription

  8. Chart comments

    5

    2 read · 2 write · 1 destructive

    Create a chart comment · List chart comments · Get a chart comment · Update a chart comment

9 more areas · 42 actions
  • Charts 5
  • Collector targets 5
  • Dashboard alerts 5
  • Dashboard sections 5
  • Exploration alerts 5
  • Explorations 5
  • Alerts 4
  • Connections 4
  • Metrics 4

Top actions

The Better Stack Telemetry API, shaped for agents.

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

ActionWhat it doesEffectSame name in
better_stack.alerts.listList alertsReturns a paginated list of all alerts accessible by the user, across all dashboards and explorations.readmonitoring.monitor.list32 connectors
better_stack.alerts.getGet an alertRetrieves a single alert by its ID from any context (dashboard or exploration).readmonitoring.monitor.get31 connectors
better_stack.alerts.deleteDelete an alertPermanently deletes an alert by its ID.destructivemonitoring.monitor.delete31 connectors
better_stack.dashboards.listList dashboardsReturns a paginated list of your team's dashboards.readmonitoring.dashboard.list15 connectors
better_stack.dashboards.createCreate a dashboardCreates a new dashboard, including its variables and other properties.writemonitoring.dashboard.create13 connectors
better_stack.charts.listList chartsRetrieves a list of all charts on a specific dashboard.readmonitoring.dashboard_panel.list4 connectors
better_stack.charts.createCreate a chartCreates a new chart on a specific dashboard.writemonitoring.dashboard_panel.create4 connectors
better_stack.sources.listList sourcesReturns a list of your team's existing sources.readthis connector
better_stack.sources.createCreate a sourceReturns a newly created source.writethis connector
better_stack.collectors.listList collectorsReturns a paginated list of collectors accessible by the authenticated user.readthis connector
better_stack.collectors.createCreate a collectorCreates a new Better Stack collector.writethis connector
better_stack.dashboards.importImport a dashboardCreates a new dashboard from an exported JSON.writethis connector

Try it

Prompts to paste into Claude.

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

  1. Readread

    List alerts in Better Stack Telemetry and tell me what stands out.

    callsbetter_stack.alerts.list

  2. Writewrite

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

    callsbetter_stack.dashboards.create

Governance for Better Stack Telemetry

Destructive actions wait for a yes.

17 Better Stack Telemetry actions are destructive. These are all of them:

  • Delete an alertbetter_stack.alerts.delete
  • Delete a dashboardbetter_stack.dashboards.delete
  • Delete a chartbetter_stack.charts.delete
  • Delete a sourcebetter_stack.sources.delete
  • Delete a collectorbetter_stack.collectors.delete
  • Delete a metricbetter_stack.metrics.delete
  • Delete a connectionbetter_stack.connections.delete
  • Delete an explorationbetter_stack.explorations.delete
  • Delete a source groupbetter_stack.source_groups.delete
  • Delete a chart commentbetter_stack.chart_comments.delete
  • Delete a dashboard alertbetter_stack.dashboard_alerts.delete
  • Delete a dashboard groupbetter_stack.dashboard_groups.delete
  • Delete a collector metrics targetbetter_stack.collector_targets.delete
  • Delete a dashboard sectionbetter_stack.dashboard_sections.delete
  • Delete an exploration alertbetter_stack.exploration_alerts.delete
  • Delete an exploration groupbetter_stack.exploration_groups.delete
  • Delete an AWS log group subscriptionbetter_stack.aws_log_group_subscriptions.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.alerts.deleteconfirm_policy: human

Delete an alert?

intent: the user asked me to delete an alert

run suspended · waiting for a named person · key better-stack-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-agent",  allowed_actions: ["better_stack.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "better_stack.alerts.delete", approver: "[email protected]" },    { match: "better_stack.dashboards.delete", approver: "[email protected]" },    { match: "better_stack.charts.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Better Stack Telemetry only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Better Stack Telemetry costs on actionlake.

Every Better Stack Telemetry action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Better Stack Telemetry 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 92 Better Stack Telemetry actions
  • 92actions pageeach page of a long list is one call
  • 40reads 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 Telemetry action.

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

Dashboards8
  • better_stack.dashboards.createCreate a dashboardwrite
  • better_stack.dashboards.deleteDelete a dashboarddestructive
  • better_stack.dashboards.exportExport a dashboardread
  • better_stack.dashboards.getGet a dashboardread
  • better_stack.dashboards.importImport a dashboardwrite
  • better_stack.dashboards.listList dashboardsread
  • better_stack.dashboards.list_templatesList dashboard templatesread
  • better_stack.dashboards.updateUpdate a dashboardwrite
Collectors7
  • better_stack.collectors.createCreate a collectorwrite
  • better_stack.collectors.deleteDelete a collectordestructive
  • better_stack.collectors.getGet a collectorread
  • better_stack.collectors.listList collectorsread
  • better_stack.collectors.list_databasesList databases monitored by a collectorread
  • better_stack.collectors.list_hostsList hosts where a collector is runningread
  • better_stack.collectors.updateUpdate a collectorwrite
Sources7
  • better_stack.sources.connect_awsConnect a source to an AWS accountwrite
  • better_stack.sources.connect_gcpConnect a source to a Google Cloud projectwrite
  • better_stack.sources.createCreate a sourcewrite
  • better_stack.sources.deleteDelete a sourcedestructive
  • better_stack.sources.getGet a sourceread
  • better_stack.sources.listList sourcesread
  • better_stack.sources.updateUpdate a sourcewrite
Dashboard groups6
  • better_stack.dashboard_groups.createCreate a dashboard groupwrite
  • better_stack.dashboard_groups.deleteDelete a dashboard groupdestructive
  • better_stack.dashboard_groups.getGet a dashboard groupread
  • better_stack.dashboard_groups.listList dashboard groupsread
  • better_stack.dashboard_groups.list_dashboardsList dashboards in a dashboard groupread
  • better_stack.dashboard_groups.updateUpdate a dashboard groupwrite
Exploration groups6
  • better_stack.exploration_groups.createCreate an exploration groupwrite
  • better_stack.exploration_groups.deleteDelete an exploration groupdestructive
  • better_stack.exploration_groups.getGet an exploration groupread
  • better_stack.exploration_groups.listList exploration groupsread
  • better_stack.exploration_groups.list_explorationsList explorations in an exploration groupread
  • better_stack.exploration_groups.updateUpdate an exploration groupwrite
Source groups6
  • better_stack.source_groups.createCreate a source groupwrite
  • better_stack.source_groups.deleteDelete a source groupdestructive
  • better_stack.source_groups.getGet a source groupread
  • better_stack.source_groups.listList source groupsread
  • better_stack.source_groups.list_sourcesList sources in a source groupread
  • better_stack.source_groups.updateUpdate a source groupwrite
Aws log group subscriptions5
  • better_stack.aws_log_group_subscriptions.createCreate an AWS log group subscriptionwrite
  • better_stack.aws_log_group_subscriptions.deleteDelete an AWS log group subscriptiondestructive
  • better_stack.aws_log_group_subscriptions.getGet an AWS log group subscriptionread
  • better_stack.aws_log_group_subscriptions.listList AWS log group subscriptionsread
  • better_stack.aws_log_group_subscriptions.updateUpdate an AWS log group subscriptionwrite
Chart comments5
  • better_stack.chart_comments.createCreate a chart commentwrite
  • better_stack.chart_comments.deleteDelete a chart commentdestructive
  • better_stack.chart_comments.getGet a chart commentread
  • better_stack.chart_comments.listList chart commentsread
  • better_stack.chart_comments.updateUpdate a chart commentwrite
Charts5
  • better_stack.charts.createCreate a chartwrite
  • better_stack.charts.deleteDelete a chartdestructive
  • better_stack.charts.getGet a chartread
  • better_stack.charts.listList chartsread
  • better_stack.charts.updateUpdate a chartwrite
Collector targets5
  • better_stack.collector_targets.createCreate a collector metrics targetwrite
  • better_stack.collector_targets.deleteDelete a collector metrics targetdestructive
  • better_stack.collector_targets.getGet a collector metrics targetread
  • better_stack.collector_targets.listList collector metrics targetsread
  • better_stack.collector_targets.updateUpdate a collector metrics targetwrite
Dashboard alerts5
  • better_stack.dashboard_alerts.createCreate a dashboard alertwrite
  • better_stack.dashboard_alerts.deleteDelete a dashboard alertdestructive
  • better_stack.dashboard_alerts.getGet a dashboard alertread
  • better_stack.dashboard_alerts.listList dashboard alertsread
  • better_stack.dashboard_alerts.updateUpdate a dashboard alertwrite
Dashboard sections5
  • better_stack.dashboard_sections.createCreate a dashboard sectionwrite
  • better_stack.dashboard_sections.deleteDelete a dashboard sectiondestructive
  • better_stack.dashboard_sections.getGet a dashboard sectionread
  • better_stack.dashboard_sections.listList dashboard sectionsread
  • better_stack.dashboard_sections.updateUpdate a dashboard sectionwrite
Exploration alerts5
  • better_stack.exploration_alerts.createCreate an exploration alertwrite
  • better_stack.exploration_alerts.deleteDelete an exploration alertdestructive
  • better_stack.exploration_alerts.getGet an exploration alertread
  • better_stack.exploration_alerts.listList exploration alertsread
  • better_stack.exploration_alerts.updateUpdate an exploration alertwrite
Explorations5
  • better_stack.explorations.createCreate an explorationwrite
  • better_stack.explorations.deleteDelete an explorationdestructive
  • better_stack.explorations.getGet an explorationread
  • better_stack.explorations.listList explorationsread
  • better_stack.explorations.updateUpdate an explorationwrite
Alerts4
  • better_stack.alerts.deleteDelete an alertdestructive
  • better_stack.alerts.getGet an alertread
  • better_stack.alerts.listList alertsread
  • better_stack.alerts.updateUpdate an alertwrite
Connections4
  • better_stack.connections.createCreate a connectionwrite
  • better_stack.connections.deleteDelete a connectiondestructive
  • better_stack.connections.getGet a connectionread
  • better_stack.connections.listList connectionsread
Metrics4
  • better_stack.metrics.createCreate a metricwrite
  • better_stack.metrics.deleteDelete a metricdestructive
  • better_stack.metrics.listList metricsread
  • better_stack.metrics.updateUpdate a metricwrite

Questions

The Better Stack Telemetry MCP server, answered.

Is there a Better Stack Telemetry MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 92 Better Stack Telemetry actions across dashboards, collectors, sources and dashboard groups, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Better Stack Telemetry.

What do I need to connect Better Stack Telemetry?

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

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

Only if its key allows it, and only with an explicit confirmation. 17 Better Stack Telemetry actions are destructive, including delete an alert, delete a dashboard and delete a chart. 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 Telemetry API limit?

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

What does a Better Stack Telemetry action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (92 Better Stack Telemetry actions page). Cache hits, searches, dry runs and calls Better Stack Telemetry 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 Telemetry API does it cover?

The Better Stack Telemetry API v1/v2, JSON:API at telemetry.betterstack.com. It is built from Better Stack Telemetry's documentation as read on 23 October 2026. 92 actions in 17 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Better Stack Telemetry 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 Telemetry 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.

Give your agent Better Stack Telemetry today.

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