# How to integrate Laposta MCP with Mastra AI

```json
{
  "title": "How to integrate Laposta MCP with Mastra AI",
  "toolkit": "Laposta",
  "toolkit_slug": "laposta",
  "framework": "Mastra AI",
  "framework_slug": "mastra-ai",
  "url": "https://composio.dev/toolkits/laposta/framework/mastra-ai",
  "markdown_url": "https://composio.dev/toolkits/laposta/framework/mastra-ai.md",
  "updated_at": "2026-10-12T13:48:33.713Z"
}
```

## Introduction

This guide walks you through connecting Laposta to Mastra AI using the Composio tool router. By the end, you'll have a working Laposta agent that can add subscriber to laposta list by email, send campaign to "monthly updates" group, get open rates for last laposta campaign through natural language commands.
This guide will help you understand how to give your Mastra AI agent real control over a Laposta account through Composio's Laposta MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Laposta with

- [Claude Code](https://composio.dev/toolkits/laposta/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/laposta/framework/claude-cowork)
- [OpenAI Agents SDK](https://composio.dev/toolkits/laposta/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/laposta/framework/claude-agents-sdk)
- [Codex](https://composio.dev/toolkits/laposta/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/laposta/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/laposta/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/laposta/framework/atomic-agent)
- [Google ADK](https://composio.dev/toolkits/laposta/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/laposta/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/laposta/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/laposta/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/laposta/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/laposta/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/laposta/framework/autogen)

## 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 Laposta tools
- Connect Mastra's MCP client to the Composio generated MCP URL
- Fetch Laposta 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 Laposta 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 Laposta MCP server, and what's possible with it?

The Laposta MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Laposta account. It provides structured and secure access to your mailing lists, subscribers, campaigns, custom fields, and webhooks, so your agent can manage lists, update subscribers, review campaigns, configure fields, and maintain webhooks on your behalf.
- Mailing list management: Have your agent create mailing lists, review or update their details, list all available lists, and delete lists you no longer need.
- Subscriber management: Let the agent add subscribers to a list, find and review members, update their details or status, and remove them when needed.
- Custom subscriber fields: Direct your agent to create, review, and update custom fields that store the subscriber information your campaigns need.
- Campaign overview: Instruct your agent to retrieve your Laposta email campaigns so you can quickly review what is available in your account.
- Webhook configuration: Have your agent create webhooks for mailing list events, inspect existing webhook details, and update their destination, event type, or blocked status.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `LAPOSTA_CAMPAIGN_GET_ALL` | Get All Campaigns | Retrieve all email campaigns from your Laposta account. Use this tool to list all campaigns with their configuration, delivery status, and analytics settings. Returns campaign details including sender information, subject lines, recipient lists, delivery timestamps, and tracking settings. No parameters required - retrieves all campaigns associated with your account. |
| `LAPOSTA_FIELD_CREATE` | Create Custom Field | Tool to create a custom field for a mailing list to define subscriber attributes. Use when you need to add custom fields like text, numeric, date, or select fields to a list. For select fields (select_single or select_multiple), you must provide the options parameter. |
| `LAPOSTA_FIELD_DELETE` | Delete Field | Tool to permanently remove a custom field from a mailing list. Use when you need to delete a field that is no longer needed. |
| `LAPOSTA_FIELD_GET` | Get Field Details | Tool to retrieve specific field details by field_id. Use when you need to fetch complete information about a custom field including its configuration, data type, and available options. |
| `LAPOSTA_FIELD_GET_ALL` | Get All Fields | Tool to retrieve all fields for a specific list in Laposta. Use when you need to see all field definitions, metadata, and settings for a list. |
| `LAPOSTA_FIELD_UPDATE` | Update Field | Tool to modify field configuration in a Laposta list. Use when you need to update field properties such as name, datatype, required status, or display settings. WARNING: Modifying datatype removes all data from that field. |
| `LAPOSTA_GET_SEGMENT` | Get Segment Details | Tool to retrieve specific segment details by segment_id. Use when you need to fetch complete information about a segment including its name, definition criteria, and timestamps. |
| `LAPOSTA_LIST_CLEAR_MEMBERS` | Clear All Members From List | Tool to clear all active members from a list. Use when you need to remove all active member relationships while preserving the list itself. The operation is permanent and cannot be undone. |
| `LAPOSTA_LIST_CREATE` | Create Mailing List | Tool to create a new mailing list in Laposta to manage email subscribers. Use when you need to create a new list with zero members. |
| `LAPOSTA_LIST_DELETE` | Delete List | Permanently deletes a mailing list from Laposta. This action is irreversible - the list and all its configuration (including notification settings and metadata) will be permanently removed. Members are not deleted, only the list itself. Use this when a mailing list is no longer needed. Returns the deleted list object with state set to 'deleted'. |
| `LAPOSTA_LIST_GET` | Get List Details | Tool to retrieve specific list details by list_id. Use when you need to fetch complete information about a mailing list including its metadata, state, notification settings, and member statistics. |
| `LAPOSTA_LIST_GET_ALL` | Get All Lists | Tool to retrieve all mailing lists from your Laposta account. Use when you need to view all lists including both active and deleted ones. |
| `LAPOSTA_LIST_UPDATE` | Update Mailing List | Tool to modify list properties such as name, remarks, or notification emails. Use when you need to update an existing mailing list's configuration. |
| `LAPOSTA_MEMBER_CREATE` | Create Member | Tool to add a new subscriber relationship to a list with custom fields and tracking info. Use when you need to create a new member in a list or update an existing member if upsert is enabled. |
| `LAPOSTA_MEMBER_DELETE` | Delete Member | Tool to permanently remove a member from a list. Use when you need to delete a member by their ID or email address. |
| `LAPOSTA_MEMBER_GET` | Get Member | Tool to retrieve specific member details by member_id or email. Use when you need to get comprehensive information about a member from a list, including their status, registration details, and custom field values. |
| `LAPOSTA_MEMBER_GET_ALL` | Get All Members | Tool to retrieve all members from a specified Laposta mailing list. Use when you need to list or view all contacts in a list. Optionally filter by member state (active, unsubscribed, or cleaned). |
| `LAPOSTA_MEMBER_UPDATE` | Update Member | Tool to modify member data, status, or custom fields in a Laposta list. Use when updating existing member information or managing subscription state. Supports partial updates (only modified fields need to be included). |
| `LAPOSTA_REPORT_GET_ALL` | Get All Campaign Reports | Tool to retrieve performance metrics for all campaigns. Use when you need campaign statistics including opens, clicks, bounces, complaints, and unsubscribes. |
| `LAPOSTA_SEGMENT_GET_ALL` | Get All Segments | Tool to retrieve all segments from a mailing list. Use when you need to list or browse segments within a specific list. |
| `LAPOSTA_WEBHOOK_CREATE` | Create Webhook | Tool to register a new webhook for list events in Laposta. Use when you need to receive real-time notifications for subscriber events like subscriptions, modifications, or deactivations. |
| `LAPOSTA_WEBHOOK_DELETE` | Delete Webhook | Tool to permanently remove a webhook. Use when you need to delete a webhook from a list. Pending webhook requests are completed before deletion. |
| `LAPOSTA_WEBHOOK_GET` | Get Webhook Details | Tool to retrieve specific webhook details by webhook_id. Use when you need to inspect webhook configuration including event type, URL, and status. |
| `LAPOSTA_WEBHOOK_GET_ALL` | Get All Webhooks | Tool to retrieve all webhooks for a specific list. Use when you need to view all webhooks configured for a particular list. |
| `LAPOSTA_WEBHOOK_UPDATE` | Update Webhook | Tool to modify webhook configuration including URL, event type, or blocked status. Use when you need to update an existing webhook's settings. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Laposta MCP server is an implementation of the Model Context Protocol that connects your AI agent to Laposta. It provides structured and secure access so your agent can perform Laposta operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. 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

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.
- This key lets your Mastra agent talk to Composio and reach Laposta through MCP.

### 2. Install dependencies

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
```bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv
```

### 3. Set up environment variables

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
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import libraries and validate environment

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
```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,
});
```

### 5. Create a Tool Router session for Laposta

What's happening:
- create spins up a short-lived MCP HTTP endpoint for this user
- The toolkits array contains "laposta" for Laposta access
- session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
```typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["laposta"],
    },
  );

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

### 6. Configure Mastra MCP client and fetch tools

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 Laposta toolkit
```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);
```

### 7. Create the Mastra agent

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
```typescript
const agent = new Agent({
    name: "laposta-mastra-agent",
    instructions: "You are an AI agent with Laposta tools via Composio.",
    model: "openai/gpt-5",
  });
```

### 8. Set up interactive chat interface

What's happening:
- messages keeps the full conversation history in Mastra's expected format
- agent.generate runs the agent with conversation history and Laposta 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
```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: {
        laposta: 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);
});
```

## Complete Code

```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: ["laposta"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "laposta-mastra-agent",
    instructions: "You are an AI agent with Laposta 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: { laposta: 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 Laposta 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 Laposta MCP Agent with another framework

- [Claude Code](https://composio.dev/toolkits/laposta/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/laposta/framework/claude-cowork)
- [OpenAI Agents SDK](https://composio.dev/toolkits/laposta/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/laposta/framework/claude-agents-sdk)
- [Codex](https://composio.dev/toolkits/laposta/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/laposta/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/laposta/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/laposta/framework/atomic-agent)
- [Google ADK](https://composio.dev/toolkits/laposta/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/laposta/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/laposta/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/laposta/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/laposta/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/laposta/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/laposta/framework/autogen)

## Related Toolkits

- [Reddit](https://composio.dev/toolkits/reddit) - Reddit is a social news platform with thriving user-driven communities (subreddits). It's the go-to place for discussion, content sharing, and viral marketing.
- [Facebook](https://composio.dev/toolkits/facebook) - Facebook is a social media and advertising platform for businesses and creators. It helps you connect, share, and manage content across your public Facebook Pages.
- [Linkedin](https://composio.dev/toolkits/linkedin) - LinkedIn is a professional networking platform for connecting, sharing content, and engaging with business opportunities. It's the go-to place for building your professional brand and unlocking new career connections.
- [Active campaign](https://composio.dev/toolkits/active_campaign) - ActiveCampaign is a marketing automation and CRM platform for managing email campaigns, sales pipelines, and customer segmentation. It helps businesses engage customers and drive growth through smart automation and targeted outreach.
- [ActiveTrail](https://composio.dev/toolkits/active_trail) - ActiveTrail is a user-friendly email marketing and automation platform. It helps you reach subscribers and automate campaigns with ease.
- [Adobe Marketing Agent MCP](https://composio.dev/toolkits/adobe_marketing_agent_mcp) - Adobe Marketing Agent MCP is Adobe's hosted MCP service that exposes marketing context, preferences, and agent capabilities. Use it to provide agents with campaign, audience, and analytics context via a managed integration.
- [Ahrefs](https://composio.dev/toolkits/ahrefs) - Ahrefs is an SEO and marketing platform for site audits, keyword research, and competitor insights. It helps you improve search rankings and drive organic traffic.
- [AimTell](https://composio.dev/toolkits/aimtell) - AimTell is a web push notification platform for managing websites, subscribers, campaigns, segments, and delivery analytics. Use it to send targeted browser notifications and measure engagement across your web push campaigns.
- [Amcards](https://composio.dev/toolkits/amcards) - AMCards lets you create and mail personalized greeting cards online. Build stronger customer relationships with easy, automated card campaigns.
- [AWeber](https://composio.dev/toolkits/aweber) - AWeber is an email marketing platform for creating campaigns, lists, and landing pages. It helps businesses automate email outreach and measure subscriber engagement.
- [Beamer](https://composio.dev/toolkits/beamer) - Beamer is a news and changelog platform for in-app announcements and feature updates. It helps companies boost user engagement by sharing news where users are most active.
- [Beehiiv](https://composio.dev/toolkits/beehiiv) - Beehiiv is a newsletter platform for creating and managing publications and subscribers. It helps grow audience engagement and monetize your mailing list.
- [Benchmark email](https://composio.dev/toolkits/benchmark_email) - Benchmark Email is a platform for creating, sending, and tracking email campaigns. It's built to help you engage audiences and analyze results—all in one place.
- [Bigmailer](https://composio.dev/toolkits/bigmailer) - BigMailer is an email marketing platform for managing multiple brands with white-labeling and automation. It helps teams streamline campaigns and simplify integration with Amazon SES.
- [Bitly](https://composio.dev/toolkits/bitly) - Bitly is a link management platform for shortening, customizing, sharing, and tracking links and QR codes. It helps teams create branded links and measure engagement across campaigns.
- [BlueFox Email](https://composio.dev/toolkits/bluefox_email) - BlueFox Email is an email API for managing contacts, subscriber lists, and sending transactional and triggered messages. Use it to reliably send transactional and triggered emails and manage subscribers at scale.
- [Brandfetch](https://composio.dev/toolkits/brandfetch) - Brandfetch is an API that delivers company logos, colors, and visual branding assets. It helps marketers and developers keep brand visuals consistent everywhere.
- [Braze](https://composio.dev/toolkits/braze) - Braze is a customer engagement platform for managing user data, messaging, campaigns, and analytics. Use it to deliver targeted, multi-channel messaging and analyze campaign performance.
- [Brevo](https://composio.dev/toolkits/brevo) - Brevo is an all-in-one email and SMS marketing platform for transactional messaging, automation, and CRM. It helps businesses engage customers and streamline communications through powerful campaign tools.
- [Buffer](https://composio.dev/toolkits/buffer) - Buffer is a social media management platform for planning, creating, scheduling, and publishing posts across connected channels. It helps teams keep content organized and publish consistently without jumping between social apps.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Laposta MCP?

With a standalone Laposta MCP server, the agents and LLMs can only access a fixed set of Laposta tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Laposta 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 Laposta tools.

### Can I manage the permissions and scopes for Laposta while using Tool Router?

Yes, absolutely. You can configure which Laposta 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 Laposta data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
