Betterstack MCP

Live

OAUTH 2.0

MONITORING

Monitoring

Monitor uptime, manage logs, and respond to incidents with Better Stack's observability platform.

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Betterstack MCP
agent · Acme Q3
Run
Acknowledge Incident in Betterstack MCP
S
betterstackmcp_acknowledge_incident
85ms
Betterstack MCP agent
Acknowledge an ongoing incident.
Sources: Betterstack MCP
betterstackmcpmcp
1 tool call
18:29
Message Claude...

Betterstack MCP tools for AI agents

CALL ANY TOOL
12 tools covering add, acknowledge.
betterstackmcp_acknowledge_incident
Acknowledge incident
Acknowledge an ongoing incident
Parameters
Name
Type
Required
Description
id
integer
Required
The ID of the incident to acknowledge
acknowledged_by
string
Optional
User email or identifier of who acknowledged the incident. Optional - when omitted, the action is attributed to the authenticated OAuth user (or "API" for team/organisation API tokens). Only pass this if the user has explicitly told you who acknowledged the incident on their behalf.
betterstackmcp_add_chart_to_dashboard
Add chart to dashboard
betterstackmcp_available_incident_escalation_policies
Available incident escalation policies
betterstackmcp_chart_alert_help
Chart alert help
betterstackmcp_clusters
Clusters
betterstackmcp_create_application
Create application
betterstackmcp_create_cloud_connection
Create cloud connection
betterstackmcp_create_incident_comment
Create incident comment
betterstackmcp_create_source
Create source
betterstackmcp_dashboard_query_help
Dashboard query help
betterstackmcp_dashboards
Dashboards
betterstackmcp_delete_chart_alert
Delete chart alert
betterstackmcp_edit_chart
Edit chart
betterstackmcp_error
Error
betterstackmcp_escalation_policies
Escalation policies
betterstackmcp_heartbeat
Heartbeat
betterstackmcp_import_dashboard
Import dashboard
betterstackmcp_incident_timeline
Incident timeline
betterstackmcp_metric_expressions
Metric expressions
betterstackmcp_metrics_query_help
Metrics query help
betterstackmcp_monitor_availability
Monitor availability
betterstackmcp_move_charts
Move charts
betterstackmcp_on_call_events
On call events
betterstackmcp_releases
Releases
betterstackmcp_remove_chart
Remove chart
betterstackmcp_resolve_incident
Resolve incident
betterstackmcp_source
Source
betterstackmcp_status_page
Status page
betterstackmcp_status_page_report_update
Update status page report
betterstackmcp_status_page_resources
Status page resources

For more tools, view docs.

Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="betterstackmcp")

mcp = MultiServerMCPClient({
"betterstackmcp": {
"url": "https://mcp.scalekit.com/betterstackmcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "betterstackmcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/betterstackmcp
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "betterstackmcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/betterstackmcp
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="betterstackmcp")
# Connect to MCP at https://mcp.scalekit.com/betterstackmcp
# Pass: Authorization: Bearer + token
Try these prompts
Paste any prompt into your agent to get started.
Get started
Copy the prompt
Copied
Update an existing metric expression?
Copy the prompt
Copied
Pause or unpause a chart alert?
Advanced
Copy the prompt
Copied
List all available teams in Better Stack Logs?
Copy the prompt
Copied
List all status pages with filtering and pagination options?
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
Betterstack MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Betterstack MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Betterstack MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Betterstack MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
Engineering Teams
DevOps assistant agent
Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
Engineering Teams
Engineering standup agent
Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.
Engineering Teams
Auto release notes agent
Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.
Test other agents
See the same per-user auth pattern across other connectors.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
ENGINEERING
Engineering standup agent
Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs into structured release notes, publish the page to Notion, and announce the release in Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
One connector today. Ten tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Betterstack as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Betterstack OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Betterstack?
Yes. Pass a tool name filter to listScopedTools so the on-call agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Betterstack.

What happens when a user revokes Betterstack access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent acknowledge incidents on behalf of anyone?
No. Incident acknowledgments and escalation changes run as the authorizing user, so on-call actions in Better Stack attribute to the responder who actually triggered them.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""betterstackmcp"": {
""url"": ""https://mcp.scalekit.com/betterstackmcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.betterstackmcp]
url = ""https://mcp.scalekit.com/betterstackmcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""betterstackmcp"": {
""url"": ""https://mcp.scalekit.com/betterstackmcp"",
""type"": ""http""
}
}
}