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/mcpdo { 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.
- 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 - 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 - 03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes,
checkvalidates 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:API
telemetry.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
Dashboards
84 read · 3 write · 1 destructive
List dashboards · Create a dashboard · Get a dashboard · Update a dashboard
Collectors
74 read · 2 write · 1 destructive
Create a collector · List collectors · List databases monitored by a collector · List hosts where a collector is running
Sources
72 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
Dashboard groups
63 read · 2 write · 1 destructive
Create a dashboard group · List dashboard groups · List dashboards in a dashboard group · Get a dashboard group
Exploration groups
63 read · 2 write · 1 destructive
Create an exploration group · List exploration groups · List explorations in an exploration group · Get an exploration group
Source groups
63 read · 2 write · 1 destructive
Create a source group · List source groups · List sources in a source group · Get a source group
Aws log group subscriptions
52 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
Chart comments
52 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.
| Action | What it does | Effect | Same name in |
|---|---|---|---|
better_stack.alerts.listList alerts | Returns a paginated list of all alerts accessible by the user, across all dashboards and explorations. | read | monitoring.monitor.list32 connectors |
better_stack.alerts.getGet an alert | Retrieves a single alert by its ID from any context (dashboard or exploration). | read | monitoring.monitor.get31 connectors |
better_stack.alerts.deleteDelete an alert | Permanently deletes an alert by its ID. | destructive | monitoring.monitor.delete31 connectors |
better_stack.dashboards.listList dashboards | Returns a paginated list of your team's dashboards. | read | monitoring.dashboard.list15 connectors |
better_stack.dashboards.createCreate a dashboard | Creates a new dashboard, including its variables and other properties. | write | monitoring.dashboard.create13 connectors |
better_stack.charts.listList charts | Retrieves a list of all charts on a specific dashboard. | read | monitoring.dashboard_panel.list4 connectors |
better_stack.charts.createCreate a chart | Creates a new chart on a specific dashboard. | write | monitoring.dashboard_panel.create4 connectors |
better_stack.sources.listList sources | Returns a list of your team's existing sources. | read | this connector |
better_stack.sources.createCreate a source | Returns a newly created source. | write | this connector |
better_stack.collectors.listList collectors | Returns a paginated list of collectors accessible by the authenticated user. | read | this connector |
better_stack.collectors.createCreate a collector | Creates a new Better Stack collector. | write | this connector |
better_stack.dashboards.importImport a dashboard | Creates a new dashboard from an exported JSON. | write | this 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.
- Readread
List alerts in Better Stack Telemetry and tell me what stands out.
calls
better_stack.alerts.list - Writewrite
Create a dashboard in Better Stack Telemetry. Show me exactly what you will send before you save it.
calls
better_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 alert
better_stack.alerts.delete - Delete a dashboard
better_stack.dashboards.delete - Delete a chart
better_stack.charts.delete - Delete a source
better_stack.sources.delete - Delete a collector
better_stack.collectors.delete - Delete a metric
better_stack.metrics.delete - Delete a connection
better_stack.connections.delete - Delete an exploration
better_stack.explorations.delete - Delete a source group
better_stack.source_groups.delete - Delete a chart comment
better_stack.chart_comments.delete - Delete a dashboard alert
better_stack.dashboard_alerts.delete - Delete a dashboard group
better_stack.dashboard_groups.delete - Delete a collector metrics target
better_stack.collector_targets.delete - Delete a dashboard section
better_stack.dashboard_sections.delete - Delete an exploration alert
better_stack.exploration_alerts.delete - Delete an exploration group
better_stack.exploration_groups.delete - Delete an AWS log group subscription
better_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.
Delete an alert?
intent: the user asked me to delete an alert
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]" } ]}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
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 dashboardwritebetter_stack.dashboards.deleteDelete a dashboarddestructivebetter_stack.dashboards.exportExport a dashboardreadbetter_stack.dashboards.getGet a dashboardreadbetter_stack.dashboards.importImport a dashboardwritebetter_stack.dashboards.listList dashboardsreadbetter_stack.dashboards.list_templatesList dashboard templatesreadbetter_stack.dashboards.updateUpdate a dashboardwrite
Collectors7
better_stack.collectors.createCreate a collectorwritebetter_stack.collectors.deleteDelete a collectordestructivebetter_stack.collectors.getGet a collectorreadbetter_stack.collectors.listList collectorsreadbetter_stack.collectors.list_databasesList databases monitored by a collectorreadbetter_stack.collectors.list_hostsList hosts where a collector is runningreadbetter_stack.collectors.updateUpdate a collectorwrite
Sources7
better_stack.sources.connect_awsConnect a source to an AWS accountwritebetter_stack.sources.connect_gcpConnect a source to a Google Cloud projectwritebetter_stack.sources.createCreate a sourcewritebetter_stack.sources.deleteDelete a sourcedestructivebetter_stack.sources.getGet a sourcereadbetter_stack.sources.listList sourcesreadbetter_stack.sources.updateUpdate a sourcewrite
Dashboard groups6
better_stack.dashboard_groups.createCreate a dashboard groupwritebetter_stack.dashboard_groups.deleteDelete a dashboard groupdestructivebetter_stack.dashboard_groups.getGet a dashboard groupreadbetter_stack.dashboard_groups.listList dashboard groupsreadbetter_stack.dashboard_groups.list_dashboardsList dashboards in a dashboard groupreadbetter_stack.dashboard_groups.updateUpdate a dashboard groupwrite
Exploration groups6
better_stack.exploration_groups.createCreate an exploration groupwritebetter_stack.exploration_groups.deleteDelete an exploration groupdestructivebetter_stack.exploration_groups.getGet an exploration groupreadbetter_stack.exploration_groups.listList exploration groupsreadbetter_stack.exploration_groups.list_explorationsList explorations in an exploration groupreadbetter_stack.exploration_groups.updateUpdate an exploration groupwrite
Source groups6
better_stack.source_groups.createCreate a source groupwritebetter_stack.source_groups.deleteDelete a source groupdestructivebetter_stack.source_groups.getGet a source groupreadbetter_stack.source_groups.listList source groupsreadbetter_stack.source_groups.list_sourcesList sources in a source groupreadbetter_stack.source_groups.updateUpdate a source groupwrite
Aws log group subscriptions5
better_stack.aws_log_group_subscriptions.createCreate an AWS log group subscriptionwritebetter_stack.aws_log_group_subscriptions.deleteDelete an AWS log group subscriptiondestructivebetter_stack.aws_log_group_subscriptions.getGet an AWS log group subscriptionreadbetter_stack.aws_log_group_subscriptions.listList AWS log group subscriptionsreadbetter_stack.aws_log_group_subscriptions.updateUpdate an AWS log group subscriptionwrite
Chart comments5
better_stack.chart_comments.createCreate a chart commentwritebetter_stack.chart_comments.deleteDelete a chart commentdestructivebetter_stack.chart_comments.getGet a chart commentreadbetter_stack.chart_comments.listList chart commentsreadbetter_stack.chart_comments.updateUpdate a chart commentwrite
Charts5
better_stack.charts.createCreate a chartwritebetter_stack.charts.deleteDelete a chartdestructivebetter_stack.charts.getGet a chartreadbetter_stack.charts.listList chartsreadbetter_stack.charts.updateUpdate a chartwrite
Collector targets5
better_stack.collector_targets.createCreate a collector metrics targetwritebetter_stack.collector_targets.deleteDelete a collector metrics targetdestructivebetter_stack.collector_targets.getGet a collector metrics targetreadbetter_stack.collector_targets.listList collector metrics targetsreadbetter_stack.collector_targets.updateUpdate a collector metrics targetwrite
Dashboard alerts5
better_stack.dashboard_alerts.createCreate a dashboard alertwritebetter_stack.dashboard_alerts.deleteDelete a dashboard alertdestructivebetter_stack.dashboard_alerts.getGet a dashboard alertreadbetter_stack.dashboard_alerts.listList dashboard alertsreadbetter_stack.dashboard_alerts.updateUpdate a dashboard alertwrite
Dashboard sections5
better_stack.dashboard_sections.createCreate a dashboard sectionwritebetter_stack.dashboard_sections.deleteDelete a dashboard sectiondestructivebetter_stack.dashboard_sections.getGet a dashboard sectionreadbetter_stack.dashboard_sections.listList dashboard sectionsreadbetter_stack.dashboard_sections.updateUpdate a dashboard sectionwrite
Exploration alerts5
better_stack.exploration_alerts.createCreate an exploration alertwritebetter_stack.exploration_alerts.deleteDelete an exploration alertdestructivebetter_stack.exploration_alerts.getGet an exploration alertreadbetter_stack.exploration_alerts.listList exploration alertsreadbetter_stack.exploration_alerts.updateUpdate an exploration alertwrite
Explorations5
better_stack.explorations.createCreate an explorationwritebetter_stack.explorations.deleteDelete an explorationdestructivebetter_stack.explorations.getGet an explorationreadbetter_stack.explorations.listList explorationsreadbetter_stack.explorations.updateUpdate an explorationwrite
Alerts4
better_stack.alerts.deleteDelete an alertdestructivebetter_stack.alerts.getGet an alertreadbetter_stack.alerts.listList alertsreadbetter_stack.alerts.updateUpdate an alertwrite
Connections4
better_stack.connections.createCreate a connectionwritebetter_stack.connections.deleteDelete a connectiondestructivebetter_stack.connections.getGet a connectionreadbetter_stack.connections.listList connectionsread
Metrics4
better_stack.metrics.createCreate a metricwritebetter_stack.metrics.deleteDelete a metricdestructivebetter_stack.metrics.listList metricsreadbetter_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.