How to integrate Amplitude MCP with CrewAI

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Amplitude logo
CrewAI logo
divider

Introduction

This guide walks you through connecting Amplitude to CrewAI using the Composio tool router. By the end, you'll have a working Amplitude agent that can get daily active users for last month, generate funnel analysis for onboarding flow, list top events for premium users through natural language commands.

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

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

Also integrate Amplitude with

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Amplitude connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Amplitude
  • Build a conversational loop where your agent can execute Amplitude 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 Amplitude MCP server, and what's possible with it?

The Amplitude MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Amplitude account. It provides structured and secure access to your analytics platform, so your agent can perform actions like managing event types, organizing cohorts, updating user properties, and tracking event categories on your behalf.

  • Cohort and user management: Ask your agent to request, download, and check the status of specific user cohorts for advanced segmentation or analysis.
  • Event type and category administration: Effortlessly create, update, or delete event types and categories, keeping your analytics taxonomy organized and up to date.
  • User property updates: Direct your agent to set or modify user properties—like device information or location—without sending new events, making user profile management a breeze.
  • Comprehensive analytics lookup: Retrieve detailed information about event types and categories, enabling your agent to provide insights or answer analytics questions in real time.

Supported Tools & Triggers

Tools
Bulk Assign Annotations to CategoryTool to bulk assign multiple annotations to a category in Amplitude.
Cancel User DeletionCancel a pending user deletion request in Amplitude.
Check Amplitude Cohort StatusCheck the status of a cohort export request.
Create Chart Annotation in AmplitudeCreate a chart annotation in Amplitude to mark important dates.
Create Annotation CategoryTool to create an annotation category in Amplitude to organize annotations.
Create Amplitude Event CategoryCreate a new event category in Amplitude.
Create Amplitude Event TypeCreate a new event type in Amplitude.
Create Amplitude ReleaseCreate a release to document product changes.
Delete Amplitude Chart AnnotationDelete a chart annotation from Amplitude.
Delete Amplitude Annotation CategoryDelete an annotation category from Amplitude.
Delete Amplitude Event CategoryDelete an event category from Amplitude.
Delete Amplitude Event TypeDelete an event type from Amplitude.
Delete Amplitude UsersSubmit user deletion requests for GDPR/CCPA compliance.
Download Amplitude Cohort FileDownload the cohort file after request is complete.
Search Amplitude UserSearch for users in Amplitude by canonical identifier (Amplitude ID, device ID, user ID, or user ID prefix).
Get Active or New UsersGet the number of active or new users for a date range with optional segmentation.
Get Amplitude AnnotationGet a single chart annotation by ID from Amplitude.
Get Amplitude Annotation CategoryGet a single annotation category by ID from Amplitude.
Request Amplitude CohortGet a single cohort by ID and initiate download.
Get User Deletion RequestsGet the status of user deletion requests within a date range.
Get Amplitude Event CategoriesGet event categories from Amplitude.
Get Amplitude Event PropertyGet a specific event property from Amplitude taxonomy.
Get Event Segmentation DataGet event segmentation data from Amplitude Analytics API.
Get Amplitude Event TypeGet a specific event type from Amplitude by name.
Get Amplitude Event TypesGet all event types from Amplitude.
Get Funnel Analysis DataGet funnel analysis data showing user conversion through a sequence of events.
Get Real-time Active UsersGet real-time active users count from Amplitude.
Get User Retention AnalysisGet user retention analysis showing how users return over time after a starting action.
Get Revenue LTV MetricsGet revenue lifetime value (LTV) metrics including ARPU, ARPPU, and total revenue.
Get Session Average LengthGet average session length (in seconds) for a specified date range from Amplitude.
Get Session Length DistributionTool to retrieve session length distribution data for a specified date range from Amplitude.
Get Sessions Per User from AmplitudeTool to get average number of sessions per user for each day in a date range from Amplitude.
Get User Activity from AmplitudeFetch a single user's profile summary and event stream by Amplitude ID.
Get User Composition by PropertyTool to get user composition breakdown by property (platform, version, country, etc.
Get User MappingsGet the list of user mappings for provided user IDs.
Get Amplitude User PropertyGet a specific user property from Amplitude taxonomy.
Update User Properties in AmplitudeUpdate user properties using Amplitude's Identify API.
List Amplitude Annotation CategoriesList all annotation categories from Amplitude.
List Chart AnnotationsTool to get all chart annotations with optional filtering by category, chart, and date range.
List Amplitude CohortsList all discoverable cohorts for an Amplitude project.
List Amplitude Event PropertiesGet all event properties from Amplitude, optionally filtered by event type or property name.
List Amplitude EventsTool to get a list of all event types in your Amplitude project with current week's statistics.
List Amplitude User PropertiesTool to get all user properties in your Amplitude project.
Map Users in AmplitudeMap users with different user IDs together (alias/merge users) in Amplitude.
Restore Amplitude Event TypeRestore a deleted event type in Amplitude.
Send Events to AmplitudeSend events to Amplitude using the HTTP V2 API.
Set Group Properties in AmplitudeSet group properties for account-level reporting without sending an event.
Update Amplitude Chart AnnotationTool to update an existing chart annotation in Amplitude.
Update Amplitude Annotation CategoryTool to update an annotation category in Amplitude.
Update Amplitude Cohort MembershipIncrementally update cohort membership by adding or removing IDs.
Update Amplitude Event CategoryUpdate an existing event category in Amplitude.
Update Amplitude Event TypeUpdate an existing event type in Amplitude.
Batch Upload Events to AmplitudeBulk upload events to Amplitude using the Batch Event Upload API.
Upload Amplitude CohortGenerate a new cohort or update an existing cohort by uploading user IDs or Amplitude IDs.

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

Prerequisites

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

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.

Install dependencies

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

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

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 Amplitude MCP URL

Create a Composio Tool Router session for Amplitude

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

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

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.

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 Amplitude 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=["amplitude"],
)
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 Amplitude through Composio's Tool Router. The agent can perform Amplitude 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

How to build Amplitude MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Amplitude MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Amplitude MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Amplitude MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Amplitude MCP with Claude Cowork

Codex logo

Codex

Use Amplitude MCP with Codex

OpenClaw logo

OpenClaw

Use Amplitude MCP with OpenClaw

Hermes logo

Hermes

Use Amplitude MCP with Hermes

CLI logo

CLI

Use Amplitude MCP with CLI

Google ADK logo

Google ADK

Use Amplitude MCP with Google ADK

LangChain logo

LangChain

Use Amplitude MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Amplitude MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Amplitude MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Amplitude MCP with LlamaIndex

FAQ

What are the differences in Tool Router MCP and Amplitude MCP?

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

Can I use Tool Router MCP with CrewAI?

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 Amplitude tools.

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

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

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 freeGet a demo↗