Claude Read AI connectorWhat Claude can do in your Read AI account.
The Claude Read AI connector exposes 2 tools, and both read. 0 write, 0 undocumented. Below: what Claude pulls from your meeting reports, what it cannot touch, where Read AI and the directory disagree, and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
Why a sales or ops lead would plug Read AI into Claude
Read AI already records and summarizes your calls. The catch is that the report sits in Read AI while the follow-up gets written somewhere else. With the connector, you ask Claude about last Tuesday's pipeline review and it opens the report itself: summary, action items, key questions and the full transcript, with who said what.
A follow-up email built on what was actually said. get_meeting_by_id brings back one meeting in full, including its action items and the speaker-tagged transcript. Claude drafts the recap from that, not from memory.
A week of calls in one answer. list_meetings walks your history over a date range, up to 10 meetings per page, and get_meeting_by_id then opens the ones that matter. Ask for every commitment made to a given client this month and Claude reads across the lot.
Prep before the next call. Pull the previous session with the same customer, check which questions stayed open, and walk in knowing where things stand.
Now the part the directory sheet does not spell out. By default, the sheet only exposes reading. It does not send a notetaker to a meeting, it does not share a report with a colleague, and it does not edit anything in Read AI. The vendor describes two tools that do those things, but the Claude directory does not list them (more on that below). Nothing runs on its own either: no tool wakes up when a meeting ends. If you want a report pushed to your CRM every time a call wraps, that is the job of an automation tool, a different trade, and our Integrations hub covers that side. The same breakdown exists for other apps, for instance the Claude asana connector.
Five words before you plug it in
The vocabulary you will meet on the way.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named job the connector opens to Claude. Claude picks the ones it needs mid-answer; the directory sheet lists them by name.
- Authorization
- Read AI's own sign-in screen, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before doing something that changes an account, shown right in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Read AI.
Connect Read AI to Claude in three steps
- 01
Find Read AI in the list
In Claude's settings, open Customize, then Connectors, and look for Read AI. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first; after that, each member connects on their own.
- 02
Start the connection
Hit Connect on its row. Read AI opens its own window, and you sign in with your usual Read AI account. If the link ever breaks, use Disconnect and connect again from scratch.
- 03
Read the authorization screen
Before you accept, read what the screen asks for. That screen belongs to Read AI, not to Claude, and it decides what the access covers. You can also withdraw that access later from your Read AI account.
The 2 tools of the Claude Read AI connector
Read AI gives Claude 2 tools: 2 that read your account, 0 that change something in it.
Both only read. Names stay exactly as Claude shows them, in English.
- 2 read
What Claude reads (2)
2 toolsTwo tools that open your meeting reports without changing them.
get_meeting_by_id
Opens one specific meeting and returns everything Read AI kept on it: title and times, attendees with their attendance, summary and chapter summaries, action items, key questions, topics, metrics, the full transcript with speakers named, and a link to download the recording as MP4.
list_meetings
Browses your meeting history, filtered by date range and paged up to 10 at a time. Claude can page on through a long history.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. The request shows up in the conversation, at the moment it matters.
With Read AI, that default barely comes into play, because the sheet lists only reading tools. The rest of the rule still matters. On Team and Enterprise, owners decide whether a member may let some actions through without being asked every time. They can also cap what a connector may do for the whole organization, keeping reading open and closing writing, and nobody gets around that from their own account. And Claude works with your rights, nothing more.
Which plans include it
Of the 819 sheets in the official directory, none shows availability by plan. The per-connector answer is published nowhere, which is a real gap in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before members can connect. For the current state, check the Read AI sheet in the directory from your own account.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing starts when a meeting ends or a report lands.
This connector is documented only by its publisher: neither Claude's help center nor Anthropic's developer docs have a page for it. Read AI calls its server an open beta. A tool list that shows only reading is an observed floor, not a guarantee, since an administrator can open actions no public sheet shows. The directory's partner badge is not a security audit, and Anthropic says on every sheet that it does not decide which tools a publisher exposes. Plug in publishers you know.
Can the Read AI connector send a bot to a meeting or share a report?
- Claude directory sheet ↗September 30, 2026Two tools listed: get_meeting_by_id and list_meetings, both reading.
- Read AI help article, MCP Server ↗September 2, 2026Read AI also describes a tool that sends its meeting bot to a Zoom, Google Meet or Teams call, and one that grants someone access to a meeting report, with an optional email invite.
What this page followsThe vendor article, updated September 2, describes two writing tools that the directory sheet, reread September 30, does not show. This page sticks to the sheet's two reading tools. If the other two show up in your account, the general approval rule covers them; the sheet on your own account is what counts.
Need help connecting Read AI to Claude?
A person reads every message.
