How to Restrict Mixpanel MCP Access to Selected Users or Specific Projects?

Novita O. · 2026-05-08T02:05:26.537Z

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

3 comments

· Sorted by Oldest

kapa.ai
APP
·
(edited)·
Based on the knowledge sources, here is what's available for controlling MCP access:
MCP Access Controls
The Mixpanel MCP server has the following built-in access controls:
Org-level toggle: MCP must be explicitly enabled by an organization admin in Settings → Org → Overview. It is off by default. [MCP Security]
No per-user restriction: Once enabled, any Mixpanel user in your organization can connect — there is no way to restrict MCP access to only selected users within the org. [MCP Docs]
Existing project permissions apply: Users authenticate with their own Mixpanel credentials, so they can only access projects they already have permission to view. All existing roles and project-level permissions remain in effect. [MCP Security]

What This Means in Practice
Since MCP respects existing project-level permissions, you can indirectly control what data users can access via MCP by:
1.
Project roles: Ensure users only have access to the specific projects they need. [Roles & Permissions]
2.
Data Views: Restrict what data a user sees within a project by assigning them to filtered Data Views. [Data Views]
3.
Classified Data: Mark sensitive properties as classified so only authorized users can view them, even through MCP. [Data Classification]

Key Limitation
There is currently no way to allow MCP for some users but not others within the same organization — it's an all-or-nothing toggle at the org level. If you need to limit exposure, your best lever is tightly managing project memberships and Data Views before enabling MCP.
⚠️ Also note: MCP does not support HIPAA requirements and is not covered by Mixpanel's BAA. [MCP Security]
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Novita O.
·
·
kapa.ai is there any plan to develop this restriction model?
kapa.ai
APP
·
(edited)·
I'm sorry, but the knowledge sources do not contain any information about planned developments or a roadmap for per-user MCP access restrictions. I cannot speculate on future product plans. For the most up-to-date information on what's coming, I'd recommend:
Checking Mixpanel's public changelog
Reaching out directly to Mixpanel's support or sales team
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

kapa.ai
APP
·
(edited)·
Based on the knowledge sources, here is what's available for controlling MCP access:
MCP Access Controls
The Mixpanel MCP server has the following built-in access controls:
Org-level toggle: MCP must be explicitly enabled by an organization admin in Settings → Org → Overview. It is off by default. [MCP Security]
No per-user restriction: Once enabled, any Mixpanel user in your organization can connect — there is no way to restrict MCP access to only selected users within the org. [MCP Docs]
Existing project permissions apply: Users authenticate with their own Mixpanel credentials, so they can only access projects they already have permission to view. All existing roles and project-level permissions remain in effect. [MCP Security]

What This Means in Practice
Since MCP respects existing project-level permissions, you can indirectly control what data users can access via MCP by:
1.
Project roles: Ensure users only have access to the specific projects they need. [Roles & Permissions]
2.
Data Views: Restrict what data a user sees within a project by assigning them to filtered Data Views. [Data Views]
3.
Classified Data: Mark sensitive properties as classified so only authorized users can view them, even through MCP. [Data Classification]

Key Limitation
There is currently no way to allow MCP for some users but not others within the same organization — it's an all-or-nothing toggle at the org level. If you need to limit exposure, your best lever is tightly managing project memberships and Data Views before enabling MCP.
⚠️ Also note: MCP does not support HIPAA requirements and is not covered by Mixpanel's BAA. [MCP Security]
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Novita O.
·
·
kapa.ai is there any plan to develop this restriction model?
kapa.ai
APP
·
(edited)·
I'm sorry, but the knowledge sources do not contain any information about planned developments or a roadmap for per-user MCP access restrictions. I cannot speculate on future product plans. For the most up-to-date information on what's coming, I'd recommend:
Checking Mixpanel's public changelog
Reaching out directly to Mixpanel's support or sales team
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

How to Restrict Mixpanel MCP Access to Selected Users or Specific Projects? | Mixpanel Community

3 comments

MCP Access Controls

What This Means in Practice

Key Limitation

MCP Access Controls

What This Means in Practice

Key Limitation