The Read AI MCP server is a remote MCP (Model Context Protocol) server that allows AI assistants to access Read AI's capabilities through a standardized interface. It is currently available as an open beta release.

⚠️ Before starting, make sure you have reviewed the prerequisites.

Server Details

You'll need these details if setting up a custom connection to the MCP server. You don't need this if you're connecting using the ChatGPT plugin or Claude connector.

Server URI: https://api.read.ai/mcp
Authentication: OAuth 2.1 (sign in using your Read AI account)
Type: Remote MCP Server
Transport: Streamable HTTP

Compatible MCP Clients

The Read AI MCP server is compatible with various MCP clients, including:

Available Tools

For examples of what you can do with these tools, see What can you do with Read AI's MCP server?

Once connected, the Read AI MCP server provides two powerful tools for accessing and analyzing your meeting data:

1. Get meeting by id

Retrieve comprehensive information about a specific meeting using the meeting ULID identifier.

What you can retrieve:

Basic metadata (title, start/end times, platform, report URL)
Participants with attendance status
Summary
Chapter summaries
Action items
Key questions
Topics
Full transcript with speaker identification
Metrics
URL to download the meeting recording as an MP4 file

2. List meetings

Browse and filter your meeting history with date-range filtering and pagination support.

What you can do:

Browse recent meetings (up to 10 per page)
Filter meetings by date range
Paginate through large collections of meetings
Includes the same detailed information as Get Meeting by ID (basic metadata summary, chapter summaries, action items, key questions, topics, transcript, metrics, and recording_download) for each meeting in the list

3. Create meeting agent

Send a Read AI meeting agent (bot) to a video conferencing meeting on your behalf. It works with Zoom, Google Meet, and Microsoft Teams.

To deploy an agent, provide:

Meeting URL — the full join link (e.g. a Zoom link or Google Meet URL). The platform, meeting ID, and password (if included in the link) are parsed automatically.

— or, if you'd rather specify manually —

Platform — Zoom, Google Meet, or Microsoft Teams
Meeting ID — the platform-specific ID (Zoom meeting number, Meet code, etc.)
Password — only if the meeting requires one

Optional:

Start time — schedule the agent to join at a future time. If omitted, it joins immediately.
Title — a custom name for the meeting report. If omitted, we'll try to generate a descriptive title based on the transcript.

Good to know:

If an agent has already been dispatched to the same meeting, requesting it again won't create a duplicate — you'll get the existing meeting record instead.
Once the meeting is underway or complete, its data (summary, transcript, action items, etc.) becomes available via the meeting report.
Agents can only be sent to meetings you've explicitly specified — not guessed or inferred meeting IDs.

4. Share meeting report

Grant another person access to a specific meeting report and, optionally, send them an email invite.

To share a report, provide:

Meeting ID — the ID of the report you want to share
Email address — the recipient's email. If they already have a Read AI account, access is granted directly; otherwise an email-based invite is created for them.