How to integrate Amplitude MCP with Pydantic AI

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Amplitude logo
Pydantic AI logo
divider

Introduction

This guide walks you through connecting Amplitude to Pydantic AI 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 Pydantic AI 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:
  • How to set up your Composio API key and User ID
  • How to create a Composio Tool Router session for Amplitude
  • How to attach an MCP Server to a Pydantic AI agent
  • How to stream responses and maintain chat history
  • How to build a simple REPL-style chat interface to test your Amplitude workflows

What is Pydantic AI?

Pydantic AI is a Python framework for building AI agents with strong typing and validation. It leverages Pydantic's data validation capabilities to create robust, type-safe AI applications.

Key features include:

  • Type Safety: Built on Pydantic for automatic data validation
  • MCP Support: Native support for Model Context Protocol servers
  • Streaming: Built-in support for streaming responses
  • Async First: Designed for async/await patterns

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 with an active API key
  • Basic familiarity with Python and async programming

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 pydantic-ai python-dotenv

Install the required libraries.

What's happening:

  • composio connects your agent to external SaaS tools like Amplitude
  • pydantic-ai lets you create structured AI agents with tool support
  • python-dotenv loads your environment variables securely from a .env file

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

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your agent to Composio's API
  • USER_ID associates your session with your account for secure tool access
  • OPENAI_API_KEY to access OpenAI LLMs

Import dependencies

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()
What's happening:
  • We load environment variables and import required modules
  • Composio manages connections to Amplitude
  • MCPServerStreamableHTTP connects to the Amplitude MCP server endpoint
  • Agent from Pydantic AI lets you define and run the AI assistant

Create a Tool Router Session

python
async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Amplitude
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["amplitude"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")
What's happening:
  • We're creating a Tool Router session that gives your agent access to Amplitude 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

Initialize the Pydantic AI Agent

python
# Attach the MCP server to a Pydantic AI Agent
amplitude_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
agent = Agent(
    "openai:gpt-5",
    toolsets=[amplitude_mcp],
    instructions=(
        "You are a Amplitude assistant. Use Amplitude tools to help users "
        "with their requests. Ask clarifying questions when needed."
    ),
)
What's happening:
  • The MCP client connects to the Amplitude endpoint
  • The agent uses GPT-5 to interpret user commands and perform Amplitude operations
  • The instructions field defines the agent's role and behavior

Build the chat interface

python
# Simple REPL with message history
history = []
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to help you with Amplitude.\n")

while True:
    user_input = input("You: ").strip()
    if user_input.lower() in {"exit", "quit", "bye"}:
        print("\nGoodbye!")
        break
    if not user_input:
        continue

    print("\nAgent is thinking...\n", flush=True)

    async with agent.run_stream(user_input, message_history=history) as stream_result:
        collected_text = ""
        async for chunk in stream_result.stream_output():
            text_piece = None
            if isinstance(chunk, str):
                text_piece = chunk
            elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                text_piece = chunk.delta
            elif hasattr(chunk, "text"):
                text_piece = chunk.text
            if text_piece:
                collected_text += text_piece
        result = stream_result

    print(f"Agent: {collected_text}\n")
    history = result.all_messages()
What's happening:
  • The agent reads input from the terminal and streams its response
  • Amplitude API calls happen automatically under the hood
  • The model keeps conversation history to maintain context across turns

Run the application

python
if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • The asyncio loop launches the agent and keeps it running until you exit

Complete Code

Here's the complete code to get you started with Amplitude and Pydantic AI:

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()

async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Amplitude
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["amplitude"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")

    # Attach the MCP server to a Pydantic AI Agent
    amplitude_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
    agent = Agent(
        "openai:gpt-5",
        toolsets=[amplitude_mcp],
        instructions=(
            "You are a Amplitude assistant. Use Amplitude tools to help users "
            "with their requests. Ask clarifying questions when needed."
        ),
    )

    # Simple REPL with message history
    history = []
    print("Chat started! Type 'exit' or 'quit' to end.\n")
    print("Try asking the agent to help you with Amplitude.\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "bye"}:
            print("\nGoodbye!")
            break
        if not user_input:
            continue

        print("\nAgent is thinking...\n", flush=True)

        async with agent.run_stream(user_input, message_history=history) as stream_result:
            collected_text = ""
            async for chunk in stream_result.stream_output():
                text_piece = None
                if isinstance(chunk, str):
                    text_piece = chunk
                elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                    text_piece = chunk.delta
                elif hasattr(chunk, "text"):
                    text_piece = chunk.text
                if text_piece:
                    collected_text += text_piece
            result = stream_result

        print(f"Agent: {collected_text}\n")
        history = result.all_messages()

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

Conclusion

You've built a Pydantic AI agent that can interact with Amplitude through Composio's Tool Router. With this setup, your agent can perform real Amplitude actions through natural language. You can extend this further by:
  • Adding other toolkits like Gmail, HubSpot, or Salesforce
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows (for example, Gmail + Amplitude for workflow automation)
This architecture makes your AI agent "agent-native", able to securely use APIs in a unified, composable way without custom integrations.

How to build Amplitude MCP Agent with another framework

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 Pydantic AI?

Yes, you can. Pydantic 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 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.