All 4 tools write and none read: events leave through mixpanel_track_event, mixpanel_track_pageview and mixpanel_track_signup, profile state through mixpanel_set_user_profile, and there is no query, funnel or report tool to read any of it back. Identity stays the caller's responsibility — mixpanel_track_event, mixpanel_track_pageview and mixpanel_set_user_profile each take a distinct_id you supply, while mixpanel_track_signup keys off the email address. That makes this a way to emit telemetry from an agent workflow, not a way to analyse what was emitted.
A write-side Mixpanel client: 4 tools that emit events and profile updates into a project.
- Custom events: mixpanel_track_event sends a named event for a distinct_id with whatever properties you attach.
- Page views as their own call: mixpanel_track_pageview takes a page_name and a referrer alongside the distinct_id.
- Signup and profile creation in one step: mixpanel_track_signup takes an email, a user_name and a plan.
- Profile maintenance: mixpanel_set_user_profile updates an existing user's profile properties by distinct_id.
A Mixpanel project and its token.
One command — npx -y mixpanel-mcp-server --token YOUR_MIXPANEL_TOKEN