Other Agents

Generic Ternary MCP connection details for Zed, Goose, and other remote MCP clients that support Streamable HTTP and browser OAuth.

See Supported AI assistants for the current compatibility list.

Requirements

Your client must support:

• Remote MCP servers
• Streamable HTTP
• Browser-based OAuth

If the client only supports API keys or bearer tokens and cannot open a browser sign-in flow, it cannot currently connect to Ternary MCP.

Connection details

Choose the server that matches the region where your Ternary tenant is hosted.

US and EU accounts are separate. A US user cannot authenticate against the EU MCP URL, and vice versa.

Connect

Your client's terminology may differ, but the flow is generally:

1. Add a new remote MCP server.
2. Enter the Ternary MCP URL for your region.
3. Choose OAuth authentication if the client asks.
4. Leave client ID and client secret empty unless the client requires a client ID.
5. Start the connection.
6. Sign in to Ternary in the browser window that opens.
7. Approve access.
8. Return to your AI client and verify that the Ternary tools are available.

If your client asks for an OAuth client ID

Use:

https://core-api.ternary.app/oauth/client-metadata.json

Do not enter a client secret.

The same client ID is used for US and EU accounts. Only the MCP server URL changes by region.

If the approval page identifies the requester as an IDE coding agent and shows a local address, approve it only if you initiated the connection yourself.

If your client is not supported

For security, Ternary only accepts sign-in from recognized AI clients.

If your client is refused, contact Ternary Support and include:

• The client name
• Its version
• A link to its MCP documentation

Verify the connection

After authentication, make sure Ternary tools are enabled in your client.

Try:

Using Ternary, which tenants can I access?

Then:

Show last month's spend by provider.

Troubleshooting

See Troubleshooting Ternary MCP for more.