Skip to content

About

Better Stack plugin for Claude: connect Claude to your Better Stack Incidents and Telemetry data.

Resources

Stars

5 stars

Watchers

0 watching

Forks

Latest commit

 

History

20 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Better Stack plugin for Claude Code

Connect Claude Code to your Better Stack Incidents and Telemetry data through the Model Context Protocol (MCP). Your agent can investigate incidents, check who is on call, manage uptime monitors, query logs, metrics, traces, errors and real user monitoring (RUM), and build dashboards, all in natural language.

Install

Better Stack is in Anthropic's plugin directory, which Claude Code has built in:

/plugin install better-stack

Or install it from this repository's marketplace:

/plugin marketplace add BetterStackHQ/claude-plugin
/plugin install betterstack@betterstack

Or add the MCP server using the CLI:

claude mcp add --transport http betterstack https://mcp.betterstack.com

Add --scope user to make it available across all your projects.

Alternatively, add the Better Stack MCP server to your .mcp.json manually:

{
  "mcpServers": {
    "betterstack": {
      "type": "http",
      "url": "https://mcp.betterstack.com"
    }
  }
}

Then run /mcp, select the Better Stack server and sign in through your browser (OAuth, no token configuration needed). Start a new session if the tools don't show up right away.

What you can do

Try asking your agent things like:

  • "Show me all monitors that are currently down."
  • "What's the availability of my website this month?"
  • "What incidents occurred yesterday?"
  • "Who's on-call right now?"
  • "Acknowledge incident #1234 and add a comment about the fix."
  • "Build an explore query to find HTTP 500 errors in the last hour."
  • "Create a dashboard showing error rates for my API service."

Tools

The plugin exposes the full Better Stack MCP toolset:

  • Incidents (formerly Uptime): incidents, on-call schedules and escalation, uptime monitors, heartbeats, status pages.
  • Telemetry: dashboards, charts, alerts, log/metric/error queries, sources and applications.
  • Documentation: search Better Stack docs from within Claude Code.

The complete tool reference and example prompts live in the Better Stack MCP integration docs.

Authentication

OAuth is the recommended flow. Run /mcp, select the Better Stack server and sign in through your browser. No token configuration needed.

If the tools aren't connected, the plugin's connect-betterstack skill tells you how to connect in the app you're using (Claude Code, the Claude apps or Claude Tag) instead of failing quietly. You can also ask it directly: "Set up Better Stack."

Skills

The plugin comes with skills that teach your agent how to work with Better Stack. It loads each one when the task calls for it.

Investigate

  • investigate-incident: investigates an incident or alert end to end. It finds the incident, checks who is on call, pulls the errors, logs, traces, metrics and releases around the start time, and posts a short situation report. It stays read-only unless asked to act.
  • health-check: a quick health assessment of a server or service (CPU, memory, disk, network, log levels, dependencies) with charts.

Query

  • logs-query, spans-query, metrics-query, errors-query: the SQL dialect for each data type, with the mistakes that make queries fail or return wrong numbers.
  • collector-queries: proven host, container and service queries for Better Stack Collector sources.

Dashboards and alerts

  • dashboard-builder, dashboard-layout: build dashboards that read well, with template variables and a clean grid.
  • chart-generation, chart-styling, map-hierarchy-charts: chart types, units and settings.
  • chart-alerts: threshold, relative and anomaly alerts on charts.
  • uptime-monitors: monitor types, valid settings and escalation policies.

Migrate

  • grafana-import: recreate Grafana dashboards in Better Stack.

Use in Claude chat and Cowork

  1. Open Better Stack in Customize > Plugins and add it.
  2. On the plugin's Connectors tab, add or connect the Better Stack server (https://mcp.betterstack.com) and sign in with your Better Stack account.
  3. Start a new chat.

The skills work as soon as the plugin is added, but the Better Stack tools only after step 2. On Team and Enterprise plans, an Owner adds the connector for the organization first, then each member connects with their own account. This follows Anthropic's plugin feature support page.

Use with Claude Tag (on-call in Slack)

Claude Tag can use Better Stack as an on-call first responder in your incident channels. An admin sets it up once in an Access bundle at claude.ai/admin-settings/claude-tag. Connect a dedicated Better Stack user rather than a personal login, because everyone in the covered channels acts through it.

Better Stack has to be added as a connector for your organization on claude.ai first. Then:

  1. On the bundle's Plugins tab, add this plugin. It points Claude at https://mcp.betterstack.com and brings the investigate-incident skill.
  2. On the Credentials tab, click Connect next to Custom tool, choose MCP Connector, pick Better Stack and sign in once as the dedicated Better Stack user.

To check it, start a new thread in a channel the bundle covers and ask "@Claude list open Better Stack incidents and the errors from the last hour."

Limiting available tools

Restrict which tools the agent can use with one of these headers:

  • X-MCP-Tools-Only: allowlist (only the listed tools are available)
  • X-MCP-Tools-Except: blocklist (all tools except the listed ones)
{
  "mcpServers": {
    "betterstack": {
      "type": "http",
      "url": "https://mcp.betterstack.com",
      "headers": {
        "X-MCP-Tools-Only": "monitors,monitor,incidents,incident"
      }
    }
  }
}

Maintainers

  • One version for all three plugins. The Claude (claude-plugin), Codex (codex-plugin) and Cursor (cursor-plugin) plugins always release with the same version number. A change that bumps one plugin's version bumps all three to that same number, in PRs opened together, even when the other two have nothing else to change. The version is set in .claude-plugin/plugin.json and .claude-plugin/marketplace.json (Claude), .codex-plugin/plugin.json (Codex) and .cursor-plugin/plugin.json (Cursor).
  • Skills from AI SRE. All skills except investigate-incident and connect-betterstack are built from AI SRE's skills in aisre-proxy with the sync tool in the maintainers' repository, BetterStackHQ/mcp-plugins (sync-skills/). Change them in aisre-proxy, then sync.
  • Only plugin files in this repository. The repository is the plugin: everything in it ships to people who install it, and Anthropic's plugin directory scans all of it. Scripts and agent notes here hold new versions for review, so they live in BetterStackHQ/mcp-plugins.

License

MIT. See LICENSE.

About

Better Stack plugin for Claude: connect Claude to your Better Stack Incidents and Telemetry data.

Resources

Stars

5 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages