Read AI offers both a REST API and an MCP (Model Context Protocol) server, giving you programmatic and agentic access to meeting data such as transcripts, summaries, and action items. Besides integrating with the API directly, you can connect third-party AI apps and platforms (such as ChatGPT, Claude, and other LLM-powered tools) as MCP clients, so they can query and work with your Read AI meeting data.
Prerequisites
The MCP server and API are available on all plans, including the Free plan. The only restriction: if you belong to a workspace, the Downloads option must be enabled in Workspace Settings > Reports & Sharing:
Getting started
For most people, the easiest way to start is to connect an AI tool you already use to the Read AI MCP server. You can then access and manage your Read AI meeting notes and transcripts right from that tool. See the setup guide for your tool:
- Connecting the Read AI MCP Server to ChatGPT and Codex (or install the official Read AI ChatGPT plugin)
- Connecting the Read AI MCP Server to Claude (or add the Read AI Claude connector)
- Connecting the Read AI MCP Server to Microsoft Copilot Studio
- Connecting the Read AI MCP Server to Gamma
You'll also find Claude, ChatGPT, Gamma, and MCP ("Connect Read AI to any MCP-compatible client") under Productivity on your Integrations page. For Claude, click Connect in Claude, or search for "Read AI" in the Claude Connectors directory. For ChatGPT, click Connect in ChatGPT, or search for "Read AI" in the ChatGPT Plugins directory, then click Install plugin and Allow Access. For other MCP-compatible clients (such as VS Code, Cursor, or Microsoft Copilot Studio), click View Documentation on the MCP card.
For ideas on what to do once you're connected, see What can you do with Read AI's MCP server? For the available tools and other ways to connect, see MCP Server.
If you're a developer or want to build a more traditional software integration with Read AI, see API Keys & Authentication to set up OAuth access to the API (Read AI uses OAuth access tokens, not static API keys), and API Reference to learn what the API can do and how to call it.
Troubleshooting
If you run into problems, first make sure you've read the relevant articles under Continue reading. The most common pitfalls and limitations are:
- Managing access tokens (API only): Access tokens expire after 10 minutes. Refresh tokens last about 6 months and are single-use: each refresh returns a new refresh token, so always save the newest one and stop using the old one. The old refresh token keeps working for a short grace period, up to 10 minutes after the new token is issued or 5 more uses, whichever comes first. This covers concurrent requests and refresh calls that fail. After that, the old token is rejected. This is a standard OAuth 2.1 setup, but developers used to long-lived static API keys may find these tokens harder to manage. Carefully follow the steps in API Keys & Authentication, including the troubleshooting tips at the end.
- Rate limits: The API allows up to 100 requests per minute per user. Going over this limit returns HTTP 429 errors; watch for this response and slow down your calls when you get it.
- SSO redirect: You can authenticate using SSO, but some users have reported not being sent back into the OAuth flow after signing in with their organization's SSO (SAML). If this happens, restart the OAuth process after signing in and it should work.
- Live transcript: Live meeting data, including the live transcript, is available through the API and MCP server, but by default it's only available for a meeting if someone has the live meeting dashboard open during the meeting. If you want live transcription turned on automatically for all your meetings, enable "Live Transcription" in your account settings.
- Permissions: You can only retrieve data for meeting reports you can access in the Read AI web app. Admins must turn on Global Report Access to access all reports in a workspace.
Feedback and improvements
If you have suggestions or need help, please contact our support team. We always welcome feedback on the developer experience. We'll keep adding new MCP tools and API endpoints, and your input helps us decide what to build.
Continue reading
For setup instructions, the API reference, and MCP guides, see: