Document named MCP OAuth clients and cache migration - #625
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
There was a problem hiding this comment.
Risk assessment: Very Low
This pull request changes five Mintlify reference pages under reference/mcp-server/clients/ (Antigravity, Claude, Goose, Windsurf, and Zed). The diff is documentation only: setup copy, example mcp-remote arguments (--static-oauth-client-metadata), and example MCP_REMOTE_CONFIG_DIR cache paths.
- No application code, docs-site config, infrastructure, or authentication implementation changed.
- Blast radius is the published client setup guides.
- The diff is small (+33 / −11) and limited to those pages.
Approving because this is a documentation-only change with no production logic or shared-system impact. Code owner review is not required on main.
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Risk assessment: Very Low
Re-checked this pull request after the latest commit (Document separate MCP OAuth callback ports). Risk is unchanged from the earlier approval.
The full diff is still five Mintlify reference pages under reference/mcp-server/clients/ (Antigravity, Claude, Goose, Windsurf, and Zed). The update only adds example OAuth callback ports (46093–46097) and matching setup copy to those pages.
- No application code, docs-site config, infrastructure, or authentication implementation changed.
- Blast radius is the published client setup guides.
- The diff is small (+40 / −11) and limited to those pages.
Existing approval stands. No code owner file applies to these paths, so code owner review is not required.
Sent by Cursor Automation: Assign PR reviewers
masnwilliams
left a comment
There was a problem hiding this comment.
Reviewed the client-specific OAuth examples and migration guidance. No blocking quality findings. Please merge the matching CLI change before publishing these instructions. Non-blocking follow-up: narrow the existing troubleshooting instruction that clears ~/.mcp-auth, since it also removes the new per-client caches.
There was a problem hiding this comment.
Risk assessment: Very Low
Re-checked this pull request after docs(mcp): clarify manual OAuth setup before CLI defaults (0704e44). Risk is unchanged from the earlier approval.
The full diff is still five Mintlify reference pages under reference/mcp-server/clients/ (Antigravity, Claude, Goose, Windsurf, and Zed). The new commit only rewords those pages: it tells readers to compare a CLI-installed entry with the manual example, and it drops claims that the latest CLI automatically assigns a per-client auth cache.
- No application code, docs-site config, infrastructure, or authentication implementation changed.
- Blast radius is the published client setup guides.
- The diff is small (+47 / −12) and limited to those pages.
- No
CODEOWNERSfile applies to these paths, so code owner review is not required.
Existing approval stands. Not approving again.
Sent by Cursor Automation: Assign PR reviewers


Summary
Validation
The manual setup instructions work with the current CLI and remain valid when per-client defaults ship.
Note
Low Risk
Documentation-only changes to MCP client setup guides with no runtime or security logic changes.
Overview
Updates MCP client setup docs so manual and CLI-assisted installs show the full
mcp-remoteOAuth pattern: per-client callback ports (e.g.46093–46097),--static-oauth-client-metadataso consent shows the real client name instead of MCP CLI Proxy, and a dedicatedMCP_REMOTE_CONFIG_DIRso multiple tools can authorize in parallel without sharing tokens.Antigravity, Windsurf, and Zed JSON examples gain port, metadata, and
envblocks plus post-install checks against CLI output. Goose updates Desktop/CLI commands, thegoose://install link, and CLI YAML guidance. Claude adds a Configure Claude Desktop with mcp-remote section for users who installed viakernel mcp install --target claude.Each page documents cache migration: close the app, delete the old
mcp-remote-v1cache (default or under a custom dir), and reauthorize—noting that clearing a shared cache signs out other clients using it.Reviewed by Cursor Bugbot for commit 0704e44. Bugbot is set up for automated code reviews on this repo. Configure here.