# Better Stack

Remote MCP server for Better Stack: SQL over logs and traces, incident handling, on-call schedules and status pages, driven from your coding agent.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · 103 installs
- Author: betterstack
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://smithery.ai/server/betterstack
- Updated: 2026-02-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/mcp/better-stack

## What it does

The server is remote. Your client talks to `https://betterstack.run.tools` over HTTP, so nothing runs on the machine. Tools cover telemetry (ClickHouse SQL over logs, spans, errors, metrics), charts and dashboards, incidents, monitors, heartbeats, on-call calendars and status pages.

Query building has a catch. Pull the instruction tool for the data type first, before asking for logs or spans. Skip that step and the SQL comes out wrong. The natural-language builders return queries in Better Stack's own dialect, so they won't run as plain ClickHouse.

Incident work is where it earns its place: read the timeline, leave a comment, escalate to a policy, resolve. Setup differs per client — a single `claude mcp add` line for Claude, a JSON block with a `url` field for Cursor and GitHub Copilot.

## Requirements
- Remote server: `https://betterstack.run.tools`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http betterstack https://betterstack.run.tools
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add better-stack --url https://betterstack.run.tools
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "better-stack": {
            "url": "https://betterstack.run.tools"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "better-stack": {
            "type": "http",
            "url": "https://betterstack.run.tools"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http better-stack https://betterstack.run.tools
```

## When to use it
- walk an incident timeline without leaving the editor
- chart error rates from logs with a SQL query
- check availability and response times for one monitor
- find who is on call this week
- append an update to a status page report

## Example prompts
- List open incidents and pull the timeline for the newest one
- Chart errors from logs over the past week and add the chart to a dashboard
- Who is on call right now?

## Similar
- [Uptimepage](https://affpapa.org/en/nevibecode/mcp/uptimepage.md) — MCP server · ★ 61 repo stars
- [Better Stack MCP](https://affpapa.org/en/nevibecode/mcp/better-stack-mcp.md) — MCP server · ★ 87 repo stars
- [logclaw-mcp-server](https://affpapa.org/en/nevibecode/mcp/logclaw-mcp-server.md) — MCP server · ★ 79 repo stars
- [Betterlytics](https://affpapa.org/en/nevibecode/mcp/betterlytics.md) — MCP server · ★ 196 repo stars
- [openstatus](https://affpapa.org/en/nevibecode/mcp/openstatus.md) — MCP server · ★ 9277 repo stars
- [Statuser](https://affpapa.org/en/nevibecode/mcp/statuser.md) — MCP server · ★ 24 repo stars

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
