SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Eventee MCP with Claude Agent SDK

Connect Claude Agent SDK to Eventee MCP. List all upcoming events this month, add keynote speaker to annual conference, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Eventee logoEventee
Api Key

Eventee is a user-friendly event management platform for mobile and web. It boosts attendee engagement for in-person, virtual, and hybrid events.

22 Tools

Introduction

This guide walks you through connecting Eventee to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Eventee agent that can invite attendees, add speakers, manage halls and partners, update lectures, and check registrations and session reviews through natural language commands.

This guide will help you understand how to give your Claude Agent SDK 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

Claude CodeClaude CoworkOpenAI Agents SDKCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

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

What is Claude Agent SDK?

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

Key features include:

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

What is the 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.

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

What is Composio SDK?

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

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

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

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

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

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

Getting API Keys for Claude/Anthropic and Composio

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

Install dependencies

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

Install the Composio SDK and the Claude Agents SDK.

What's happening:

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

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

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

Import dependencies

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

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

Create a Composio instance and Tool Router session

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

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

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

Configure Claude Agent with MCP

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

Create client and start chat loop

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

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

  let isProcessing = false;

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

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

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

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

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

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

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

Run the application

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

Complete Code

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

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

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

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

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

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

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

  let isProcessing = false;

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

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

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

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

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

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

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

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

Conclusion

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

Key features:

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

Supported Tools

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

Add speaker

Add a speaker to the Eventee event associated with the API token, with a name and optional profile details.

Create Hall

Tool to create a new hall/stage for an event where sessions can be scheduled.

Create Label

Tool to create a new label/track for categorizing event sessions by topic or theme.

Create Partner

Submit a request to create a partner for the Eventee event associated with the API token, supplying company and optional contact details for the event's partner listings.

Create Pause

Tool to create a new break/pause in the event schedule (e.

Delete Attendee

Removes an attendee from the event by email address.

Delete Hall

Deletes a hall or stage from the event by ID.

Delete Partner

Tool to delete a partner/sponsor by their ID.

Delete Registration

Tool to remove a registration from the event by email address.

Delete Speaker

Delete a speaker by ID from the Eventee event associated with the API token.

Delete Test Content

Tool to clear all test content from the event.

Get Groups

Tool to retrieve all event groups from Eventee (e.

Get Participants

Tool to retrieve all participants/attendees for an Eventee event.

Get Partners

Retrieve partners for the Eventee event associated with the API token.

Get Registrations

Tool to retrieve all registrations for an Eventee event.

Get Reviews

Retrieve session reviews for the Eventee event associated with the API token.

Invite Attendee

Invites attendees to the event using their email addresses.

Invite Registration

Submits registration invitations for one or more email addresses.

List Events

Retrieves the event content structure for the event associated with the API token.

Update Hall

Updates an event hall or stage by ID, including its name, order or existing stream code.

Update Lecture

Updates an existing lecture or session by ID, with name, start and end required.

Update Partner

Tool to update an existing partner/sponsor details.

FRAMEWORKS

How to build Eventee MCP Agent with another framework

Claude Code logo

Claude Code

Use Eventee MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Eventee MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Eventee MCP with OpenAI Agents SDK

Codex logo

Codex

Use Eventee MCP with Codex

OpenClaw logo

OpenClaw

Use Eventee MCP with OpenClaw

Hermes logo

Hermes

Use Eventee MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Eventee MCP with Atomic Agent

Google ADK logo

Google ADK

Use Eventee MCP with Google ADK

LangChain logo

LangChain

Use Eventee MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Eventee MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Eventee MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Eventee MCP with LlamaIndex

CrewAI logo

CrewAI

Use Eventee MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Eventee MCP with Pydantic AI

AutoGen logo

AutoGen

Use Eventee MCP with AutoGen

FAQ

Frequently asked questions

Start with Eventee.It takes 30 seconds.

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

Start building