betterstack.com

In Better Stack, open API tokens, then copy an existing token or create a new one in the Global API tokens section. Docs for Uptime, Telemetry, and Errors all say to send it as Authorization: Bearer $TOKEN.

Open Better Stack Telemetry/Errors docs' token instructions at Telemetry API getting started or Errors API getting an API token. They direct you to Better Stack API tokens → Team-based tokens to create a team-scoped token for Telemetry resources, including Errors. Send it as Authorization: Bearer $TOKEN.

Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.

Open Better Stack Telemetry's SQL API instructions at SQL API. The page says to navigate to Integrations in the side menu, then create a username and password for the SQL API connection.

Create or open a Telemetry source in Better Stack, then use that source's token for HTTP ingestion. The ingestion docs at Ingesting logs via HTTP API show sending it as Authorization: Bearer $SOURCE_TOKEN.