oauth_support
Whether the provider supports OAuth 2.0 authentication for remote MCP servers, including token storage and automatic refresh.
Type: bool Content type: mcp
Provider Support
Section titled “Provider Support”| Provider | Supported | Mechanism |
|---|---|---|
| amp | ✓ | oauth_support: Amp supports OAuth 2.0 authentication for remote MCP servers |
| claude-code | ✓ | mcp_oauth_authentication: OAuth 2.0 for HTTP MCP servers; dynamic client registration; token storage in macOS keychain or credentials file; auto-refresh |
| codex | ✓ | mcp_oauth_support: Codex supports OAuth 2.0 authentication for remote MCP servers |
| cline | ✗ | Cline MCP does not document OAuth 2.0 authentication for remote servers |
| copilot-cli | ✗ | Copilot CLI MCP does not document OAuth 2.0 authentication |
| crush | ✗ | Crush MCP does not document OAuth 2.0 authentication for remote servers |
| cursor | ✗ | Cursor's MCP documentation does not describe OAuth 2.0 flows for remote servers. |
| factory-droid | ✗ | Factory Droid MCP does not document OAuth 2.0 authentication |
| gemini-cli | ✗ | Gemini CLI MCP does not document OAuth 2.0 authentication for remote servers |
| kiro | ✗ | Kiro MCP does not document OAuth 2.0 authentication |
| opencode | ✗ | No OAuth 2.0 authentication for remote MCP servers documented |
| roo-code | ✗ | No OAuth 2.0 authentication flow documented for Roo Code MCP servers |
| windsurf | ✗ | Windsurf MCP does not document OAuth 2.0 authentication for remote servers |
| zed | ✗ | Zed MCP configuration does not document OAuth 2.0 authentication for MCP servers |