GRO-107: Update MCP docs to recommend direct connection - #104
Open
myronkaifung with Copilot wants to merge 3 commits into
Open
GRO-107: Update MCP docs to recommend direct connection#104myronkaifung with Copilot wants to merge 3 commits into
myronkaifung with Copilot wants to merge 3 commits into
Conversation
…d Gemini CLI - Cursor OAuth: use direct `url` format instead of `npx mcp-remote` - Gemini CLI OAuth: use `--transport http` and `httpUrl` instead of `npx mcp-remote` - Gemini CLI Service Accounts: use `--transport http --header` and `httpUrl`/`headers` instead of mcp-remote with stdio args Fixes https://linear.app/mixpanel/issue/GRO-107/update-mcp-docs-to-recommend-direct-connection
Copilot
AI
changed the title
[WIP] Update MCP docs to recommend direct connection
GRO-107: Update MCP docs to recommend direct connection
Jul 17, 2026
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
myronkaifung
marked this pull request as ready for review
July 28, 2026 23:15
myronkaifung
enabled auto-merge (squash)
July 28, 2026 23:17
myronkaifung
approved these changes
Jul 28, 2026
Contributor
Confidence Score: 3/5The invalid Gemini service-account authorization examples need to be corrected before merging. Both changed Gemini examples instruct users to send Files Needing Attention: docs/mcp.mdx
|
| Filename | Overview |
|---|---|
| docs/mcp.mdx | Converts Cursor and Gemini examples to direct HTTP, but the Gemini service-account headers no longer contain the required authorization scheme. |
Reviews (1): Last reviewed commit: "Merge branch 'main' into copilot/gro-107..." | Re-trigger Greptile
myronkaifung
disabled auto-merge
July 28, 2026 23:17
myronkaifung
enabled auto-merge (squash)
July 28, 2026 23:19
myronkaifung
disabled auto-merge
July 28, 2026 23:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs for Cursor (OAuth) and Gemini CLI (OAuth + Service Accounts) were recommending
npx mcp-remoteas a stdio proxy. Both clients now support native HTTP transport, so the proxy is unnecessary.Changes
command/argsmcp-remote config with directurlfield (consistent with the existing Cursor Service Accounts config)gemini mcp add mixpanel npx -y mcp-remote ...withgemini mcp add --transport http ...; settings.json useshttpUrlinstead ofcommand/argsenv-based header injection with--transport http --headerCLI flag andhttpUrl/headersin settings.jsonBefore (Cursor OAuth):
{ "mcpServers": { "mixpanel": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.mixpanel.com/mcp"] } } }After:
{ "mcpServers": { "mixpanel": { "url": "https://mcp.mixpanel.com/mcp" } } }The
mcp-remotereference in the "Building Custom Integrations" section is intentionally preserved — it remains relevant for developers building custom OAuth clients.