From 6834daf07215a5fcbd07553ad2153840625b3608 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 17 Jul 2026 01:14:25 +0000 Subject: [PATCH 1/3] Initial plan From ee36484c1fa1c1a93e169a60a5cbb6a5552dacfa Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 17 Jul 2026 01:16:34 +0000 Subject: [PATCH 2/3] docs(TOF-303): update MCP docs for default enablement MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit MCP is now enabled by default for all organizations. Admins can disable it in Settings → Org → Overview if needed. - Update Permissions & Access note to reflect on-by-default - Remove "MCP must be enabled" from Service Accounts prerequisites - Update Security Considerations bullet from off-by-default to on-by-default - Update Troubleshooting to say "disabled" instead of "not enabled" --- docs/mcp.mdx | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/mcp.mdx b/docs/mcp.mdx index a29a638c..f5ac0f1d 100644 --- a/docs/mcp.mdx +++ b/docs/mcp.mdx @@ -79,10 +79,10 @@ A typical workflow looks like: ## Permissions & Access - **Admin setup required.** An organization admin must enable MCP in **Settings → Org → Overview** before anyone can connect. Changes can take up to 15 minutes to take effect. + **MCP is enabled by default.** Any Mixpanel user in your organization can connect right away. Organization admins can disable MCP in **Settings → Org → Overview** if needed. Changes can take up to 15 minutes to take effect. -Once enabled, any Mixpanel user in your organization can connect. Users authenticate with their own Mixpanel credentials, so all existing project permissions and roles apply — users can only see data from projects they already have access to. +Any Mixpanel user in your organization can connect. Users authenticate with their own Mixpanel credentials, so all existing project permissions and roles apply — users can only see data from projects they already have access to. ## Connecting to the MCP Server @@ -205,7 +205,6 @@ Use service accounts when you need a headless MCP connection, such as CI/CD pipe 1. **Create a service account** in your [Organization settings](https://mixpanel.com/settings/org#serviceaccounts) or [Project settings](https://mixpanel.com/settings/project#serviceaccounts). You need Owner or Admin permissions to do this. 2. **Save the username and secret** — you won't be able to view the secret again after creation. 3. **Ensure the service account has access** to the projects you want to query via MCP. -4. **MCP must be enabled** by an org admin in **Settings → Org → Overview**. ### Generating the Authorization Header @@ -403,7 +402,7 @@ Once connected, try asking your AI assistant: When connected, the AI assistant can both **read and write** to Mixpanel on your behalf. Your Mixpanel data is also sent to whichever AI provider you're using (Claude, ChatGPT, etc.), so review that provider's data handling policies before connecting. **Access controls** -- MCP must be explicitly enabled by an org admin. It is off by default +- MCP is enabled by default; org admins can disable it in **Settings → Org → Overview** - Users can only access projects they already have permission to view in Mixpanel - All existing roles and project-level permissions remain in effect @@ -413,9 +412,9 @@ When connected, the AI assistant can both **read and write** to Mixpanel on your ## Troubleshooting -- **"MCP access is not enabled for this project"**: Ask your org admin to enable MCP in **Settings → Org → Overview**. +- **"MCP access is not enabled for this project"**: Ask your org admin to check that MCP has not been disabled in **Settings → Org → Overview**. - **"Missing scope" error**: Your cached auth token was created with an outdated scope list. Delete the `.mcp-auth` folder in the directory where you ran the authorization command, then re-authorize. -- **Authorization fails**: Ensure your Mixpanel account has access to at least one project and that MCP is enabled at the org level. +- **Authorization fails**: Ensure your Mixpanel account has access to at least one project and that MCP has not been disabled at the org level. - **Desktop app doesn't pick up config changes**: Restart the application after editing the config file. ## Rate Limits From 3f2db3a870d0fb0bda4c8918810c86f874222b1e Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 17 Jul 2026 01:20:47 +0000 Subject: [PATCH 3/3] docs(TOF-303): correct MCP default enablement scope MCP is only enabled by default for new free and growth accounts created after August 1, 2026. All other accounts still require an org admin to enable it. - Permissions & Access: two-tier note distinguishing new free/growth accounts (on by default) from all others (admin required) - Service Accounts prerequisites: restore step 4 requiring admin enablement, with caveat for new accounts - Security Considerations: restore "must be enabled by admin" bullet with note about new account default - Troubleshooting: restore original wording for admin enablement --- docs/mcp.mdx | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/docs/mcp.mdx b/docs/mcp.mdx index f5ac0f1d..61c65549 100644 --- a/docs/mcp.mdx +++ b/docs/mcp.mdx @@ -79,10 +79,14 @@ A typical workflow looks like: ## Permissions & Access - **MCP is enabled by default.** Any Mixpanel user in your organization can connect right away. Organization admins can disable MCP in **Settings → Org → Overview** if needed. Changes can take up to 15 minutes to take effect. + **New free and growth accounts (created after August 1, 2026):** MCP is enabled by default — no admin action required. Organization admins can disable it in **Settings → Org → Overview** if needed. + + **All other accounts:** An organization admin must enable MCP in **Settings → Org → Overview** before anyone can connect. + + Changes can take up to 15 minutes to take effect. -Any Mixpanel user in your organization can connect. Users authenticate with their own Mixpanel credentials, so all existing project permissions and roles apply — users can only see data from projects they already have access to. +Once MCP is enabled, any Mixpanel user in your organization can connect. Users authenticate with their own Mixpanel credentials, so all existing project permissions and roles apply — users can only see data from projects they already have access to. ## Connecting to the MCP Server @@ -205,6 +209,7 @@ Use service accounts when you need a headless MCP connection, such as CI/CD pipe 1. **Create a service account** in your [Organization settings](https://mixpanel.com/settings/org#serviceaccounts) or [Project settings](https://mixpanel.com/settings/project#serviceaccounts). You need Owner or Admin permissions to do this. 2. **Save the username and secret** — you won't be able to view the secret again after creation. 3. **Ensure the service account has access** to the projects you want to query via MCP. +4. **MCP must be enabled** by an org admin in **Settings → Org → Overview** (free and growth accounts created after August 1, 2026 have it enabled by default). ### Generating the Authorization Header @@ -402,7 +407,7 @@ Once connected, try asking your AI assistant: When connected, the AI assistant can both **read and write** to Mixpanel on your behalf. Your Mixpanel data is also sent to whichever AI provider you're using (Claude, ChatGPT, etc.), so review that provider's data handling policies before connecting. **Access controls** -- MCP is enabled by default; org admins can disable it in **Settings → Org → Overview** +- MCP must be enabled by an org admin in **Settings → Org → Overview** (free and growth accounts created after August 1, 2026 have it on by default; admins can still disable it) - Users can only access projects they already have permission to view in Mixpanel - All existing roles and project-level permissions remain in effect @@ -412,9 +417,9 @@ When connected, the AI assistant can both **read and write** to Mixpanel on your ## Troubleshooting -- **"MCP access is not enabled for this project"**: Ask your org admin to check that MCP has not been disabled in **Settings → Org → Overview**. +- **"MCP access is not enabled for this project"**: Ask your org admin to enable MCP in **Settings → Org → Overview**. - **"Missing scope" error**: Your cached auth token was created with an outdated scope list. Delete the `.mcp-auth` folder in the directory where you ran the authorization command, then re-authorize. -- **Authorization fails**: Ensure your Mixpanel account has access to at least one project and that MCP has not been disabled at the org level. +- **Authorization fails**: Ensure your Mixpanel account has access to at least one project and that MCP is enabled at the org level. - **Desktop app doesn't pick up config changes**: Restart the application after editing the config file. ## Rate Limits