
Amplitude Automation
Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user...
Install
npx skills add davepoon/buildwithclaude --skill amplitude-automation -g -a claude-code -y- Repository
- davepoon/buildwithclaude3.7k
- Category
- AI and agents
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 1,969 tokens
- Runs scripts
- No, instructions only
What it does
Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.
Amplitude Automation via Rube MCP
Automate Amplitude product analytics through Composio's Amplitude toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/amplitude
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Amplitude connection via
RUBE_MANAGE_CONNECTIONSwith toolkitamplitude - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed, just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitamplitude - If connection is not ACTIVE, follow the returned auth link to complete Amplitude authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Send Events
When to use: User wants to track events or send event data to Amplitude
Tool sequence:
AMPLITUDE_SEND_EVENTS- Send one or more events to Amplitude [Required]
Key parameters:
events: Array of event objects, each containing:event_type: Name of the event (e.g., 'page_view', 'purchase')user_id: Unique user identifier (required if nodevice_id)device_id: Device identifier (required if nouser_id)event_properties: Object with custom event propertiesuser_properties: Object with user properties to settime: Event timestamp in milliseconds since epoch
Pitfalls:
- At least one of
user_idordevice_idis required per event event_typeis required for every event; cannot be emptytimemust be in milliseconds (13-digit epoch), not seconds- Batch limit applies; check schema for maximum events per request
- Events are processed asynchronously; successful API response does not mean data is immediately queryable

