Amplitude
Product analytics and behavioral cohorts.
Verdict
Common use cases
- Audit tracking plan before a release
- Check cohort export status during analysis
- Create event categories to organize taxonomy
- Validate event definitions with engineering
- Delete deprecated events from the plan
Integration
- Vendor
- Amplitude
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 16
- Composio slug
amplitude
Tools
- Check Amplitude Cohort Status
Check the status of a cohort export request. this action allows you to: - poll the status of an in-progress cohort download request - determine if a cohort is ready for download
- Create Amplitude Event Category
Create a new event category in amplitude. this action allows you to: - create a new event category to organize event types - validate category name before creation key features: - creates event categories for organizing events - returns suc
- Create Amplitude Event Type
Create a new event type in amplitude. this action allows you to: - define a new event type with various properties - associate the event with a category - add metadata like description, tags, and owner key features: - creates trackable even
- Delete Amplitude Event Categorydestructive
Delete an event category from amplitude. this action allows you to: - delete an existing event category - remove category organization from events key features: - permanently removes event categories - returns success/failure status
- Delete Amplitude Event Typedestructive
Delete an event type from amplitude. this action allows you to: - remove an event type from your project - mark live events as deleted - remove planned events from the tracking plan key features: - different behavior based on event status (
- Get Amplitude Event Categories
Get event categories from amplitude. this action allows you to: - get all event categories in your project - get a specific category by name
- Get Amplitude Event Type
Get a specific event type from amplitude by name. this action allows you to: - retrieve detailed information about a single event type - get all properties and metadata for the event key features: - retrieves comprehensive event type detail
- Get Amplitude Event Types
Get all event types from amplitude. this action allows you to: - retrieve all event types in your project - optionally include deleted events
- List Amplitude Cohorts
List all discoverable cohorts for an amplitude project. this action allows you to: - get a list of all cohorts in your amplitude project - optionally include sync information for each cohort key features: - returns cohort details including
- Request Amplitude Cohort
Get a single cohort by id and initiate download. this action allows you to: - request a specific cohort from amplitude - optionally include user properties in the response - start the asynchronous download process key features: - supports f
- Restore Amplitude Event Type
Restore a deleted event type in amplitude. this action allows you to: - restore a previously deleted event type - make the event available again in the ui and api key features: - undoes the deletion of an event type - returns success/failur
- Send Events to Amplitude
Send events to amplitude using the http v2 api. this action allows you to send events to amplitude for tracking user behavior and analytics. it supports all amplitude event fields, handles proper validation, and includes comprehensive error
- Update Amplitude Cohort Membership
Incrementally update cohort membership by adding or removing ids. this action allows you to: - add new ids to an existing cohort - remove ids from an existing cohort - perform multiple operations in a single request
- Update Amplitude Event Category
Update an existing event category in amplitude. this action allows you to: - update the name of an existing event category - validate the new category name key features: - updates category names - returns success/failure status
- Update Amplitude Event Type
Update an existing event type in amplitude. this action allows you to: - change event type properties - update event name, category, metadata, and settings - modify display name for ingested events key features: - updates event type configu
- Update User Properties in Amplitude
Update user properties using amplitude's identify api. this action allows you to: - set or update the user id for a device id - update user properties without sending an event - perform operations on user properties (set, append, etc.) - up
Setup
Setup guide
- 11. In Switchy, open Settings → Integrations → Developer Tools and click 'Connect' next to Amplitude. 2. You'll be prompted to paste an Amplitude API key — generate one in Amplitude under Settings → Projects → [Your Project] → API Keys (create a new key with 'Tracking Plan' and 'Cohort' scopes enabled). 3. Paste the key into Switchy and click 'Authorize'. 4. Switchy confirms the connection and shows 'Amplitude' in your active integrations list. 5. Open any Space, type '@Amplitude get event types' and send — if the MCP returns a list of events from your project, you're connected. 6. From that point forward, @mention Amplitude in any message to invoke its tools (e.g. '@Amplitude create event type' or '@Amplitude check cohort status').
What teammates see: by default, memories from Amplitude are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Event Types
@Amplitude get all event types in our project, including any that have been marked as deleted.Open in a Space →
Create New Event Type
@Amplitude create a new event type called 'Checkout Completed' in the 'E-commerce' category, with description 'User finalized purchase and received order confirmation'.Open in a Space →
Check Cohort Export
@Amplitude check the status of cohort export request ID 12345 and let me know if it's ready for download.Open in a Space →
Organize Event Categories
@Amplitude create an event category called 'Onboarding Flows' to organize all signup and activation events.Open in a Space →
Delete Deprecated Event
@Amplitude delete the event type 'Legacy Button Click' from our project since we removed that UI element last quarter.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@amplitude list all event types in our tracking plan and show me which ones haven't been used in the last 30 days
I've retrieved 47 event types from your Amplitude project. Here are the ones with no recent activity: 'checkout_abandoned' (last seen 45 days ago), 'referral_link_clicked' (last seen 38 days ago), 'survey_completed' (no activity in 60+ days), and 'feature_flag_toggled' (last seen 33 days ago). These events are still in your tracking plan but may be candidates for deprecation if they're no longer part of your product flows. The remaining 43 events show regular activity.
This example combines Amplitude's event-type listing with the AI's ability to filter and reason over the data. Requires read access to your project's tracking plan. Note that Amplitude's API returns event metadata but not real-time usage stats—the AI infers 'last seen' from available fields, which may not reflect live event volume.
@amplitude create a new event category called 'Onboarding Flows' and move all events starting with 'onboarding_' into it
I've created the 'Onboarding Flows' category in your Amplitude project. I found 8 events matching the 'onboarding_' prefix: onboarding_started, onboarding_step_completed, onboarding_skipped, onboarding_profile_created, onboarding_team_invited, onboarding_tutorial_viewed, onboarding_survey_submitted, and onboarding_finished. All 8 events have been reassigned to the new category. This should make it easier to filter onboarding analytics in your dashboards.
This demonstrates Amplitude's category-management tools and the AI's ability to batch-update events. Requires write access to your project's taxonomy. Be aware that moving events to a new category affects how they appear in Amplitude's UI for all team members—coordinate with your analytics team before making bulk changes.
@amplitude check if our 'high-value users' cohort export from this morning is ready, and if so, summarize the cohort size and any notable segments
The 'high-value users' cohort export (request ID: coh_abc123) completed at 9:47 AM and is ready for download. The cohort contains 3,842 users. Based on the cohort's definition (users with >$500 LTV in the last 90 days), this represents about 12% of your active user base. The export includes user IDs, email addresses, and LTV values. You can download the full CSV from the Amplitude UI or use the provided download URL (expires in 24 hours).
This showcases Amplitude's cohort-export polling, useful for syncing high-value segments to other tools (email platforms, ad networks). The MCP checks export status but doesn't download the file itself—you'll need to handle the download URL separately. Cohort exports can take 5-30 minutes depending on size, so this is typically used after initiating an export earlier.
Use-case deep-dives
When this MCP makes sense for taxonomy overhaul
A 6-person product team at a B2B SaaS company runs a quarterly event-tracking audit. They have 200+ events in Amplitude, half of them deprecated or duplicated from old feature launches. The team uses Switchy to batch-rename event categories, delete obsolete event types, and tag active events with owner metadata—all without opening the Amplitude UI. This MCP is the right call if your team does infrequent, high-volume taxonomy work and you already have the event names documented in a spreadsheet or Linear epic. If you're doing daily ad-hoc queries or building dashboards, the Amplitude web app is faster. The buying moment: you're staring at a 50-row CSV of events to clean up and you don't want to click through the UI 50 times.
When this MCP speeds up tracking plan documentation
A startup hires its first analytics engineer to own the Amplitude tracking plan. The engineer needs to audit every event type, understand which properties exist, and document ownership in Notion. Using Switchy with this MCP, they pull all event types and categories in one pass, export the schema to markdown, and cross-reference it with the codebase. This works well for teams under 500 events where the tracking plan fits in a single doc. If your event volume is over 1,000 or you need to join event data with user cohorts, the MCP's 16 tools won't cover the full workflow—you'll still need the Amplitude API or SQL export. The buying call: you're onboarding someone who needs to learn the tracking plan in a week, not three months of clicking around.
When this MCP isn't the right fit for real-time debugging
A 3-person support team gets a ticket: 'Why didn't my upgrade event fire?' They want to check if the event type exists in Amplitude and see its recent status. This MCP can retrieve the event type definition and confirm it's not deleted, but it can't query actual event data or user timelines—that requires the Amplitude Query API or the web app's user lookup. The MCP is useful if the question is 'Is this event in our tracking plan?' but not 'Did this user trigger this event yesterday?' For real-time debugging, you need the full Amplitude interface or a separate MCP that wraps the Analytics API. The threshold: if your support flow involves checking event definitions more than twice a week, this MCP saves 10 minutes per lookup. Otherwise, bookmark the Amplitude events page.
Frequently asked
What does the Amplitude MCP let me do in Switchy?
It lets your AI agents read and manage your Amplitude event taxonomy — create event types, organize them into categories, check cohort export status, and pull event definitions. Useful if you're building prompts that need to understand your product analytics setup or automate tracking plan maintenance.
Do I need admin access to connect Amplitude?
You need an Amplitude API key with sufficient permissions to read and write event types and categories. Typically that means Manager or Admin role in your Amplitude org. If you only want read access, a Viewer key works for the get-event tools but won't let agents create or delete anything.
Can the MCP send events to Amplitude or query user data?
No. This MCP manages your tracking plan metadata — event types, categories, cohort export status — not the actual event stream or user profiles. If you need to send events or run behavioral queries, use Amplitude's HTTP API or Batch API directly.
Why use this instead of editing my tracking plan in Amplitude's UI?
You wouldn't replace the UI. This is for programmatic workflows — like an agent that auto-generates event definitions from a product spec, or a prompt that checks which events are marked deleted before writing SQL. It's faster than clicking through Data when you need to inspect or bulk-update dozens of event types.
Who on my team should connect this MCP?
Whoever owns your Amplitude tracking plan — usually a product analyst or data lead. They'll need to generate the API key and decide whether agents should have write access. If your team just needs to read event definitions for documentation prompts, a read-only key is safer.