How to integrate Modem MCP with CrewAI

This guide walks you through connecting Modem to CrewAI using the Composio tool router. By the end, you'll have a working Modem agent that can create company records, add your contacts, review company activity, trace histories, and check identities through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Modem account through Composio's Modem MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Modem logoModem
Api Key

Modem is a customer intelligence platform that turns conversations into structured topics, people, and company insights. Use it to analyze feedback patterns and automate customer workflows faster.

30 Tools

Introduction

This guide walks you through connecting Modem to CrewAI using the Composio tool router. By the end, you'll have a working Modem agent that can create company records, add your contacts, review company activity, trace histories, and check identities through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Modem account through Composio's Modem MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Modem with

TL;DR

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

What is CrewAI?

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

Key features include:

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

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

The Modem MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Modem account. It provides structured and secure access to your customer conversation topics, people, companies, channels, and activity insights, so your agent can search topics, analyze engagement, manage customer records, review histories, and organize insights on your behalf.

  • Topic discovery and analysis: Have your agent search customer conversation topics by keywords or meaning, then review summaries, classifications, priorities, participants, message groups, and history.
  • People and company insights: Let the agent find people and companies, inspect their profiles and conversation activity, and see how engagement breaks down across sources.
  • Customer record management: Direct your agent to create or update people and companies, associate people with companies, and connect external records to the right profiles.
  • Channel and activity monitoring: Instruct your agent to review connected conversation channels, message counts, company activity trends, and source-level engagement.
  • Data cleanup and topic organization: Have your agent update topic priorities or archive states, inspect change histories, and merge duplicate topics, people, or companies when needed.

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 step08 STEPS
1

Prerequisites

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

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

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

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

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

Import dependencies

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

dotenv.load_dotenv()

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

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

Create a Composio Tool Router session for Modem

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

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

Initialize the MCP Server

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

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

Create a CLI Chatloop and define the Crew

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

conversation_context = ""

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

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

    if not user_input:
        continue

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

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

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

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

Complete Code

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

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

load_dotenv()

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

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

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

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

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

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

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

    conversation_context = ""

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

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

        if not user_input:
            continue

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

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

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

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

Conclusion

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

Next steps:

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

Supported Tools

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

Add People to Company

Associate one or more existing people with an existing company.

Create Companies

Create one to 50 companies in one batch.

Create People

Create one to 50 people in one batch.

Get Channel

Get one channel's source details, connection state, context, timestamps, and message count by UUID.

Get Company

Get one company's core details, connection values, domain, logo, and VIP status by decimal ID.

Get Company Activity

Get one company's message count, weekly activity series, and source-level message breakdown.

Get Company History

Get up to 50 company audit records plus merge history.

Get Company Identities

Get external platform identities linked to one company by Modem's identify operation.

Get Current Organization

Return the organization selected by the connected API key.

Get Person

Get one person's complete profile, including company, connections, tags, sources, timestamps, identities, and message activity aggregates.

Get Person History

Get up to 50 person audit records plus merge history.

Get Person Identities

Get all external platform identities linked to one person.

Get Person Source Stats

Get one person's message counts broken down by source platform.

Get Topic

Get one topic's complete details, including its summary, classification, lifecycle, priority, keywords, time range, archive state, and event count.

Get Topic Groups

Get every message group assigned to one topic in ascending or descending group-time order.

Get Topic History

Get up to 50 topic audit records plus action and merge history.

Get Topic People

Get every unique person who participated in one topic, including source identities, company, profile, VIP state, and contribution count.

Identify External Records

Upsert links from external platform records to Modem people and companies in batches of 50.

List Channels

List organization channels with connection state and message counts, optionally filtered by source, name, or channel IDs.

List Companies

List companies with person and message aggregates, optionally searching and sorting the result.

List Groups

List message groups for exactly one company or one person, returning compact message content and topic context one page at a time.

List People

List people with aggregated message statistics, optionally filtering by search text, ecosystem tags, or company and sorting the result.

List and Search Topics

List or search topics by keywords or semantic meaning with organization, participant, source, status, date, and classification filters, one page at a time.

Merge Companies Irreversibly

Irreversibly merge one or more source companies into one surviving target.

Merge People Irreversibly

Irreversibly merge one or more source people into one surviving target.

Merge Topics Irreversibly

Irreversibly merge 1 to 50 source topics into one surviving target.

Update Companies

Update one to 50 companies in one batch.

Update People

Update one to 50 people in one batch.

Update Topic

Update one topic's priority, lifecycle, issue type, complete keyword list, or archive state.

Update Topics

Set priority or archive state for one to 100 topics at once.

FAQ

Frequently asked questions

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

Yes, you can. CrewAI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Modem tools.

Yes, absolutely. You can configure which Modem 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.

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 Modem data and credentials are handled as safely as possible.

Start with Modem.It takes 30 seconds.

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

Start building