Hunter H.

Robin H. Looks like OAI may have reverted the change causing that field to be required even if the label is not up to date. Worth trying it again.

Robin H. Weird, not for me. Good luck.

Those fields are for if there is a static/non-per-user type configuration. But also, see above - Mixpanel are working through some scoping issues that may impact your ability to auth until resolved.

Robin H. Skip those, they are optional fields but leave it set to OAuth. It will then prompt you to login to Mixpanel to authenticate.

Sharan M. In case useful to the team, I'm seeing some failures calling retention reports via MCP, perhaps auth scoping related. Failed to execute run_retention_query: Unexpected error: HTTP 403: You do not have the required scope(s) for this request

Sharan M. Will send you an email for sure!

Thanks from me also! Some on my team have gotten so used to having this, they were starting to give me some side-eye when they couldn't get on. 🙂

This stopped working for me today so I can't do double-check now but yes, I have found it very useful. Allowed me to build an agent that my non-technical folks can use to do a deep-dive on sales prospects. The users of this tool would be lost in the Mixpanel UI.

Very simple for me to reproduce using the npx command from your docs: npx -y mcp-remote https://mcp.mixpanel.com/sse --allow-http . Using the generated URL then shows the error. MCP is enabled for the org (and was working previously).

Marisa B. This has been working for me in Cursor in general but as of today, Mixpanel returns 'invalid scope' during the oAuth process. The scopes it is asking for are openid, email and profile.