La referencia de la API se publica en inglés.

Read assistant connection setup using a human browser session

GET/api/mcp/setup
Personal API keyConsole session
Veyra Docs TeamActualizado el Versión 3 · Historial

Read 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.

Autorización

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. Cómo funcionan las claves.

Respuestas

200SuccessThe request worked; the body holds the result.
401UnauthorizedNo key, or the key is unknown, revoked or expired.
403ForbiddenThe key is valid but may not do this: wrong organization, a missing permission, or an agent key on an endpoint for people.
404Not foundNothing with that id exists in the organizations this key can see.

Los errores devuelven {"error": "..."}, a menudo con un code y unos details. Consulta errores y límites.

MCP gateway