[warp-agent-staging]

Summary

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

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 — no changes needed there.

Verification

Docs-only change — testing-exempt category pure data/copy. Verified server-side that managed MCP installations are live for cloud agents and that a raw url config requiring OAuth with no pre-supplied credentials is still rejected at dispatch.

• npm run build — full Starlight build succeeds.
• npm run typecheck (astro check) — 0 errors.
• python3 .agents/skills/style_lint/style_lint.py --changed — no new style issues (pre-existing unrecognized-term warnings in the guide predate this change).
• Grepped the docs tree for residual "does not currently support OAuth" / "OAuth-based MCP servers are not currently supported" cloud-agent claims — none remain.

Rework changes

Editorial pass per requester feedback in Slack: tightened the OAuth authentication section and both Limitations/caution blocks for concision and a developer-docs voice, and trimmed this PR description to a short summary (moved server-side verification detail out of the description).

Review fix (rework cycle 1): addressed one ⚠️ [IMPORTANT] finding — the cloud-MCP caution in using-mcp-servers-with-warp.mdx implied every OAuth-gated raw url MCP server is unsupported. Restored the qualifier so it matches /platform/mcp/: unsupported only when the server requires OAuth and has no pre-supplied Authorization header. Managed-installation warp_id guidance is unchanged.

Merge-conflict repair (2026-08-26): main had moved substantially since this branch was cut (a docs-variable rollout added {VARS.WARP_AGENT_CLI} / {VARS.WEB_APP} / {VARS.WARP_AUTOMATION_PLATFORM} substitutions and a new Warp-managed integration-server (linear/slack/jira) feature to both target files), which made the branch DIRTY/CONFLICTING against the current base.

• Merged current main into this branch (no rebase, per policy) and resolved the two real conflicts in platform/mcp.mdx:
  • the transport table's warp_id row — combined the OAuth-managed-install wording with main's new "or a Warp-managed integration server by its id" wording into one row.
  • the warp_id bullet under Supported fields — combined the managed-MCP-installation phrasing with main's new integration-server id list into one bullet.
• using-mcp-servers-with-warp.mdx merged cleanly with no manual resolution needed.
• Re-grepped the full docs tree for residual "does not currently support OAuth" / "OAuth-based MCP servers are not currently supported" cloud-agent claims after the merge — none found; the support-matrix wording from the ticket's acceptance criteria now appears exactly once per page, with no contradictory or duplicated text.
• The resulting diff against main stays confined to the same two files (platform/mcp.mdx, guides/external-tools/using-mcp-servers-with-warp.mdx).
• Re-ran npm run build, npm run typecheck, and style_lint --changed after the merge — all pass (see Verification above).

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 26, 2026 10:39pm

[warp-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

[warp-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