Connecting your AI
OAuth and supported AI clients
Updated 2026-08-13
Granova uses OAuth 2.1. Start at /connect, approve once in your AI client, and the connection covers every expert.
What works today
Recommended: claude, cursor, codex. These are verified end-to-end. Claude is the one-tap path on mobile and desktop. Cursor and Codex need a desktop app.
What “coming soon” means
chatgpt is listed as coming soon. The client's custom-connector UI supports OAuth in principle, but we haven't verified the full flow end-to-end. We don't list a client as live until it works for a real user, not just in our own tests.
Why OAuth, not a pasted key
OAuth means you approve Granova in your AI client's own settings. On the live path you never paste a key into a config file. The connection revokes cleanly from the client side.
Manual and advanced setup
Bearer key paste is advanced/manual only. If the one-click Connect button failed or you prefer a static config, see /setup.
Still stuck? Email support@granova.ai or use the contact form.
Related
Connect Granova to Claude
Connect Granova to claude.ai, Claude Desktop, or Claude mobile. One account-based link covers every expert.
Connect Granova to Cursor
Add Granova to Cursor with one deeplink. Cursor supports remote MCP and auto-discovers OAuth.
Connect Granova to Codex
Codex CLI connects to remote MCP servers directly. One terminal command, no bridge.
Troubleshooting connections and answers
Tools not appearing, 401 on refresh, agent won't call tools, or an answer that feels generic. The common cases and the fix for each.