// docs / integrations

OAuth MCP

Recommended. Point Claude Desktop, Cursor, or any remote MCP client at primeta.ai/mcp — OAuth handles auth.

The recommended way to connect a remote MCP client like Claude Desktop or Cursor to Primeta. No API key needed — the client handles authentication via browser OAuth.

When to use this

  • Your client supports remote MCP servers (Claude Desktop, Cursor, Zed, etc.)
  • You want the simplest possible setup (copy a URL, log in once)
  • You don't need the bridge-token flow for a local coding agent

Setup

  1. Add https://primeta.ai/mcp as an MCP server in your client. For clients with a JSON config, drop in: json { "mcpServers": { "primeta": { "type": "http", "url": "https://primeta.ai/mcp" } } }
  2. The first time you connect, the client opens a browser window. Log in to Primeta; the client stores the token.
  3. You're connected. Your MCP client can now call primeta_send, primeta_set_persona, primeta_list_personas, and the other tools documented in the full MCP reference.

The full setup page with click-to-copy URLs is at bridge setup — pick the OAuth tab.

What you get

Once connected, your MCP client's responses are spoken through your chosen Primeta persona's avatar and voice. The avatar reacts with emotion tags and animations as the model generates text.

OAuth MCP creates an MCP session, not a channel. Both kinds of connection show as cards on your dashboard — see sessions, connections, conversations for the distinction.