MCP and OAuth2¶
Connect the AI client to https://elo-api-prod.quaggamock.com/mcp using MCP HTTP transport and OAuth2 with S256 PKCE. Start a fresh authorization, sign in, consent and complete the callback.
| Resource | Endpoint |
|---|---|
| Server | /mcp |
| Authorize | /oauth/authorize |
| Exchange/refresh token | /oauth/token |
| Dynamic registration | /oauth/register |
Prefer the client's OAuth/MCP discovery. Scopes: meetings:read and, if granted, offline_access. Never reuse consumed callbacks or authorization codes.
| Tool | Input | Result |
|---|---|---|
list_meetings |
{} |
Up to 100 meetings, including tags: [{id,name,description}] |
get_transcript |
UUID meetingId |
Authorized transcript, chat and notes |
ask_meeting |
UUID meetingId, question (3–2000 chars) |
Meeting-context answer |
list_meetings has no MCP cursor in this version. get_transcript is distinct from the paginated plugin API. Use transcript:read for incremental external UI reads.
MCP OAuth tokens are not plugin grants and must not go to iframes. There is no shared static API key. Each authorization belongs to the consenting user and client.