Ternary MCP for other agents

Claude, ChatGPT and VS Code have their own setup guides: Connect Claude, Connect ChatGPT/Codex, Connect Visual Studio Code.

Every other agent follows the same pattern. Your agent asks for a remote MCP server; you give it the Ternary URL; it opens a Ternary sign-in page. Each agent words its own setup differently and changes it often, so follow your agent's own MCP documentation for where to paste the URL, and use the details below for what to paste.

What to give your agent

Setting	Value
Transport	Streamable HTTP (not SSE)
Server URL, US (`my.ternary.app`)	`https://core-api.ternary.app/mcp`
Server URL, EU (`my.eu.ternary.app`)	`https://core-api.eu.ternary.app/mcp`
Authentication	OAuth. Leave any client ID or secret field empty.

Use the URL for the region where your Ternary tenant lives. US and EU are separate: a US account cannot sign in against the EU URL.

❗️
Type the URL exactly, with no trailing slash
Some agents treat .../mcp/ as a different server from .../mcp and sign-in then fails with "Unknown client".

Your agent then opens a Ternary sign-in page. Log in with your normal Ternary credentials and approve the access request. Every tool runs as you, with exactly your permissions, and all of them are read-only.

Supported agents

For security, Ternary only accepts sign-in from AI tools it recognises. An agent that is not approved is refused even with the correct URL and a valid account.

Agent	Status
Claude (web, desktop)	Supported — guide
Claude Code	Supported — guide
ChatGPT	Supported — guide
OpenAI Codex	Supported — guide
Visual Studio Code (GitHub Copilot)	Supported — guide
Zed	Supported
Goose	Supported
Cursor	Planned
Cline	Planned
Gemini CLI	Planned
Kiro	Planned
OpenCode	Planned
Windsurf / Devin	Under review
Google Antigravity	Under review
Visual Studio	Under review

Agents marked Planned need one extra step that Ternary is preparing, and this page will carry it once ready. Agents marked Under review are being assessed for compatibility.

Some tools cannot connect at all today, because they do not support the sign-in method Ternary requires. That is a limitation of the tool, not of your account. If your agent offers only an API key or bearer-token field and no browser sign-in, it falls into this group.

If your agent is not listed

Contact Ternary support and tell us which agent you want to use. Adding one is usually a small change on our side, and knowing which tools customers actually use is how we prioritise. Include the agent's name and version, and a link to its MCP documentation if you have it.

Troubleshooting

"Unknown client", or sign-in is refused — the agent is not on the supported list above, or the URL has a typo or a trailing slash.
Sign-in fails or loops — your email must already be a Ternary user in that region. The connection does not create accounts.
"No tenants found" — your Ternary user has no explicit role on any tenant. Ask your Ternary admin to grant you one.
The agent connects but never uses Ternary — check its Ternary tools are enabled for the current conversation, and name Ternary in your question.