Connect your assistant

Ontyx is a remote MCP server. Most assistants can connect to it directly over the web — you sign in with your Ontyx account in a browser window, approve access, and the tools appear in your conversation. No API key, no config file, no install.

The server URL is:

https://mcp.ontyx.io/mcp

Two ways to authenticate

Both reach the same tools and draw on the same monthly credits. If your assistant offers a connector UI, prefer it — nothing secret ends up in a config file, and you can revoke access from your dashboard.

For the API-key route, see Installation and Authentication.

Before you start

You need an Ontyx account, and it must have accepted the current Terms of Service.

If you have never used Ontyx before, you’ll create an account during the connection flow and accept the terms as part of signing up — nothing extra to do.

If you already have an account, sign in at ontyx.io/legal/accept and accept once. Signing in doesn’t re-prompt for terms the way signing up does, so existing accounts need this step. Until it’s done, tool calls return:

TERMS_ACCEPTANCE_REQUIRED

Your assistant will show that message along with the link. Accept, then ask again — you don’t need to reconnect.

Claude

Add the connector from the web portal at claude.ai — not from the iOS or Android app. The mobile apps can use a connector once it exists, but they have no screen for adding a custom one. A mobile browser works fine; it’s the native app that can’t do it.

1. Go to claude.ai and open Settings → Connectors.
2. Click Add custom connector.
3. Paste the server URL:

   https://mcp.ontyx.io/mcp
   The bare hostname (https://mcp.ontyx.io) also works if you leave the path off.
4. Click Add. A browser window opens for Ontyx sign-in.
5. Sign in and approve access.

Once added, the connector syncs to your account, so it’s available in the mobile apps and Claude Desktop too. Try: “What’s the population of zip code 94110?”

Claude Code can also use an API key via its JSON config, which is often easier for headless or scripted use — see Installation.

ChatGPT

Requires a paid plan (Plus, Pro, Business, Enterprise, or Edu) and developer mode.

1. Open Settings → Security and login and turn on Developer mode. On Business/Enterprise/Edu, a workspace admin must enable it first under Workspace Settings → Permissions & Roles.
2. Go to your apps/connectors settings and create a new developer-mode app.
3. Enter https://mcp.ontyx.io/mcp — include the /mcp path.
4. Create the connection and complete the Ontyx sign-in when prompted.
5. Review the discovered tools and enable the ones you want.

New connectors appear under Drafts until you enable them.

Grok

Requires a paid Grok plan.

1. Go to grok.com/connectors.
2. Click New Connector, then choose Custom.
3. Enter https://mcp.ontyx.io/mcp.
4. Complete the Ontyx sign-in when prompted.

Grok discovers the tool list and makes it available in conversations alongside its built-in connectors.

Gemini

Support depends on which Gemini you use, and the consumer app is the weakest case:

• Gemini Enterprise — supported. An administrator registers Ontyx as a custom MCP server (Streamable HTTP with OAuth 2.0) in your tenant. See Google’s custom MCP server documentation.
• Gemini CLI — can reach remote MCP servers, though OAuth support has been uneven; you may need the mcp-remote bridge.
• Consumer Gemini app — not currently self-serve. Connectors there are partnership-only, so you cannot add Ontyx yourself today. Use an API key with a different client, or one of the assistants above.

Other MCP clients

Ontyx is a standard OAuth-protected Streamable HTTP MCP server, so it works with any compliant client. Known-good surfaces include VS Code with GitHub Copilot, Cursor, Zed, Amazon Q Developer CLI, and the Docker MCP Toolkit. Point them at https://mcp.ontyx.io/mcp and follow their remote-server instructions.

Clients that support remote URLs but not OAuth (some older builds of Windsurf, Cline, Continue.dev) can use the mcp-remote bridge, or an API key instead.

Managing access

• See what you’ve connected — the OAuth consent step is per-account; revoke from your dashboard.
• Revoking an API key or a connector affects only that credential. The others keep working.
• Usage from every connection — connector or key — is metered against the same monthly credits. See Usage.

Troubleshooting

“Terms acceptance required.” Your account hasn’t accepted the current terms. Go to /legal/accept, sign in, accept, then retry. No reconnection needed.

“Couldn’t register with Ontyx’s sign-in service.” Check that you’re adding the connector from the claude.ai web portal rather than the mobile app. If it still fails, wait a minute and press Connect again — the same message also covers transient discovery failures.

Connected, but the assistant says it has no Ontyx tools. Remove and re-add the connector. If your assistant reports the connection as healthy but a tool search comes back empty, it usually means discovery completed against a URL that doesn’t serve the tool list; re-adding with https://mcp.ontyx.io/mcp is the reliable fix.

No “Add custom connector” option anywhere. You’re likely in the mobile app. Custom connectors can only be added from the web portal — open claude.ai in a browser instead.

The connector adds but no tools appear. Your assistant may not have finished discovery. Remove and re-add the connector; if it persists, confirm your client supports Streamable HTTP remote MCP servers rather than only local stdio ones.

Sign-in opens but never completes. Check that pop-ups aren’t blocked, and that you’re signing in to the account you expect — if you have several, the consent screen shows which one.

Everything worked, then stopped. You may have exhausted your monthly credits; free-tier calls stop until the month resets. Check Usage.

Next steps

• Available Tools — the full tool list and parameters
• Quickstart — your first query and how credits work