Mixpanel MCP Integration: Error Overwriting 'args' in LogRecord

Kasper W. · 2025-12-09T14:44:41.514Z

I’m using the Mixpanel MCP integration from Cursor and every MCP call I try (at least get_projects, get_events, get_issues) fails with the error Attempt to overwrite 'args' in LogRecord. Is this a known issue on the MCP backend or is there a workaround?

Mixpanel MCP Integration: Error Overwriting 'args' in LogRecord | Mixpanel Community

3 comments

· Sorted by Oldest

kapa.ai
APP
·
·
Hi Kasper W., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
kapa.ai
APP
·
·
The available Mixpanel MCP documentation and blog posts do not mention an error like Attempt to overwrite 'args' in LogRecord, nor any known MCP backend issue with get_projects, get_events, or get_issues when used from Cursor.[MCP overview][MCP troubleshooting]The documented MCP “Common Issues” are limited to Node.js missing, authorization problems, desktop app glitches, and free-user limitations, none of which match this error.[MCP troubleshooting] The implementation steps for Cursor only describe configuring mcpServers with npx mcp-remote and completing OAuth, with no mention of this logging-related failure.[MCP implementation]Because of that, I can’t confirm from the docs whether this is: - a Mixpanel MCP server bug, or - an issue in Cursor’s MCP client / mcp-remote / local environment (the error string looks like a client‑side logging problem, but this is not documented).Documented next steps for MCP issues are generic: ensure Node is installed, re‑run authorization, and restart the desktop app.[MCP troubleshooting] There is no official workaround or configuration change in the docs for your specific error.Given the lack of coverage in the knowledge sources, the best documented guidance I can offer is: - Double‑check you followed the Cursor setup and OAuth flow exactly as described in the MCP “Option 3: Cursor” section (including data residency URL, scopes, and mcpServers config).[MCP implementation] - If the problem persists, this specific error is not documented; you’ll likely need to contact Mixpanel support or your CSM and reference the MCP beta docs and your environment (Cursor + MCP + mcp-remote), since MCP is explicitly in beta.[MCP overview]So: this exact error is not listed as a known MCP backend issue in the docs, and no official workaround is documented.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Kasper W.
·
·
FYI. This works again

kapa.ai
APP
·
·
Hi Kasper W., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
kapa.ai
APP
·
·
The available Mixpanel MCP documentation and blog posts do not mention an error like Attempt to overwrite 'args' in LogRecord, nor any known MCP backend issue with get_projects, get_events, or get_issues when used from Cursor.[MCP overview][MCP troubleshooting]The documented MCP “Common Issues” are limited to Node.js missing, authorization problems, desktop app glitches, and free-user limitations, none of which match this error.[MCP troubleshooting] The implementation steps for Cursor only describe configuring mcpServers with npx mcp-remote and completing OAuth, with no mention of this logging-related failure.[MCP implementation]Because of that, I can’t confirm from the docs whether this is: - a Mixpanel MCP server bug, or - an issue in Cursor’s MCP client / mcp-remote / local environment (the error string looks like a client‑side logging problem, but this is not documented).Documented next steps for MCP issues are generic: ensure Node is installed, re‑run authorization, and restart the desktop app.[MCP troubleshooting] There is no official workaround or configuration change in the docs for your specific error.Given the lack of coverage in the knowledge sources, the best documented guidance I can offer is: - Double‑check you followed the Cursor setup and OAuth flow exactly as described in the MCP “Option 3: Cursor” section (including data residency URL, scopes, and mcpServers config).[MCP implementation] - If the problem persists, this specific error is not documented; you’ll likely need to contact Mixpanel support or your CSM and reference the MCP beta docs and your environment (Cursor + MCP + mcp-remote), since MCP is explicitly in beta.[MCP overview]So: this exact error is not listed as a known MCP backend issue in the docs, and no official workaround is documented.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Kasper W.
·
·
FYI. This works again