What Are Custom Connectors?
In clients with Custom Connector support, you paste the MCP URL into the AI app settings and sign in through OAuth. That path does not require copying an API key. Other MCP clients can have different configuration and authentication capabilities.
Behind the scenes, Custom Connectors use the OAuth 2.1 protocol with PKCE. When you click "Add connector" in Claude.ai or ChatGPT, the AI app discovers our authorization endpoints automatically, opens a login page, and securely exchanges tokens. You never see or handle credentials.
How to Connect
IDE and CLI clients use the same Streamable HTTP endpoint, but their OAuth and header support varies by client version. Use OAuth when the client supports the discovery flow; otherwise use a scoped agent key and follow that client's remote-MCP configuration.
Security Built In
OAuth connector flows use authorization-code exchange with PKCE. Your Lite ASO password is entered only on the Lite ASO authorization page, and the client receives a resource-bound access token. Agent-key clients use a separate, scoped credential that can be revoked from the dashboard.
- PKCE (S256) prevents authorization code interception
- Tokens expire automatically and can be revoked
- CSRF protection on all authentication forms
- Rate limiting prevents brute force attacks
Connection Examples
Lite ASO exposes one Streamable HTTP endpoint and OAuth discovery for compatible, pre-registered clients. MCP 2026-07-28 clients may use a Client ID Metadata Document (CIMD); Dynamic Client Registration is disabled. A scoped agent key is available for clients that support remote MCP headers but not the OAuth flow. Client support still varies and is not guaranteed by discovery alone.
| AI Tool | Method | Auth |
|---|---|---|
| Claude.ai | Custom Connector | OAuth |
| ChatGPT | Custom Connector | OAuth |
| Claude Desktop | Remote MCP | OAuth or agent key |
| Claude Code | Remote MCP | OAuth or agent key |
| Cursor | Remote MCP | Client-dependent |
| VS Code Copilot | Remote MCP | Client-dependent |
| GitHub Copilot Agent | Remote MCP | Client-dependent |
| Gemini CLI | Remote MCP | OAuth or agent key |
| OpenAI Codex | Remote MCP | OAuth or agent key |
| Windsurf | Remote MCP | Agent key if supported |
| Cline | Remote MCP | Agent key if supported |
| Goose | Remote MCP | Client-dependent |
API Keys Still Work
If you prefer API keys — for local development, CI/CD pipelines, or tools that do not support OAuth yet — you can still generate an API key from the dashboard. The Connect AI Agent page now has two tabs: Custom Connector (recommended) and API Key. Both connect to the same MCP server with the same tools.