An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Better Stack (#1) to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Turn your AI agent into a reliable L1 SRE.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Better Stack.

  1. 01

    Get incident

    Fetches the specific technical timeline and payload for a single incident.

  2. 02

    List incidents

    Returns a list of all active or recent incidents in your Better Stack account.

  3. 03

    Get monitor

    Retrieves the full configuration and status details for a specific uptime monitor.

  4. 04

    List monitors

    Provides a list of all configured monitors, including HTTP, DNS, and latency probes.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Better Stack.

  1. 05

    Acknowledge incident

    Signals that an incident is being handled to stop automated paging and escalations.

  2. 06

    List heartbeats

    Shows all configured cron heartbeats used to track background worker health.

  3. 07

    Resolve incident

    Forces an incident into a resolved state once the issue is fixed.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Better Stack.

  1. 08

    Get heartbeat

    Gets the specific details and status of a single passive heartbeat node.

  2. 09

    List on call

    Retrieves the current on-call routing calendars and team schedules.

  3. 10

    List status pages

    Lists all public status pages configured in your account.

Real work

What teams actually run

01

Rapid Incident Triage

When an alert fires, your agent pulls the technical payload so you can see the error immediately.

02

On-Call Verification

Ask your agent who is on the current rotation to confirm who should be paged.

03

Cron Job Debugging

Use the agent to check if a specific heartbeat node has failed due to a server limit.

04

Post-Mortem Data Gathering

Retrieve specific incident timelines to understand exactly when a service went down.

Automate a task

Put Better Stack to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Better Stack works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Better Stack to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

863ms average. Fast in production.

Better Stack is checked daily against the live service.

Daily averagePeak 1253ms
Oct 3Today
Fastest day
739ms
Slowest day
1253ms
14-day trend
Stable0%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Better Stack, so you can see the experience inside your AI.

It does not authenticate your account with Better Stack. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Better Stack Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_xq7kQqt3rPeZjz6W7YzsnYg5qqlmUHoAnFRvYBQj/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Better Stack capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "better-stack-1-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_xq7kQqt3rPeZjz6W7YzsnYg5qqlmUHoAnFRvYBQj/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Better Stack in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Better Stack owners hand off.

This MCP is built for technical teams who need to manage uptime and incidents without leaving their development environment.

  • 01

    DevOps & SREs

    They use the agent to audit on-call matrices and orchestrate initial debugging during outages.

  • 02

    Engineering Managers

    They use the agent to review downtime timelines and quickly resolve dormant alerts.

  • 03

    Backend Developers

    They use the agent to debug failing cron heartbeats while they work on code patches.

FAQ

Questions Better Stack owners ask.

  • 01

    How do I connect my Better Stack account?

    You subscribe to the MCP on Vinkius and enter your Better Stack API Token. Once connected, your AI client can immediately start using the capabilities.

  • 02

    Which AI clients can use this MCP?

    This MCP works with any compatible client, including Claude, Cursor, and Windsurf.

  • 03

    Can my agent actually stop an alert from paging?

    Yes, you can use the acknowledge_incident capability to acknowledge an ongoing incident and halt paging.

  • 04

    Is my API token secure?

    Yes, Vinkius hosts the MCP and manages your credentials securely so you don't have to.

  • 05

    Can I use this to check on-call schedules?

    Yes, the list_on_call capability allows your agent to see active shifts and routing calendars.

  • 06

    Can my AI automatically acknowledge an incident so my phone stops ringing?

    Yes! Running the acknowledge_incident capability pushes a verified API command halting escalation cycles (like SMS and phone calls) natively while you debug.

  • 07

    Is it possible to see the exact HTTP response body or headers that caused a monitor to fail?

    Yes, pulling details via get_incident exposes the raw nested trace containing the root cause payloads and server errors Better Stack historically received when the check failed.

  • 08

    Can the agent create new monitors automatically?

    No. The integration focuses safely on observation, alerting resolution, and tracking currently. Creation endpoints represent mutation vectors decoupled to ensure you preserve billing and account structure intentionally.

Explore

More in Ship It

Suggestions

Connect Better Stack to Claude, Cursor, ChatGPT & more