| name | amplitude-automation |
| description | Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | business-marketing |
| category | analytics |
| risk | critical |
| source | community |
| tags | ["skill","business-marketing","analytics","amplitude","automation"] |
Amplitude Automation via Rube MCP
Automate Amplitude product analytics through Composio's Amplitude toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Amplitude connection via
RUBE_MANAGE_CONNECTIONS with toolkit amplitude
- Always call
RUBE_SEARCH_TOOLS first 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_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit amplitude
- 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 no device_id)device_id: Device identifier (required if no user_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_id or device_id is required per event
event_type is required for every event; cannot be emptytime must 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
