Better stack with Mastra AI

How to integrate Better stack MCP with Mastra AI

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Better stack with TL;DR What is Mastra AI What is the Better stack MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Better stack MCP Agent with another framework Explore Other Toolkits FAQ

Connect Better stack without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

Introduction

This guide walks you through connecting Better stack to Mastra AI 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 Mastra AI 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 SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Set up your environment so Mastra, OpenAI, and Composio work together
Create a Tool Router session in Composio that exposes Better stack tools
Connect Mastra's MCP client to the Composio generated MCP URL
Fetch Better stack tool definitions and attach them as a toolset
Build a Mastra agent that can reason, call tools, and return structured results
Run an interactive CLI where you can chat with your Better stack agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

MCP Client: Built-in support for Model Context Protocol servers
Toolsets: Organize tools into logical groups
Step Callbacks: Monitor and debug agent execution
OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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:

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

Step-by-step Guide

Prerequisites

Before starting, make sure you have:

Node.js 18 or higher
A Composio account with an active API key
An OpenAI API key
Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key.
You need credits or a connected billing setup to use the models.
Store the key somewhere safe.

Composio API Key

Log in to the Composio dashboard.
Go to Settings and copy your API key.
This key lets your Mastra agent talk to Composio and reach Better stack through MCP.

Install dependencies

bash

npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

@composio/core is the Composio SDK for creating MCP sessions
@mastra/core provides the Agent class
@mastra/mcp is Mastra's MCP client
@ai-sdk/openai is the model wrapper for OpenAI
dotenv loads environment variables from .env

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_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 your requests to Composio
COMPOSIO_USER_ID tells Composio which user this session belongs to
OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});

What's happening:

dotenv/config auto loads your .env so process.env.* is available
openai gives you a Mastra compatible model wrapper
Agent is the Mastra agent that will call tools and produce answers
MCPClient connects Mastra to your Composio MCP server
Composio is used to create a Tool Router session

Create a Tool Router session for Better stack

typescript

async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["better_stack"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Better stack MCP URL:", composioMCPUrl);

What's happening:

create spins up a short-lived MCP HTTP endpoint for this user
The toolkits array contains "better_stack" for Better stack access
session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript

const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);

What's happening:

MCPClient takes an id for this client and a list of MCP servers
The headers property includes the x-api-key for authentication
getTools fetches the tool definitions exposed by the Better stack toolkit

Create the Mastra agent

typescript

const agent = new Agent({
    name: "better_stack-mastra-agent",
    instructions: "You are an AI agent with Better stack tools via Composio.",
    model: "openai/gpt-5",
  });

What's happening:

Agent is the core Mastra agent
name is just an identifier for logging and debugging
instructions guide the agent to use tools instead of only answering in natural language
model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript

let messages: AiMessageType[] = [];

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

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

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        better_stack: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

What's happening:

messages keeps the full conversation history in Mastra's expected format
agent.generate runs the agent with conversation history and Better stack toolsets
maxSteps limits how many tool calls the agent can take in a single run
onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

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

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["better_stack"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      better_stack: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "better_stack-mastra-agent",
    instructions: "You are an AI agent with Better stack tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

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

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { better_stack: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Better stack through Composio's Tool Router. You can extend this further by:

Adding other toolkits like Gmail, Slack, or GitHub
Building a web-based chat interface around this agent
Using multiple MCP endpoints to enable cross-app workflows

How to build Better stack MCP Agent with another framework

OpenAI Agents SDK

Use Better stack MCP with OpenAI Agents SDK

Claude Agent SDK

Use Better stack MCP with Claude Agent SDK

Claude Code

Use Better stack MCP with Claude Code

Claude Cowork

Use Better stack MCP with Claude Cowork

Codex

Use Better stack MCP with Codex

OpenClaw

Use Better stack MCP with OpenClaw

Hermes

Use Better stack MCP with Hermes

CLI

Use Better stack MCP with CLI

Google ADK

Use Better stack MCP with Google ADK

LangChain

Use Better stack MCP with LangChain

Vercel AI SDK

Use Better stack MCP with Vercel AI SDK

LlamaIndex

Use Better stack MCP with LlamaIndex

CrewAI

Use Better stack MCP with CrewAI

Explore Other Toolkits

Supabase

Oauth2Api Key

Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.

Codeinterpreter

No Auth

Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.

GitHub

Oauth2

GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.

TOOLKIT MARKETPLACE

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 Mastra AI?

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

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 free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

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

Abhi AryaCo-founder, Opennote

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 has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

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

Ryan YuFounder, Extra Thursday

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

Tomisin JenrolaFounder & CEO, SwarmZero

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

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

How to integrate Better stack MCP with Mastra AI

Table of Contents

Connect Better stack without Auth hassles

Introduction

Also integrate Better stack with

TL;DR

What is Mastra AI?

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

Supported Tools & Triggers

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import libraries and validate environment

Create a Tool Router session for Better stack

Configure Mastra MCP client and fetch tools

Create the Mastra agent

Set up interactive chat interface

Complete Code

Conclusion

How to build Better stack MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

LlamaIndex

CrewAI

Explore Other Toolkits

Supabase

Codeinterpreter

GitHub

FAQ

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

Can I use Tool Router MCP with Mastra AI?

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

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability