Read AI

Read Read AI meeting transcripts, summaries and action items.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Read AI connector does

The Read AI MCP server connects your Read AI meeting history — transcripts, summaries, action items, key questions and engagement metrics — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists two read tools. Read AI's own documentation describes four, and the two it omits both write. Sign-in is OAuth 2.1.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Read AI tools (4)

  • get_meeting_by_id
  • list_meetings

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Anthropic's listing omits both write tools. The directory carries two names and marks the connector "permissions": "Read". Read AI documents four tools, and the two missing ones dispatch a recording bot and email a meeting report to a named person. Do not size this connector's risk from the directory entry.
  • We could not verify which list the live server serves. The endpoint returned HTTP 401 to an anonymous request, so no tools/list response, no parameter schemas and no safety annotations. Whether the deployed server exposes two tools or four is unresolved from outside.
  • We do not publish machine names for the two write tools. Read AI's article gives them as prose headings only. Guessing at snake_case identifiers would fabricate a fact, so they appear here in Read AI's own wording.
  • mcp:execute is an undifferentiated grant. One of seven advertised scopes names a resource, and it is the read one. Nothing at the OAuth grant separates reading a transcript from sending a bot into a live call or emailing a report externally.
  • Both outbound actions are irreversible on the first call. A dispatched bot has been seen by the other participants; a sent invite has been delivered. Read AI's documented idempotency protects against duplicate retries, not against the first call.
  • Consent in desktop and mobile mode is entirely yours to obtain. No bot appears, no participant list entry, and the "Read Stop" and "Opt Out" chat commands do not work. Read AI says so itself and provides recommended consent language, but cannot enforce it.
  • Global Report Access widens the read surface to the whole workspace, and Read AI names the MCP server explicitly as a path that inherits it. We found no way to scope the connector more narrowly than the account it authenticates as.
  • There is no delete, edit or correction tool. Nothing in either list removes a report, redacts a passage or fixes a misattributed speaker. Deletion runs through the Read AI app, an in-meeting "Opt Out", or account deletion.
  • The model-training exception is opt-out, not opt-in. Read AI states meeting content is not used for training without explicit opt-in, except for a Customer Experience Improvement Program that is opt-out by default and which it says 10 to 15 percent of users are in.
  • Token handling is awkward by Read AI's own account. It documents 10-minute access tokens and single-use rotating refresh tokens, warns this "may require manual intervention if token chains break", and reports some MCP clients failing against its authentication.
  • Rate limit is 100 requests per minute per user, returning HTTP 429. list_meetings caps at 10 meetings per page.
  • The whole thing is an open beta. Read AI labels both the API and the MCP server as open beta, lists feature gaps including Ask Read and coaching, and says additional tools are planned.
  • The vendor's own docs are unreachable to a normal HTTP client. Read AI's help centre sits behind a Cloudflare challenge that returns HTTP 403 to a plain request. Everything cited here came through the help_center JSON API, which Read AI's llms.txt nominates for exactly this purpose.

Frequently asked questions

How many tools does the Read AI MCP server have?

Read AI documents four; Anthropic's directory lists two. The directory names get_meeting_by_id and list_meetings, both reads. Read AI's own MCP Server article adds Create meeting agent and Share meeting report, numbered 3 and 4 on the same page. The two the directory omits are the only two that write.

Can the Read AI connector send a recording bot into a meeting?

Yes, per Read AI's documentation, though Anthropic's listing does not show that tool. Read AI documents a Create meeting agent tool that dispatches a Read AI bot to a Zoom, Google Meet or Microsoft Teams meeting from a join link, optionally scheduled for a future time. Anthropic's directory lists only the two read tools.

Do other people know when Read AI is recording them?

In web mode yes, in desktop mode no. Read AI states that in web mode the bot appears in the participant list, may announce itself in chat, and any attendee can type Opt Out to end recording and delete that session's data. In desktop and mobile mode audio is captured locally, no bot appears, and those commands do not work.

Can the Read AI connector share a meeting report with someone outside my company?

Read AI documents a Share meeting report tool that grants a named email address viewer or editor access and sends an invite. Read AI states that if the recipient has no account an email-based invite is created for them, and that a notify flag defaults to yes. Anthropic's directory does not list this tool.

What OAuth scopes does the Read AI MCP server request?

Seven, of which two are functional. Read AI's RFC 9728 descriptor advertised openid, profile, email, offline_access, offline, mcp:execute and meeting:read on 2026-08-23. Only meeting:read names a resource. The write tools Read AI documents can only fall under mcp:execute, which names no object and separates nothing.

What personal data does the Read AI MCP server expose to an agent?

Full transcripts with speaker attribution, plus participant names and email addresses. Read AI documents the meeting object as carrying participants with name, email, invited and attended flags, an owner record, engagement metrics, and a URL to download the recording as an MP4. Those participants include people outside your company.

Can a Read AI admin read the whole workspace through MCP?

Yes, if Global Report Access is enabled. Read AI states that workspace owners and admins granted this setting can retrieve data for all meetings in their workspace through the REST API and MCP server, and warns to use it with caution as it could expose sensitive information. Without it, a user sees only their own reports.

Are there rate limits on the Read AI MCP server?

Read AI documents 100 requests per minute per user, returning HTTP 429 when exceeded. It also documents access tokens expiring after 10 minutes and single-use refresh tokens that rotate on each refresh, and warns this may require manual intervention if token chains break. Both API and MCP server are in open beta.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Read AI to work.

Connect Read AI once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.