How to integrate Better stack MCP with Claude Agent SDK

This guide walks you through connecting Better stack to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Better stack agent that can show uptime percentage for api monitor, create escalation policy for on-call team, list heartbeat availability for last week through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Better stack account through Composio's Better stack MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Better stack logoBetter stack
Api Key

Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights.

117 Tools

Introduction

This guide walks you through connecting Better stack to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Better stack agent that can show uptime percentage for api monitor, create escalation policy for on-call team, list heartbeat availability for last week through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Better stack account through Composio's Better stack MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Better stack with

OpenAI Agents SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Better stack
  • Configure an AI agent that can use Better stack as a tool
  • Run a live chat session where you can ask the agent to perform Better stack operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Better stack MCP server, and what's possible with it?

The Better stack MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Better Stack account. It provides structured and secure access to your monitoring, logging, and incident management tools, so your agent can perform actions like retrieving uptime metrics, managing escalation policies, checking heartbeat statuses, and organizing log sources on your behalf.

  • Monitor health checks and availability: Let your agent fetch uptime percentages, availability summaries, and incident details for any monitor in your stack.
  • Automated escalation policy management: Instruct your agent to create or delete escalation policies, keeping your incident response workflows up-to-date without manual effort.
  • Heartbeat tracking and organization: Have your agent fetch specific heartbeat data, check heartbeat availability, or group related heartbeats for easier monitoring.
  • Log source grouping and management: Enable your agent to create or delete source groups, helping you organize log streams and maintain a tidy observability structure.
  • Webhook integration setup: Direct your agent to register outgoing webhooks so your stack can notify external systems of important events automatically.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Better stack account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Better stack functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Better stack
  const session = await composio.create(USER_ID, {
    toolkits: ['better_stack'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Better stack
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Better stack tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Better stack
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Better stack and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['better_stack']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Better stack tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Better stack through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Better stack action and event your agent gets out of the box.

Acknowledge Incident

Tool to acknowledge an ongoing incident.

Create Escalation Policy

Creates a new escalation policy for incident management.

Create Heartbeat

Tool to create a new heartbeat monitor for cron jobs and scheduled tasks.

Create Heartbeat Group

Tool to create a new heartbeat group.

Create Incident

Tool to create a new incident and alert the on-call person.

Create Incident Comment

Tool to create a new comment on an incident.

Create Metadata

Tool to create or update a metadata record for a resource.

Create Monitor

Tool to create a new uptime monitor for a URL or service.

Create Monitor Group

Tool to create a new monitor group.

Create On-Call Schedule

Tool to create a new on-call schedule.

Create Outgoing Webhook Integration

Tool to create a new outgoing webhook integration.

Create Escalation Policy Group

Tool to create a new escalation policy group.

Create Source Group

Tool to create a new source group.

Create Status Page Group

Tool to create a new status page group.

Create Status Page Report

Tool to create a new status page report (incident or maintenance).

Create Status Page Resource

Tool to create a new status page resource.

Create Status Page Section

Tool to create a new section on a status page.

Create Status Update

Tool to create a new status update for an existing status report.

Create Severity Level

Tool to create a new severity level (urgency) for incident management.

Create Urgency Group

Tool to create a new urgency group (severity group) for incident categorization.

Delete Escalation Policy

Tool to delete an escalation policy by ID.

Delete Heartbeat

Tool to permanently delete a heartbeat by ID.

Delete Heartbeat Group

Tool to permanently delete a heartbeat group by ID.

Delete Incident

Tool to permanently delete an existing incident by ID.

Delete Incident Comment

Tool to delete an existing comment from an incident.

Delete Monitor

Tool to permanently delete a monitor by ID from Better Stack Uptime.

Delete Monitor Group

Tool to permanently delete a monitor group by ID from Better Stack Uptime.

Delete On-Call Schedule

Tool to permanently delete an on-call schedule by ID.

Delete Outgoing Webhook Integration

Tool to delete an outgoing webhook integration by ID.

Delete Escalation Policy Group

Tool to delete an escalation policy group by ID.

Delete Source Group

Tool to permanently delete a source group by ID from Better Stack Telemetry (Logs).

Delete Status Page Group

Tool to delete a status page group by ID.

Delete Status Page Report

Tool to permanently delete a status page report by ID from Better Stack Uptime.

Delete Status Page Resource

Tool to delete an existing resource from a status page.

Delete Status Page Section

Tool to permanently delete a status page section by ID.

Delete Status Update

Tool to delete an existing status update from a status report.

Delete Severity

Tool to delete a severity (urgency) by ID.

Delete Urgency Group

Tool to permanently delete an urgency group (severity group) by ID.

Escalate Incident

Tool to escalate an ongoing incident to a user, team, schedule, policy, or organization.

Get Escalation Policy

Tool to get a single escalation policy by its ID.

Get Heartbeat

Tool to get a single heartbeat by ID.

Get Heartbeat Availability

Tool to retrieve availability summary for a specific heartbeat.

Get Heartbeat Group

Tool to get a single heartbeat group by ID.

Get Incident Comment

Tool to get a single comment from an incident.

Get Monitor

Tool to get a single monitor.

Get Monitor Availability

Tool to return an availability summary for a specific monitor.

Get Monitor Group

Tool to get a single monitor group by ID.

Get Monitor Group's Monitors

Tool to get all monitors belonging to a monitor group.

Get Monitor Response Times

Retrieves response time performance metrics for a specific uptime monitor.

Get On-Call Schedule

Tool to get a single on-call schedule by ID.

Get Outgoing Webhook Integration

Tool to get a single outgoing webhook integration by ID.

Get Escalation Policy Group

Tool to get a single escalation policy group.

Get Status Page

Tool to get a single status page by ID.

Get Status Page Group

Tool to get a single status page group by ID.

Get Status Page Report

Tool to get a single status page report by ID.

Get Status Page Resource

Tool to get a single status page resource by ID.

Get Status Page Section

Tool to get a single status page section.

Get Status Update

Tool to get a single status update by its ID.

Get Uptime API Token

Tool to retrieve the configured Uptime API token.

Get Severity Level

Tool to get a single severity level (urgency) by ID.

Get Urgency Group

Tool to get a single urgency group (severity group) by ID.

List AWS CloudWatch Integrations

Tool to list all AWS CloudWatch integrations.

List Azure Integrations

Tool to list all Azure integrations.

List Catalog Relations

Tool to list all catalog relations.

List Datadog Integrations

Tool to list all Datadog integrations.

List Elastic Integrations

Tool to list Elastic integrations.

List Email Integrations

Tool to list email integrations.

List Google Monitoring Integrations

Tool to list all Google Monitoring integrations.

List Grafana Integrations

Tool to list all Grafana integrations.

List Heartbeat Groups

Tool to list all heartbeat groups.

List Heartbeats

Tool to list all heartbeats.

List Incidents Comments

Tool to list all comments on an incident.

List Incidents Timeline

Tool to retrieve all timeline events for an incident.

List Incidents Uptime

Tool to list all incidents with optional filtering by monitor, heartbeat, date range, or resolution status.

List Jira Integrations

Tool to list all Jira integrations.

List Metadata

Tool to list all existing metadata.

List Monitor Groups

Tool to list all monitor groups.

List Monitors

Tool to list all monitors.

List New Relic Integrations

Tool to list New Relic integrations.

List On-Call Schedule Events

Tool to list all events for a specific on-call schedule.

List On-Call Schedules

Tool to list all on-call schedules.

List Outgoing Webhook Integrations

Tool to list all outgoing webhook integrations.

List PagerDuty Webhooks

Tool to list PagerDuty integrations.

List Escalation Policies

Tool to list all escalation policies.

List Escalation Policy Groups

Tool to list all escalation policy groups.

List Prometheus Integrations

Tool to list all Prometheus integrations.

List Single Incident

Tool to retrieve detailed information about a single incident by its ID.

List Slack Integrations

Tool to list all Slack integrations.

List Splunk On-Call Integrations

Tool to list all Splunk On-Call integrations.

List Status Page Groups

Tool to list all status page groups.

List Status Pages In Status Page Group

Tool to list status pages within a specific status page group.

List Status Page Reports

Tool to list all reports on a status page.

List Status Page Report Status Updates

Tool to list all status updates for a status page report.

List Status Pages

Tool to list all your status pages.

List Status Page Sections

Tool to list all sections of a specific status page.

List Status Page Resources

Tool to list all resources on a status page.

List Severity Levels

Tool to list all severity levels (urgencies).

List Urgency Groups

Tool to list all urgency groups (severity groups).

Resolve Incident

Tool to resolve an ongoing incident.

Update Escalation Policy

Tool to update an existing escalation policy.

Update Heartbeat

Tool to update an existing heartbeat configuration.

Update Heartbeat Group

Updates an existing heartbeat group's properties.

Update Incident Comment

Tool to update an existing comment on an incident.

Update Monitor

Tool to update an existing uptime monitor configuration.

Update Monitor Group

Updates an existing monitor group's properties.

Update On-Call Schedule

Tool to update an on-call schedule's name.

Update Outgoing Webhook Integration

Tool to update an existing outgoing webhook integration.

Update Escalation Policy Group

Updates an existing escalation policy group's properties.

Update Source Group

Update an existing source group in Better Stack Logs/Telemetry.

Update Status Page Group

Tool to update an existing status page group.

Update Status Page Report

Tool to update an existing status page report.

Update Status Page Resource

Tool to update an existing status page resource.

Update Status Pages

Tool to update an existing status page configuration.

Update Status Page Section

Tool to update an existing status page section.

Update Status Update

Tool to update an existing status update for a status report.

Update Severity Level

Tool to update an existing severity level (urgency) configuration.

Update Urgency Group

Tool to update an existing urgency group (severity group).

FRAMEWORKS

How to build Better stack MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Better stack MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Better stack MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Better stack MCP with Claude Cowork

Codex logo

Codex

Use Better stack MCP with Codex

OpenClaw logo

OpenClaw

Use Better stack MCP with OpenClaw

Hermes logo

Hermes

Use Better stack MCP with Hermes

CLI logo

CLI

Use Better stack MCP with CLI

Google ADK logo

Google ADK

Use Better stack MCP with Google ADK

LangChain logo

LangChain

Use Better stack MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Better stack MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Better stack MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Better stack MCP with LlamaIndex

CrewAI logo

CrewAI

Use Better stack MCP with CrewAI

FAQ

Frequently asked questions

With a standalone Better stack MCP server, the agents and LLMs can only access a fixed set of Better stack tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Better stack and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Better stack tools.

Yes, absolutely. You can configure which Better stack scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Better stack data and credentials are handled as safely as possible.

Start with Better stack.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Better stack tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies