read.ai
Read AI is an AI meeting intelligence platform that captures meeting transcripts, summaries, action items, and analytics. It helps users and teams access and act on meeting data from video conferencing and related workflows.
Read AI exposes two developer integration surfaces in open beta: a REST API at https://api.read.ai/ and a remote MCP server at https://api.read.ai/mcp; both use Read-issued OAuth 2.1 credentials and bearer access tokens.
- Read AI MCP serverdetected
- Read AI REST APIdiscovered
Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.
Obtain this bearer access token through the Read AI OAuth 2.1 authorization-code flow described in API Keys & Authentication: first register a client at `https://api.read.ai/oauth/register`, then complete the browser flow at `https://api.read.ai/oauth/ui`, then exchange the code for tokens at the token endpoint shown in the docs. Tokens carry scopes such as meeting:read and mcp:execute; access tokens expire after about 10 minutes and must be refreshed with the rotating refresh token.
conventions · 1/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://read.ai/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing