Google OAuth

Some clients — currently, Claude Desktop and Claude.ai's "Add custom connector" flow — speak the full MCP authorization spec: they can discover that Cohearence is an OAuth-protected server and register themselves automatically, so you never have to generate or paste a token at all.

Cohearence currently supports signing in with Google, so this flow signs you in with the same Google account you use for Cohearence itself.

Connecting Claude

1. In Claude, open Settings → Connectors → Add custom connector.
2. Enter your Cohearence MCP URL (the same one shown on the Connect AI screen in the app).
3. Claude redirects you to Google to sign in and approve access.
4. Once approved, Claude holds a refresh token on your behalf — no secret for you to manage.

If you signed in to Cohearence with the same Google account on mobile, this resolves to the exact same account — your data is unified across both, not split into a second identity.

Disconnecting

Remove the connector from Claude's settings at any time, or revoke Cohearence's access from your Google Account permissions — either one immediately cuts off access.

When this doesn't apply

Most MCP clients today (Cursor, Claude Code, and most agent frameworks) don't yet implement the full connector/OAuth flow — they expect a static URL and header instead. For those, use a Personal Access Token.