# How to integrate Eventee MCP with LangChain

```json
{
  "title": "How to integrate Eventee MCP with LangChain",
  "toolkit": "Eventee",
  "toolkit_slug": "eventee",
  "framework": "LangChain",
  "framework_slug": "langchain",
  "url": "https://composio.dev/toolkits/eventee/framework/langchain",
  "markdown_url": "https://composio.dev/toolkits/eventee/framework/langchain.md",
  "updated_at": "2026-05-12T10:10:47.460Z"
}
```

## Introduction

This guide walks you through connecting Eventee to LangChain using the Composio tool router. By the end, you'll have a working Eventee agent that can list all upcoming events this month, add keynote speaker to annual conference, remove cancelled speaker from event lineup through natural language commands.
This guide will help you understand how to give your LangChain agent real control over a Eventee account through Composio's Eventee MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Eventee with

- [OpenAI Agents SDK](https://composio.dev/toolkits/eventee/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/eventee/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/eventee/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/eventee/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/eventee/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/eventee/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/eventee/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/eventee/framework/cli)
- [Google ADK](https://composio.dev/toolkits/eventee/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/eventee/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/eventee/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/eventee/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/eventee/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Connect your Eventee project to Composio
- Create a Tool Router MCP session for Eventee
- Initialize an MCP client and retrieve Eventee tools
- Build a LangChain agent that can interact with Eventee
- Set up an interactive chat interface for testing

## What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.
Key features include:
- Agent Framework: Build agents that can use tools and make decisions
- MCP Integration: Connect to external services through Model Context Protocol adapters
- Memory Management: Maintain conversation history across interactions
- Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

## What is the Eventee MCP server, and what's possible with it?

The Eventee MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Eventee account. It provides structured and secure access to your event management workspace, so your agent can list events, add new speakers, and manage speaker lineups with ease.
- Retrieve all scheduled events: Instantly get a comprehensive list of your upcoming and past events, making it easy for your agent to reference, review, or summarize them for you.
- Add new speakers to events: Have your agent seamlessly add speakers to any specific Eventee event, streamlining the process of building out your event agenda.
- Delete speakers from events: Let your agent remove speakers by their ID, ensuring your speaker lineup stays accurate and up to date without manual intervention.
- Automate speaker management workflows: Enable your agent to help with onboarding, updating, or cleaning up speaker information across multiple events, saving you time and reducing errors.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `EVENTEE_ADD_SPEAKER` | Add speaker | Tool to add a new speaker to a specific Eventee event. Use after creating an event and obtaining its ID. |
| `EVENTEE_CREATE_HALL` | Create Hall | Tool to create a new hall/stage for an event where sessions can be scheduled. Use when setting up venues or stages for your event to organize presentations and activities. |
| `EVENTEE_CREATE_LABEL` | Create Label | Tool to create a new label/track for categorizing event sessions by topic or theme. Use this when organizing sessions into different tracks like technology, design, or marketing themes. |
| `EVENTEE_CREATE_PARTNER` | Create Partner | Tool to add a new partner/sponsor to the event. Use when you need to register sponsors or exhibitors for your event. |
| `EVENTEE_CREATE_PAUSE` | Create Pause | Tool to create a new break/pause in the event schedule (e.g., coffee break, lunch). Use when scheduling breaks between sessions. Start and end times must be within the event date range. |
| `EVENTEE_DELETE_ATTENDEE` | Delete Attendee | Tool to remove an attendee from the event by their email address. Use when you need to delete an attendee registration. |
| `EVENTEE_DELETE_HALL` | Delete Hall | Tool to delete a hall/stage from an event by its ID. Use when you need to remove a hall/stage after confirming its ID. |
| `EVENTEE_DELETE_PARTNER` | Delete Partner | Tool to delete a partner/sponsor by their ID. Use when you need to remove a partner after confirming their ID. |
| `EVENTEE_DELETE_REGISTRATION` | Delete Registration | Tool to remove a registration from the event by email address. Use when you need to delete or cancel a specific registration. |
| `EVENTEE_DELETE_SPEAKER` | Delete Speaker | Tool to delete a speaker by their ID. Use when you need to remove a speaker after confirming their ID. |
| `EVENTEE_DELETE_TEST_CONTENT` | Delete Test Content | Tool to clear all test content from the event. Use this during development or testing to remove test data. This operation is destructive and cannot be undone. |
| `EVENTEE_GET_GROUPS` | Get Groups | Tool to retrieve all event groups from Eventee (e.g., VIP attendees, speaker groups). Use this to get the list of attendee groups configured for your event. |
| `EVENTEE_GET_PARTICIPANTS` | Get Participants | Tool to retrieve all participants/attendees for an Eventee event. The event is determined by your API token. Use this to get a list of all attendees who have registered or been invited to your event. |
| `EVENTEE_GET_PARTNERS` | Get Partners | Tool to retrieve all partners/sponsors for an Eventee event. Use this to get information about exhibitors and sponsors associated with your event. |
| `EVENTEE_GET_REGISTRATIONS` | Get Registrations | Tool to retrieve all registrations for an Eventee event. The event is determined by your API token. Use this to get a list of all registered attendees for your event. |
| `EVENTEE_GET_REVIEWS` | Get Reviews | Tool to retrieve all reviews for your Eventee event. Reviews can include ratings and feedback from attendees about speakers, lectures, or the event itself. Use this to analyze attendee satisfaction and gather feedback. |
| `EVENTEE_INVITE_ATTENDEE` | Invite Attendee | Tool to invite attendees to your Eventee event by sending invitation emails to specified users. Use when you need to send event invitations to new attendees. |
| `EVENTEE_INVITE_REGISTRATION` | Invite Registration | Tool to invite registrants to your Eventee event by email. Use when you need to send event invitations to one or more participants. |
| `EVENTEE_LIST_EVENTS` | List Events | Retrieves the content structure of your Eventee event including halls, speakers, lectures, workshops, and other event components. The event is determined by your API token. Use this to get an overview of all content within your event. |
| `EVENTEE_UPDATE_HALL` | Update Hall | Tool to update an existing hall/stage details in an Eventee event. Use when you need to modify hall properties like name, order, or streaming URL. |
| `EVENTEE_UPDATE_LECTURE` | Update Lecture | Tool to update an existing lecture/session details in Eventee. Use when modifying lecture information such as name, time, or description. Note that all required fields (name, start, end) must be provided even for partial updates. |
| `EVENTEE_UPDATE_PARTNER` | Update Partner | Tool to update an existing partner/sponsor details. Use when you need to modify partner information such as company name, contact details, or status. |

## Supported Triggers

None listed.

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

The Eventee MCP server is an implementation of the Model Context Protocol that connects your AI agent to Eventee. It provides structured and secure access so your agent can perform Eventee 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

No description provided.

### 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'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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

No description provided.
```python
pip install composio-langchain langchain-mcp-adapters langchain python-dotenv
```

```typescript
npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters 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's API
- COMPOSIO_USER_ID identifies the user for session management
- OPENAI_API_KEY enables access to OpenAI's language models
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

No description provided.
```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
```

```typescript
import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
```

### 5. Initialize Composio client

What's happening:
- We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
- Creating a Composio instance that will manage our connection to Eventee tools
- Validating that COMPOSIO_USER_ID is also set before proceeding
```python
async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
```

```typescript
const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
```

### 6. Create a Tool Router session

What's happening:
- We're creating a Tool Router session that gives your agent access to Eventee tools
- The create method takes the user ID and specifies which toolkits should be available
- The returned session.mcp.url is the MCP server URL that your agent will use
- This approach allows the agent to dynamically load and use Eventee tools as needed
```python
# Create Tool Router session for Eventee
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['eventee']
)

url = session.mcp.url
```

```typescript
const session = await composio.create(
    userId as string,
    {
        toolkits: ['eventee']
    }
);

const url = session.mcp.url;
```

### 7. Configure the agent with the MCP URL

No description provided.
```python
client = MultiServerMCPClient({
    "eventee-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
```

```typescript
const client = new MultiServerMCPClient({
    "eventee-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
```

### 8. Set up interactive chat interface

No description provided.
```python
conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Eventee related question or task to the agent.\n")

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

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

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
```

```typescript
let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Eventee related question or task to the agent.\n");

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

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;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
```

### 9. Run the application

No description provided.
```python
if __name__ == "__main__":
    asyncio.run(main())
```

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

## Complete Code

```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['eventee']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "eventee-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Eventee related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

if __name__ == "__main__":
    asyncio.run(main())
```

```typescript
import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['eventee']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "eventee-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Eventee related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    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;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

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

## Conclusion

You've successfully built a LangChain agent that can interact with Eventee through Composio's Tool Router.
Key features of this implementation:
- Dynamic tool loading through Composio's Tool Router
- Conversation history maintenance for context-aware responses
- Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

## How to build Eventee MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/eventee/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/eventee/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/eventee/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/eventee/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/eventee/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/eventee/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/eventee/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/eventee/framework/cli)
- [Google ADK](https://composio.dev/toolkits/eventee/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/eventee/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/eventee/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/eventee/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/eventee/framework/crew-ai)

## Related Toolkits

- [Google Calendar](https://composio.dev/toolkits/googlecalendar) - Google Calendar is a time management service for scheduling meetings, events, and reminders. It streamlines personal and team organization with integrated notifications and sharing options.
- [Apaleo](https://composio.dev/toolkits/apaleo) - Apaleo is a cloud-based property management platform for hospitality businesses. It centralizes reservations, billing, and daily operations for smoother hotel management.
- [Appointo](https://composio.dev/toolkits/appointo) - Appointo is an appointment booking platform for Shopify stores. It lets businesses add online scheduling to their websites with zero coding.
- [Bart](https://composio.dev/toolkits/bart) - Bart is the Bay Area Rapid Transit system, providing fast public transportation across the San Francisco Bay Area. It helps commuters and travelers get real-time schedule info, plan routes, and stay updated on service changes.
- [Bookingmood](https://composio.dev/toolkits/bookingmood) - Bookingmood is commission-free booking software for rental businesses. It lets you manage reservations and sync bookings directly on your website.
- [Booqable](https://composio.dev/toolkits/booqable) - Booqable is a rental software platform for managing inventory, bookings, and reservations. It helps businesses streamline rentals and keep track of every item with ease.
- [Cal](https://composio.dev/toolkits/cal) - Cal is a meeting scheduling platform that offers shareable booking links and real-time calendar syncing. It streamlines the process of finding mutual availability to make scheduling effortless.
- [Calendarhero](https://composio.dev/toolkits/calendarhero) - Calendarhero is a powerful scheduling platform that streamlines your calendar management across multiple services. It helps you efficiently schedule, reschedule, and organize meetings without the back-and-forth.
- [Calendly](https://composio.dev/toolkits/calendly) - Calendly is an appointment scheduling tool that automates meeting invitations, availability checks, and reminders. It helps individuals and teams avoid endless email back-and-forth when booking meetings.
- [Etermin](https://composio.dev/toolkits/etermin) - eTermin is an online appointment scheduling platform for businesses to manage bookings. It streamlines client appointments, saving time and reducing scheduling conflicts.
- [Evenium](https://composio.dev/toolkits/evenium) - Evenium is an all-in-one platform for managing professional events, from planning to analysis. It helps teams simplify event logistics, boost engagement, and track every detail in one place.
- [Eventzilla](https://composio.dev/toolkits/eventzilla) - Eventzilla is an event management platform for creating, promoting, and running events. It streamlines ticketing, registration, and attendee coordination for organizers.
- [Humanitix](https://composio.dev/toolkits/humanitix) - Humanitix is a not-for-profit ticketing platform that donates 100% of profits to charity. It empowers event organizers to make social impact with every ticket sold.
- [Lodgify](https://composio.dev/toolkits/lodgify) - Lodgify is an all-in-one vacation rental software for property managers and owners. It centralizes bookings, guest messaging, and channel synchronization in one dashboard.
- [Planyo Online Booking](https://composio.dev/toolkits/planyo_online_booking) - Planyo Online Booking is a flexible reservation system for managing bookings by day, hour, or event. It streamlines scheduling for any business needing reservations.
- [Scheduleonce](https://composio.dev/toolkits/scheduleonce) - Scheduleonce is a scheduling platform for capturing, qualifying, and engaging with inbound leads. It streamlines appointment booking and follow-ups for faster lead conversion.
- [Supersaas](https://composio.dev/toolkits/supersaas) - Supersaas is a flexible appointment scheduling platform for businesses and individuals. It streamlines bookings, reminders, and calendar management in one place.
- [Sympla](https://composio.dev/toolkits/sympla) - Sympla is a platform for managing in-person and online events, ticket sales, and registrations. It streamlines event setup, attendee tracking, and digital content delivery.
- [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.
- [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.

## Frequently Asked Questions

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

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

### Can I use Tool Router MCP with LangChain?

Yes, you can. LangChain 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 Eventee tools.

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

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

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