Can My Agent Uselookup · compare · cite

Aug 28, 2026 · Catalog foundation is up

Specification feature · interfaces

MCP OAuth authorizationMCP 2026-07-28

Complete the MCP authorization flow for protected remote servers.

Terminology basis: MCP 2026-07-28. MCP 2026-07-28

MCP OAuth authorization: 5 supported, 1 partial, 0 unsupported, 25 unreviewed across 31 cataloged products.

Markdown · JSON

Explore this familyMore in Model Context Protocol23 capabilities

Current evidence by product

Can my agent use MCP OAuth authorization?

Read across for the answer. 6 of 31 current product columns have reviewed evidence; unreviewed does not mean unsupported.

Known issues (0)Report an issue
  • Supported5
  • Partial1
  • Unsupported0
  • Unknown25
  • Not applicable0

Web

9 products

Desktop

13 products
ClineCline
Y4Supported
Docs checked 2026-08-28Current · 1 condition
?Unknown
No source reviewedPreview record
Report this result

CLI

9 products

Unknown means no public evidence has been reviewed for that product and capability. It does not mean unsupported.

How statuses are assigned

Definition and scope

What this capability means

Complete the MCP authorization flow for protected remote servers.

This row remains unknown for a product until exact, dated evidence covers this capability rather than MCP generally.

Traceable compatibility

Assertion ledger

Documentation evidence only. No runtime conformance test is implied.

Claude CLIcli · current
Supported
Target
current Claude Code MCP documentation · dated-documentation
Environment
local-default
Observed
2026-08-28
  • authOAuth applies to HTTP servers and requires a server-compatible redirect and client-registration flow
Evidence
Cursordesktop · current
Supported
Target
current Cursor MCP documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • authremote servers may use dynamic registration or configured static credentials, and redirect URLs differ between web/agents and desktop surfaces
Evidence
Gemini CLIcli · current
Supported
Target
Gemini CLI MCP documentation updated 2026-06-18 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • authbrowser-based OAuth requires local callback access; headless, remote SSH, and container environments need an alternative authentication arrangement
Evidence
Continuedesktop · current
Partial
Target
Continue source commit 5522c6f44ca0 observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportthe reviewed desktop connection path limits native MCP OAuth handling to legacy SSE servers
  • autha browser callback is required; API keys and configured headers are separate authentication paths
Evidence
Zed Agentdesktop · current
Supported
Target
current Zed MCP documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • authautomatic OAuth prompting applies when a remote server has no configured Authorization header
Evidence
  1. 1. Evidence checked 2026-08-28: Claude Code documents browser-based OAuth for remote HTTP MCP servers, secure token storage and refresh, revocation, callback recovery, and fixed callback-port or preconfigured-client options.
  2. 2. Evidence checked 2026-08-28: Gemini CLI documents OAuth 2.0 for remote SSE and HTTP MCP servers, automatic discovery, browser authorization, token storage and refresh, and `/mcp auth` management.
  3. 3. Evidence checked 2026-08-28: Cursor documents OAuth for remote MCP servers, dynamic or static client registration, fixed redirect URLs, and CLI login with automatic callback handling.
  4. 4. Evidence checked 2026-08-28: Cline's pinned desktop implementation performs MCP OAuth discovery, client registration, browser authorization, callback validation, code exchange, token storage, and refresh for remote SSE and Streamable HTTP servers.
  5. 5. Evidence checked 2026-08-28: Continue's pinned desktop implementation includes the MCP OAuth authorization-code flow, but its connection path states that native OAuth is currently supported only for the legacy SSE transport.
  6. 6. Evidence checked 2026-08-28: Zed documents prompting the user through the standard MCP OAuth flow when a remote server has no configured Authorization header.