better-stack-api-patternslisted

# Better Stack MCP Tools & API Patterns ## Overview Better Stack provides an official hosted MCP server at `mcp.betterstack.com` covering three products in one server: **Uptime** (monitors, on-call, incidents, status pages), **Telemetry** (logs, metrics, ClickHouse SQL, dashboards), and **Error Tracking** (exceptions, releases). When accessed through the MCP Gateway, the Bearer token is injected automatically. ## Connection & Authentication ### Bearer Token Auth Better Stack authenticates using an API token passed as a Bearer token: | Header | Description | |--------|-------------| | `Authorization` | `Bearer <your-api-token>` | ### Token Types | Token Type | Scope | Where to Generate | |------------|-------|-------------------| | **Global API Token** | All products, all teams | Better Stack > API tokens > Global API tokens | | **Uptime API Token** | Uptime product only, team-scoped | Better Stack > API tokens > (select team) > Uptime API tokens | Use the **Global API Token** for full MCP access across Uptime, Telemetry, and Error Tracking. **Environment Variables:** ```bash export BETTERSTACK_API_TOKEN="your-api-token" ``` > **IMPORTANT:** Never hardcode credentials. Always use environment variables. ### How the Gateway Injects Credentials The MCP Gateway stores your token as an org credential and automatically forwards: ``` Authorization: Bearer <stored-api-token> ``` ## Available MCP Tools ### Monitoring | Tool | Description | |------|-------------| | `li