Read assistant connection setup using a human browser session
/api/mcp/setupRead assistant connection setup using a human browser session.
Person-only: a person connects their own assistant, such as Claude, ChatGPT or another MCP client, in their browser on Assistant connections, with this conversation's organization prefix as . That page gives the invitation and server URL to paste into the assistant; the assistant then opens a Veyra Intelligence consent screen where the person picks the organization and approves access. The consent screen offers only access within that person's own role: a read-only member can grant read access but not writes. An agent cannot read this setup or approve consent for anyone: these routes accept only the person's own signed-in browser session. Do not search for another route; link that page, say the person approves access there themselves, and reply.
Authorization
Send a personal API key as Authorization: Bearer <key>. It acts as you, with your permissions in each organization. Agent API keys are refused with 403. How keys work.
Responses
Errors return {"error": "..."}, often with a code and details. See errors and limits.