docs: sync ADP changes from cloudv2 (2026-06-13)

[micheleRP]

What changed

Synced one user-facing ADP change from cloudv2 main (last 24h) into the docs.

Well-known OAuth client catalog expanded (5 → 9)

Source: redpanda-data/cloudv2@913e51daf — feat(adp): server-supplied docs urls and wider wellknown client catalog (author: @malinskibeniamin)

The "Register Client" catalog of well-known OAuth clients grew from 5 to 9. The commit adds four presets, each with first-party-cited redirect URIs:

Client	Redirect URIs (from source)	Notes
Visual Studio Code	https://vscode.dev/redirect, http://127.0.0.1:33418	Also covers GitHub Copilot in VS Code
Zed	http://127.0.0.1/callback
Gemini CLI	http://localhost:7777/oauth/callback	The CLI, distinct from the consumer Gemini apps
mcp-remote bridge	http://localhost:3334/oauth/callback	stdio-to-HTTP bridge for clients without native remote OAuth

Updated modules/connect/pages/remote-mcp-clients.adoc:

• Expanded the catalog enumeration where the "Register Client" step lists the prefilled clients.
• Expanded the preset list in "Wire up other chat clients" and added a short bullet per new preset (disambiguating Gemini CLI from the consumer Gemini apps).

Deploy preview

https://deploy-preview-100--redpanda-agentic-data-plane.netlify.app/agentic-data-plane/connect/remote-mcp-clients/

(404s until Netlify finishes the preview build.)

Considered but not documented

These cloudv2 changes were reviewed and intentionally left out of this PR:

• 318f512e6 (@WesWWagner) — feat(aigw/odata): deep-insert create via nested navigation properties. Enhances the OData managed MCP server's create tool. TODO for human review: the OData managed MCP server is not currently documented in adp-docs (no page, not in the managed catalog). Documenting it requires a new page plus a maturity-tier decision per the maturity-status policy — flagging for Michele / the docs team rather than creating one speculatively.
• 3d9591961 (@johnkennedy-cmyk) — fix(aigw): route Jira MCP user-OAuth through Atlassian API gateway. Internal request-routing fix (resolves the Atlassian cloud ID behind api.atlassian.com); transparent to users, no new config field. No doc change.
• 2fb693c10 (@simon0191) — fix(aigw): surface outputSchema and structuredContent on managed MCP wire. Wire-level correctness fix to match MCP spec 2025-06-18; no user-facing config/API surface change. No doc change.
• 639a1f104 (@simon0191) — rpai: add --spec-file to agent create. Adds a CLI flag to create a managed agent (incl. subagents/agent_card) from a JSON/YAML spec file. TODO for human review: subagents are already documented for the UI create form; it's unclear whether this flag is surfaced in the published rpk ai CLI vs. internal rpai, and it landed alongside a customer PoC. Flagging rather than documenting a possibly-internal CLI surface.

Reviewers

Added @malinskibeniamin as an optional reviewer for a source-accuracy check on the catalog change. Their approval is not blocking.

🤖 Generated with Claude Code

https://claude.ai/code/session_014sr3bghMVna1jX8jgufrVU

[netlify]

✅ Deploy Preview for redpanda-agentic-data-plane ready!

Name	Link
🔨 Latest commit	dcef9dc
🔍 Latest deploy log	https://app.netlify.com/projects/redpanda-agentic-data-plane/deploys/6a2d47bd7848ca0008f50371
😎 Deploy Preview	https://deploy-preview-100--redpanda-agentic-data-plane.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[micheleRP]

[adp-docs PR critic] Verdict: looks accurate against the source. Reviewed the diff in modules/connect/pages/remote-mcp-clients.adoc against cloudv2 and found no issues.

Source accuracy — verified (all match): cloudv2 apps/aigw/internal/idp/wellknown.go (and the pinning test apps/aigw/internal/idp/wellknown_test.go).

• The catalog has exactly 9 entries — prior 5 (claude-ai, claude-desktop, chatgpt, cursor, windsurf) plus the 4 new ones — confirming the 5→9 claim.
• Visual Studio Code — source Description: "Visual Studio Code with built-in MCP support (also covers GitHub Copilot in VS Code)." The PR's "(which also covers GitHub Copilot in VS Code)" is verbatim. Redirect URIs https://vscode.dev/redirect, http://127.0.0.1:33418 match.
• Zed — http://127.0.0.1/callback, "remote MCP server OAuth support" matches.
• Gemini CLI — http://localhost:7777/oauth/callback; source notes it is the CLI (Id: gemini-cli, homepage github.com/google-gemini/gemini-cli), so "the command-line tool, distinct from the consumer Gemini apps" is accurate.
• mcp-remote bridge — DisplayName: "mcp-remote bridge", http://localhost:3334/oauth/callback, "stdio-to-HTTP bridge for MCP clients without native remote OAuth support" matches the source Description.

Robustness note (not a defect): the doc describes that the presets prefill redirect URIs but does not hardcode the URI strings into the prose, so there's no stale-value drift risk if a vendor changes theirs. Good call.

Policy: the maturity-status rule doesn't apply here (these are OAuth client presets, not managed MCP servers). The "Considered but not documented" section correctly flags the OData server (needs a page + maturity decision) and the rpai --spec-file flag (possibly-internal CLI) for human review rather than acting on them — consistent with the repo's HARD RULEs.

No Critical, Suggestion, or Minor findings.

---

Generated by Claude Code