Skip to content
Vinkius

Better Stack Connector for AI agents.

10 live capabilities

Manage uptime incidents and on-call rotations from your chat interface.

Live agent request Better Stack / Connector

Waiting for input…

AI Agent

Why people use Better Stack

Better Stack for Eliminating Dashboard Fatigue

This Connector puts that data in one place. Your agent can pull the incident payload and tell you who's on call in one go. You get a clear picture of the problem without the tab-hopping.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get an AI teammate that handles the heavy lifting of monitoring and incident triage.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Triage a 3 AM production page

    An SRE gets paged and asks the agent to list_incidents and list_on_call to see what's wrong and who's on duty.

  2. Real-world use case 02

    Audit cron job health

    A developer uses list_heartbeats to check if all background workers are reporting correctly during a migration.

  3. Real-world use case 03

    Review public status

    A product manager asks the agent to read the status pages to see if the current outage is visible to customers.

Complete set · 10capabilities

The complete Better Stack capability set.

These are the exact actions your AI can choose when you ask it to work with Better Stack.

Capability set01 / 03

01—04

4 capabilities in this set.

Part of 10 available through Better Stack.

  1. 01 Capability

    List incidents

    List all explicit incidents on Better Stack. This helps you see what is currently firing or has resolved recently.

  2. 02 Capability

    Get incident

    Retrieve the native timeline payload of an explicit incident. This provides the raw data needed for deep debugging.

  3. 03 Capability

    List monitors

    List every uptime monitor you have active on Better Stack. This gives you a bird's eye view of your entire monitoring fleet.

  4. 04 Capability

    Get monitor

    Get the full configuration and status for a specific monitor. Use this to see exact latency constraints and ping targets.

Capability set02 / 03

05—07

3 capabilities in this set.

Part of 10 available through Better Stack.

  1. 05 Capability

    Acknowledge incident

    Acknowledge an ongoing explicit incident. This action halts the paging sequence so your team knows you're on it.

  2. 06 Capability

    Resolve incident

    Force resolve a specific incident. Use this to clear the dashboard once you've confirmed the fix is live.

  3. 07 Capability

    List heartbeats

    List all configured cron heartbeats securely. This helps you track the health of your background workers.

Capability set03 / 03

08—10

3 capabilities in this set.

Part of 10 available through Better Stack.

  1. 08 Capability

    Get heartbeat

    Get explicit details of a passive heartbeat node. Use this to check the last successful run of a specific task.

  2. 09 Capability

    List status pages

    List all explicit Status Pages. This lets you see what your customers see on your public dashboards.

  3. 10 Capability

    List on call

    List exact On-Call routing calendars. This tells you exactly who is responsible for the current shift.

Set up in minutes

One URL. Then ask Better Stack to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Better Stack from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_xq7kQqt3rPeZjz6W7YzsnYg5qqlmUHoAnFRvYBQj/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it Better Stack, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable Better Stack for the conversation.

Where the request belongs

Work Better Stack can move forward.

Built around the request

This is for the SRE or DevOps engineer who's tired of clicking through multiple dashboards at 2 AM and wants a direct line to their infrastructure data.

01

Site Reliability Engineer

Uses the Connector to triage high-priority alerts and check on-call rotations without leaving the chat.

02

DevOps Engineer

Audits heartbeat statuses for background workers and reviews uptime monitor configurations.

03

Engineering Manager

Reviews downtime timelines and checks public status pages to give updates to stakeholders.

Build the capability set

Add more capabilities.

Each Connector adds new actions and data without changing how you work.

Browse Connectors
Better Stack logo
01 10 capabilities

Better Stack

Monitor uptime and incidents via Better Stack. list monitors, heartbeats, and on-call schedules directly from any AI agent.

View Connector
Incident.io logo
02 10 capabilities

Incident.io

Manage incidents, roles, and on-call schedules via Incident.io API.

View Connector
PagerDuty logo
03 11 capabilities

PagerDuty

Manage incidents, services, on-call schedules, and escalation policies via PagerDuty. trigger, acknowledge, and resolve alerts from any AI agent.

View Connector
ncScale logo
04 10 capabilities

ncScale

Monitor and observe your no-code stack via ncScale. track logs, alerts, and tickets directly from your AI agent.

View Connector
Opsgenie logo
05 11 capabilities

Opsgenie

Automate incident management via Opsgenie. manage alerts, track on-calls, and coordinate incidents directly from any AI agent.

View Connector
PagerDuty Incident Trigger logo
06 1 capability

PagerDuty Incident Trigger

This MCP does exactly one thing: it triggers incidents in PagerDuty. That's its only function, and nothing else. Incredible for giving your AI agents the power to wake up engineers.

View Connector

Bring your own AI

Change the model, client or framework. Keep Better Stack connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about Better Stack.

The practical details behind the request, access and result.

Can the Better Stack MCP help me during a production outage?

Yes, it allows your AI agent to pull incident details, check on-call schedules, and acknowledge alerts directly from your chat interface, which helps you triage faster.

How does the Better Stack MCP handle on-call schedules?

It exposes your on-call routing calendars so you can ask your agent exactly who is on duty for any given shift or team rotation.

Can I use the Better Stack MCP to see my heartbeat status?

Yes, your agent can check the status of your cron heartbeats and background workers to ensure your passive tracking endpoints are running.

Does the Better Stack MCP support public status pages?

It can read your public-facing status dashboards, allowing you to quickly check what information is being shared with your customers.

Can my AI agent acknowledge alerts with the Better Stack MCP?

Yes, your agent can acknowledge ongoing incidents to halt the paging sequence while you work on a resolution.

Is the Better Stack MCP good for checking DNS probes?

It can retrieve the definitions and current status of all your active monitors, including DNS probes and HTTP endpoint pings.

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.

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.

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.

One connection away

Give your agent a direct line to Better Stack.

Connect Better Stack once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available