Novita O.

Hi Mixpanel team, I want to ask about the rate limiter for remote evaluation in Mixpanel. We are getting many 429 (Too Many Requests) errors when sending requests to Mixpanel. Our service traffic is around 1000 RPM. Do you have recommendation on how to ensure the request success and is it safe for us to hit 1000 RPM?

I want to ask how many the rate limiter for remote evaluation in Mix Panel? I can’t see the documentation. We got many error when hit Mix Panel with Code 429 (Too Many Request). The service have traffic 1000 RPM.

Hi team, I saw that the optimized reentry feature can only be enabled for 90 days data. Is there any way to implement this for more than 90 days window time? We require this since the definition of our conversion rate is for users who can reenter funnel multiple times, and after migration from previous analytic tool to Mixpanel, we checked that this can’t be extended unless we parse the window time and save it somewhere in our spreadsheet.

Hi Mixpanel team! I really love your Mixpanel MCP feature, it’s super exciting to see analytics becoming more accessible through AI workflows. Because of that, I wanted to share some feedback and a product idea regarding MCP access control. Currently, Mixpanel MCP only provides a single global on/off toggle. Once enabled, it applies to all projects and all users without any granular restriction model. This creates a few security and governance concerns from our infosec team:

It would be extremely beneficial if Mixpanel could introduce granular MCP access controls, such as:

I believe these controls would help us adopt Mixpanel MCP more confidently while reducing governance and data security risks. Thanks in advance!!

Is there any way to restrict Mixpanel MCP access to only selected users within my organization or specific projects?