How to integrate Better stack MCP with CrewAI

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Better stack logo
CrewAI logo
divider

Introduction

This guide walks you through connecting Better stack to CrewAI 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 CrewAI 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

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Better stack connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Better stack
  • Build a conversational loop where your agent can execute Better stack operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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.

Supported Tools & Triggers

Tools
Acknowledge IncidentTool to acknowledge an ongoing incident.
Create Escalation PolicyCreates a new escalation policy for incident management.
Create HeartbeatTool to create a new heartbeat monitor for cron jobs and scheduled tasks.
Create Heartbeat GroupTool to create a new heartbeat group.
Create IncidentTool to create a new incident and alert the on-call person.
Create Incident CommentTool to create a new comment on an incident.
Create MetadataTool to create or update a metadata record for a resource.
Create MonitorTool to create a new uptime monitor for a URL or service.
Create Monitor GroupTool to create a new monitor group.
Create On-Call ScheduleTool to create a new on-call schedule.
Create Outgoing Webhook IntegrationTool to create a new outgoing webhook integration.
Create Escalation Policy GroupTool to create a new escalation policy group.
Create Source GroupTool to create a new source group.
Create Status Page GroupTool to create a new status page group.
Create Status Page ReportTool to create a new status page report (incident or maintenance).
Create Status Page ResourceTool to create a new status page resource.
Create Status Page SectionTool to create a new section on a status page.
Create Status UpdateTool to create a new status update for an existing status report.
Create Severity LevelTool to create a new severity level (urgency) for incident management.
Create Urgency GroupTool to create a new urgency group (severity group) for incident categorization.
Delete Escalation PolicyTool to delete an escalation policy by ID.
Delete HeartbeatTool to permanently delete a heartbeat by ID.
Delete Heartbeat GroupTool to permanently delete a heartbeat group by ID.
Delete IncidentTool to permanently delete an existing incident by ID.
Delete Incident CommentTool to delete an existing comment from an incident.
Delete MonitorTool to permanently delete a monitor by ID from Better Stack Uptime.
Delete Monitor GroupTool to permanently delete a monitor group by ID from Better Stack Uptime.
Delete On-Call ScheduleTool to permanently delete an on-call schedule by ID.
Delete Outgoing Webhook IntegrationTool to delete an outgoing webhook integration by ID.
Delete Escalation Policy GroupTool to delete an escalation policy group by ID.
Delete Source GroupTool to permanently delete a source group by ID from Better Stack Telemetry (Logs).
Delete Status Page GroupTool to delete a status page group by ID.
Delete Status Page ReportTool to permanently delete a status page report by ID from Better Stack Uptime.
Delete Status Page ResourceTool to delete an existing resource from a status page.
Delete Status Page SectionTool to permanently delete a status page section by ID.
Delete Status UpdateTool to delete an existing status update from a status report.
Delete SeverityTool to delete a severity (urgency) by ID.
Delete Urgency GroupTool to permanently delete an urgency group (severity group) by ID.
Escalate IncidentTool to escalate an ongoing incident to a user, team, schedule, policy, or organization.
Get Escalation PolicyTool to get a single escalation policy by its ID.
Get HeartbeatTool to get a single heartbeat by ID.
Get Heartbeat AvailabilityTool to retrieve availability summary for a specific heartbeat.
Get Heartbeat GroupTool to get a single heartbeat group by ID.
Get Incident CommentTool to get a single comment from an incident.
Get MonitorTool to get a single monitor.
Get Monitor AvailabilityTool to return an availability summary for a specific monitor.
Get Monitor GroupTool to get a single monitor group by ID.
Get Monitor Group's MonitorsTool to get all monitors belonging to a monitor group.
Get Monitor Response TimesRetrieves response time performance metrics for a specific uptime monitor.
Get On-Call ScheduleTool to get a single on-call schedule by ID.
Get Outgoing Webhook IntegrationTool to get a single outgoing webhook integration by ID.
Get Escalation Policy GroupTool to get a single escalation policy group.
Get Status PageTool to get a single status page by ID.
Get Status Page GroupTool to get a single status page group by ID.
Get Status Page ReportTool to get a single status page report by ID.
Get Status Page ResourceTool to get a single status page resource by ID.
Get Status Page SectionTool to get a single status page section.
Get Status UpdateTool to get a single status update by its ID.
Get Uptime API TokenTool to retrieve the configured Uptime API token.
Get Severity LevelTool to get a single severity level (urgency) by ID.
Get Urgency GroupTool to get a single urgency group (severity group) by ID.
List AWS CloudWatch IntegrationsTool to list all AWS CloudWatch integrations.
List Azure IntegrationsTool to list all Azure integrations.
List Catalog RelationsTool to list all catalog relations.
List Datadog IntegrationsTool to list all Datadog integrations.
List Elastic IntegrationsTool to list Elastic integrations.
List Email IntegrationsTool to list email integrations.
List Google Monitoring IntegrationsTool to list all Google Monitoring integrations.
List Grafana IntegrationsTool to list all Grafana integrations.
List Heartbeat GroupsTool to list all heartbeat groups.
List HeartbeatsTool to list all heartbeats.
List Incidents CommentsTool to list all comments on an incident.
List Incidents TimelineTool to retrieve all timeline events for an incident.
List Incidents UptimeTool to list all incidents with optional filtering by monitor, heartbeat, date range, or resolution status.
List Jira IntegrationsTool to list all Jira integrations.
List MetadataTool to list all existing metadata.
List Monitor GroupsTool to list all monitor groups.
List MonitorsTool to list all monitors.
List New Relic IntegrationsTool to list New Relic integrations.
List On-Call Schedule EventsTool to list all events for a specific on-call schedule.
List On-Call SchedulesTool to list all on-call schedules.
List Outgoing Webhook IntegrationsTool to list all outgoing webhook integrations.
List PagerDuty WebhooksTool to list PagerDuty integrations.
List Escalation PoliciesTool to list all escalation policies.
List Escalation Policy GroupsTool to list all escalation policy groups.
List Prometheus IntegrationsTool to list all Prometheus integrations.
List Single IncidentTool to retrieve detailed information about a single incident by its ID.
List Slack IntegrationsTool to list all Slack integrations.
List Splunk On-Call IntegrationsTool to list all Splunk On-Call integrations.
List Status Page GroupsTool to list all status page groups.
List Status Pages In Status Page GroupTool to list status pages within a specific status page group.
List Status Page ReportsTool to list all reports on a status page.
List Status Page Report Status UpdatesTool to list all status updates for a status page report.
List Status PagesTool to list all your status pages.
List Status Page SectionsTool to list all sections of a specific status page.
List Status Page ResourcesTool to list all resources on a status page.
List Severity LevelsTool to list all severity levels (urgencies).
List Urgency GroupsTool to list all urgency groups (severity groups).
Resolve IncidentTool to resolve an ongoing incident.
Update Escalation PolicyTool to update an existing escalation policy.
Update HeartbeatTool to update an existing heartbeat configuration.
Update Heartbeat GroupUpdates an existing heartbeat group's properties.
Update Incident CommentTool to update an existing comment on an incident.
Update MonitorTool to update an existing uptime monitor configuration.
Update Monitor GroupUpdates an existing monitor group's properties.
Update On-Call ScheduleTool to update an on-call schedule's name.
Update Outgoing Webhook IntegrationTool to update an existing outgoing webhook integration.
Update Escalation Policy GroupUpdates an existing escalation policy group's properties.
Update Source GroupUpdate an existing source group in Better Stack Logs/Telemetry.
Update Status Page GroupTool to update an existing status page group.
Update Status Page ReportTool to update an existing status page report.
Update Status Page ResourceTool to update an existing status page resource.
Update Status PagesTool to update an existing status page configuration.
Update Status Page SectionTool to update an existing status page section.
Update Status UpdateTool to update an existing status update for a status report.
Update Severity LevelTool to update an existing severity level (urgency) configuration.
Update Urgency GroupTool to update an existing urgency group (severity group).

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

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Better stack connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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.

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Better stack via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Better stack MCP URL

Create a Composio Tool Router session for Better stack

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["better_stack"])

url = session.mcp.url
What's happening:
  • You create a Better stack only session through Composio
  • Composio returns an MCP HTTP URL that exposes Better stack tools

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

Here's the complete code to get you started with Better stack and CrewAI:

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["better_stack"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Better stack through Composio's Tool Router. The agent can perform Better stack operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations

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 Agent SDK logo

Claude Agent SDK

Use Better stack MCP with Claude Agent 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

FAQ

What are the differences in Tool Router MCP and Better stack MCP?

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.

Can I use Tool Router MCP with CrewAI?

Yes, you can. CrewAI 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.

Can I manage the permissions and scopes for Better stack while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗