AI client compatibility

JamRelay exposes a remote MCP Streamable HTTP endpoint:

https://mcp.example.com/mcp

It supports two authentication families:

• MCP OAuth — recommended for clients with first-class OAuth support;
• static Bearer token — useful for debugging and clients that allow custom HTTP headers.

Multi-client OAuth

One deployment can serve multiple MCP clients through the static registry or Dynamic Client Registration (DCR).

Available registration paths:

multi-client static registry    ✅
Dynamic Client Registration     ✅
public OAuth clients            ✅
confidential OAuth clients      ✅
CIMD                            not advertised yet

See MCP OAuth registration for the registration model and current MCP-spec note about CIMD.

Compatibility matrix

Client	Remote Streamable HTTP	OAuth	Bearer/custom headers	Recommended JamRelay mode	Status
ChatGPT	✅	✅	custom-app UI is OAuth-oriented	static OAuth	previously verified
Codex CLI + Desktop	✅	✅	✅	DCR	protocol path implemented
Claude hosted surfaces	✅	✅	not primary connector path	DCR	protocol path implemented
Claude Code	✅	✅	dynamic headers also supported	DCR	protocol path implemented
Gemini CLI	✅	✅	✅	DCR	protocol path implemented
Cursor	✅	✅	✅	DCR or static OAuth	protocol path implemented
VS Code + Copilot	✅	✅	✅	DCR	protocol path implemented
Windsurf Cascade	✅	✅	✅	OAuth discovery / Bearer fallback	not yet verified end-to-end
MCP Inspector	✅	✅	✅	OAuth or Bearer	developer verification tool

“Protocol path implemented” means JamRelay now implements the registration/callback behavior documented by that vendor. It is not a certification that every current client build has been manually exercised against this exact release.

Test prompts

Read test:

What is currently playing on Spotify?

Write test:

Create a private playlist called MCP Test and add two tracks to it.

Client guides

• ChatGPT
• Codex CLI and Desktop
• Claude
• Gemini CLI
• Cursor
• VS Code + GitHub Copilot
• Windsurf Cascade
• MCP Inspector
• MCP OAuth registration

Last reviewed against vendor documentation: 2026-09-12.