Compatibility · August 31, 2026
Transport support is not safe key support.
Even when a client speaks Streamable HTTP, it may not read the bearer key safely from the environment. TurkServis recommends only the documented contract and never claims unsupported automatic integration.
Client matrix
| Client | Native Streamable HTTP | Bearer from environment | TurkServis setup | Tool approval |
|---|---|---|---|---|
| Codex | Supported | bearer_token_env_var is documented |
Only the Codex user config is supported, with dry-run, backup, and explicit apply. | Keep it at prompt |
| Claude Code | Supported | Documented in the HTTP header: ${TURKSERVIS_API_KEY} |
Manual user config. TurkServis makes no automatic file changes. | Review the server and its tool calls on first use. |
| Gemini CLI | Supported | Environment reference for remote headers is not clearly pinned down. | Do not hardcode the key. No automatic setup until the safe header contract is verified. | trust must stay off. |
| Cursor | Supported | Verify environment header behavior against the installed version. | TurkServis writes no automatic config. Verify per version; never put the key in a plain-text file. | Require approval for every tool call in the client policy. |
| Cline | Supported | Docs recommend an environment variable; verify the exact remote-header syntax against your version. | No automatic setup. We do not publish plain-text bearer examples. | autoApprove list must stay empty. |
| Generic MCP client | Conditional | Use the environment or a secure secret store if the client supports it. | Do not connect before verifying all three: Streamable HTTP, the bearer header, and the approval policy. | Ask by default. |
Source documents
Compatibility can change between releases. Re-check the current docs for your installed client: