Update MCP docs to reflect current OAuth MCP support for cloud agents

[warp-agent-staging]

Summary

Updates the MCP docs to accurately describe OAuth authentication support for cloud agents (Oz), replacing the previous blanket "OAuth is not supported" claims.

Verified against warpdotdev/warp-server (read-only, no server PR needed):

• oauth_managed_remote_mcp_enabled: true in config/prod.yaml — managed MCP installations (create → authorize via OAuth → reference by warp_id) are live in production, including the "Managed MCP servers" section on the Oz web app's Integrations page (VITE_FEATURE_MANAGED_MCP=true in client/packages/agents/.env.production).
• allow_oauth_in_ambient_mcp: false in config/prod.yaml — a direct url MCP config that requires OAuth and has no Authorization header is still rejected at dispatch (logic/ai/ambient_agents/mcp/mcp_validation.go): "mcp server %q requires OAuth, which is not currently supported in ambient agents".
• Managed installs referenced via warp_id are accepted when visible and ACTIVE under oauth_managed_remote_mcp_enabled (same file, ValidateManagedMCPServersForDispatch).

Changes

• platform/mcp.mdx — added an OAuth authentication section describing the managed-MCP-installation path, updated the warp_id schema description, and rewrote the Limitations caution to name the precise remaining gap (a raw url OAuth config with no pre-supplied credentials).
• guides/external-tools/using-mcp-servers-with-warp.mdx — updated the matching cloud-MCP caution for consistency and linked to the new OAuth authentication section.
• Reviewed reference/cli/mcp-servers.mdx and agents/capabilities/mcp.mdx for consistency — neither made a false claim about cloud OAuth support, so no changes were needed there.

Verification

Docs-only change — testing-exempt category pure data/copy (no application code changed).

• npm run build — full Starlight build succeeds (364 pages).
• python3 .agents/skills/check_for_broken_links/check_links.py --internal-only — 3487 internal links checked, 0 broken (including the new #oauth-authentication and #integrations anchors).
• python3 .agents/skills/style_lint/style_lint.py --changed — no new style issues introduced (pre-existing hardcoded-var/unrecognized-term warnings in the guide predate this change).

Originating thread: https://warpdev.slack.com/archives/C09BVK0PL3Y/p1786488521102829

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 11, 2026 11:10pm

[oz-for-oss]

@warp-agent-staging[bot]

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

Overview

This docs-only PR updates MCP cloud-agent guidance to distinguish direct url OAuth configs from managed OAuth MCP installations referenced by warp_id. The changed content uses the docs variable system for the Oz web app name and keeps the guide and platform reference consistent.

Concerns

• No blocking concerns found in the changed lines.
• No security findings were identified in this docs-only diff.
• spec_context.md states no approved or repository spec was found, so there was no implementation/spec drift to evaluate.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz