Can my AI agent debug a specific user dropping out of our onboarding?

Yes. Search for the user by their email or ID using `search_users`, completely avoiding the manual lookup. Then, ask your agent to pull their raw activity stream via `get_user_activity`. The agent will retrieve all events triggered by this user, making it simple to spot exactly where they failed or stopped interacting.

Can I request funnel conversions without building a dashboard manually?

Absolutely. You can provide a sequence of events (e.g., 'Homepage Viewed', 'Sign Up Clicked', 'Account Created') and ask for the funnel conversion for the last 7 days. Your AI agent queries Amplitude and parses the exact drop-off rates at each step right into your prompt window.

How does the cohort fetching work for custom targeted segments?

Your agent can list all available cohorts associated with your project. Once you find the target cohort's ID, you can use the `get_cohort` tool to request its download URL. This is incredibly useful for instantly moving targeted lists of power-users or churned-users into your other workflows.

Amplitude MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Amplitude
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Amplitude through Vinkius, pass the Edge URL in the `mcps` parameter and every Amplitude tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Amplitude Specialist",
    goal="Help users interact with Amplitude effectively",
    backstory=(
        "You are an expert at leveraging Amplitude tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Amplitude "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Amplitude MCP Server

Connect your Amplitude account to your AI agent and seamlessly query behavioral data and product analytics using natural language.

When paired with CrewAI, Amplitude becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Amplitude tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

User Activity & Search — Search for specific users and track their detailed event stream to diagnose individual journeys
Funnels & Conversions — Request step-by-step conversion funnels to identify where users drop off
Retention — Generate day-over-day retention curves to understand how well features keep users engaged
Segmentation — Query event counts and uniques over time to see clear adoption trends
Cohorts — List your behavioral cohorts, view sizes, and request exports for further targeted analysis
Active Users & Revenue — Instantly pull DAU/WAU/MAU and daily revenue metrics right into your workflow

The Amplitude MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Amplitude to CrewAI via MCP

Follow these steps to integrate the Amplitude MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Amplitude

Why Use CrewAI with the Amplitude MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Amplitude through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Amplitude + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Amplitude MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Amplitude for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Amplitude, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Amplitude tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Amplitude against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Amplitude MCP Tools for CrewAI (10)

These 10 tools become available when you connect Amplitude to CrewAI via MCP:

active_users

Start/End as YYYYMMDD. Get Amplitude daily/weekly/monthly active users (DAU/WAU/MAU)

event_segmentation

Pass event name, start/end as YYYYMMDD. Query Amplitude event segmentation

export_events

Amplitude is a product analytics platform. Pass start/end as YYYYMMDDTHH (e.g. 2026010100). Export raw Amplitude event data for a time range

get_cohort

Depending on the backend this may require polling until ready. Request an Amplitude cohort download

get_funnel

Pass comma-separated event names, start/end as YYYYMMDD. Query Amplitude funnel conversion

get_retention

Pass start_event (acquisition), return_event, start/end dates. Start/End should be YYYYMMDD. Query Amplitude retention

get_user_activity

Useful for diagnosing individual user journeys. Get Amplitude user activity stream

list_cohorts

Cohorts group users by behavior. List Amplitude behavioral cohorts

revenue_analysis

Start/End as YYYYMMDD. Get Amplitude revenue analysis by day

search_users

Useful to find specific users before checking their activity. Search Amplitude users by user ID, device ID, or email

Example Prompts for Amplitude in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Amplitude immediately.

"What's our funnel conversion from 'Landing_Page_View' to 'Sign_Up_Success' for the last 3 days?"

"Show the recent user activity for customer email@example.com"

"What is our Daily Active Users (DAU) count since start of the month?"

Troubleshooting Amplitude MCP Server with CrewAI

Common issues when connecting Amplitude to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Amplitude + CrewAI FAQ

Common questions about integrating Amplitude MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.