Supported clients

The CloudQuell MCP server is a standards-compliant remote MCP server over Streamable HTTP with OAuth 2.1 + PKCE. Any MCP client that supports remote HTTP servers and OAuth can connect. Claude (web and Desktop), Claude Code and ChatGPT are tested end to end; the other rows follow the same standard flow.

Client	How it connects	OAuth login	Notes
Claude (claude.ai / Claude.com)	Custom connector (remote MCP URL)	In-browser, built-in	Best experience. Tested.
Claude Desktop (macOS/Windows)	Custom connector, or mcp-remote bridge in claude_desktop_config.json	In-browser via connector, or mcp-remote opens a browser	Use the connector UI on current builds. Tested.
ChatGPT	Custom MCP server at chatgpt.com/plugins	In-browser, built-in	Subject to your ChatGPT plan and workspace settings. Tested.
Claude Code (CLI)	claude mcp add --transport http …	Opens a browser for OAuth	Great for scheduled / terminal workflows. Tested.
Cursor	mcp-remote bridge as a command server in mcp.json	mcp-remote opens a browser	Cursor’s built-in sign-in for remote servers isn’t supported yet; use the bridge.
Goose (Block)	Remote extension (Streamable HTTP)	Browser flow	Add via goose configure → Add Extension → Remote Extension.
Codex (OpenAI Codex CLI)	mcp-remote bridge in ~/.codex/config.toml	mcp-remote opens a browser	Codex speaks stdio; the bridge handles remote HTTP + OAuth.
Any MCP client	Point it at the MCP URL; it discovers OAuth automatically	Per client	The server publishes RFC 9728 / RFC 8414 discovery + a DCR /register shim, so compliant clients self-configure.

What “any MCP client” needs

A client works out-of-the-box if it supports:

1. Streamable HTTP transport (not just stdio). The server is stateless and replies with buffered JSON (no SSE).
2. OAuth 2.1 Authorization Code + PKCE (S256). The server advertises its discovery documents and a Dynamic Client Registration (/register) shim, so the client does not need a pre-issued client id or secret.

Clients that only speak stdio (or don’t yet do OAuth) can still connect through the mcp-remote bridge — a small local proxy that handles the OAuth dance and forwards JSON-RPC to the remote server. See Connecting for the exact snippet.

The endpoint

Use this URL in every client:

https://mcp.cloudquell.com/mcp

Continue to Connecting for step-by-step setup per client.