Claude Vibe AI connectorWhat Claude can do in your Vibe AI account.
The Claude Vibe AI connector exposes 10 tools, all of them reading. 10 read your meetings, transcripts, summaries and memos, 0 change anything, 0 are undocumented. Below: what Claude reads, what it asks first, what it cannot do, and who can switch it off in your organization.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude reads your Vibe AI record
Meetings captured by Vibe Bot, Vibe Dot or the Vibe AI app stop being something you replay. You ask what was decided on a given call, who took which task, or what a memo said, and Claude goes to your Vibe AI record to answer. It fetches that context when the question comes up, not as a live feed.
Find the call before you dig into it. search_meetings narrows meetings with filters, list_meetings covers everything you can access, and get_meeting confirms the details of the one you meant.
Read the right part of a long meeting. get_meeting_outline previews its timeline segments, then search_meeting_transcript brings back the full transcript when you need the exact wording.
Reuse summaries and memos instead of rewriting them. list_summaries shows every AI summary of a meeting, get_summary fetches one by template, and the three memo tools find notes captured on the go.
What Claude cannot do here: none of the 10 tools records, edits or deletes a meeting, a summary or a memo, and Vibe states that every tool is read-only. It also never reaches a meeting you cannot open yourself in the Vibe app. For how assistants and automation tools divide the work, the Integrations hub gathers the other families.
Five words before you plug it in
The vocabulary of this page, in one minute.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work with it while it answers you.
- Tool
- One named job a connector hands to Claude. Claude chooses the ones it needs on its own, and the directory sheet lists them by name.
- Authorization
- The Vibe sign-in screen where you give Claude the access it uses afterwards. Granted once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before something that would change your account goes ahead, asked in the conversation.
- MCP
- The open standard connectors rely on: it is what lets an assistant like Claude talk to an outside service such as Vibe AI.
Plug the Claude Vibe AI connector in, in three steps
- 01
Find Vibe AI in your connectors
Open Claude's settings, go to Customize, then Connectors, and search for Vibe AI. On a Team or Enterprise workspace, an Owner or Primary Owner switches it on for the organization before each member can sign in.
- 02
Start the connection
Click Connect on the Vibe AI row and sign in to Vibe in the window Vibe opens itself. Vibe describes this sign-in as its standard route; a personal access token is only an option for setups that do not use it.
- 03
Check what the screen grants
Read the authorization screen before you accept: it is Vibe's screen, not Claude's, that sets what the access covers. If the link breaks later, Disconnect and connect again.
The 10 tools of the Claude Vibe AI connector
Vibe AI gives Claude 10 tools: 10 that read your account, 0 that change something in it.
Every tool reads, and Vibe's own help article says so. Names stay exactly as Claude displays them.
- 10 read
What Claude reads (10)
10 toolsTen tools for meetings, transcripts, AI summaries and memos, none of which changes anything in Vibe AI.
get_meeting
Returns the details of a single meeting along with the permissions attached to it, so you can confirm which call is meant.
get_meeting_outline
Previews the timeline segments of a meeting before any transcript is pulled, so the segments can be seen without opening the whole transcript. It only covers meetings you can already see in the Vibe app.
get_memo
Opens the full content of one memo you recorded, rather than just its place in a list. The memo itself stays unchanged in Vibe.
get_summary
Fetches one AI summary of a meeting, chosen by its template. Vibe applies the same permissions as its own app, so only summaries you can already see in Vibe come back.
list_meetings
Lists every Chorus meeting your access covers, with no filter applied.
list_memos
Shows all the memos you can access, the notes captured on the go outside of a meeting. Each entry can then be opened in full by the next tool.
list_summaries
Enumerates every AI summary that exists for a given meeting. It shows what exists without opening any of them, for meetings captured with Vibe Bot, Vibe Dot or the Vibe AI app.
search_meeting_transcript
Despite its name, Vibe describes it as fetching the full transcript of a meeting, not just a segment of it.
search_meetings
Looks for meetings using optional filters, narrowing a long history down to the calls that match your question. Only meetings your access covers can come up.
search_memos
Runs a filtered search across your memos to surface the ones that match the filters you give. Results are limited to the memos you can access.
What Claude asks before acting in Vibe AI
Here, all 10 tools read, and no source describes a Vibe-specific confirmation inside Claude's web or desktop apps.
Claude's default rule is to stop and ask before any action it takes on an account for someone. Vibe's article adds one detail for Claude Code: the first tool call asks for permission, and choosing to always allow it is safe because every tool reads. Claude works with the access of the person who connected, and Vibe enforces the same permissions as its own app. On Team and Enterprise, owners decide which actions members may let through and can restrict a connector for the whole organization.
Which plans include the Claude Vibe AI connector
None of the 819 directory sheets states its availability by plan, so there is no official answer for Vibe AI alone.
Anthropic's general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization before members can connect. For the current state of this one, the Vibe AI sheet in the official directory is the only place that shows it.
What the connector does not do
This connector is documented only by its publisher: no Claude help center article and no Anthropic developer page covers it, so the limits below come from Vibe.
A connector is not an automation: Claude calls its tools while it answers you, and nothing runs by itself when a meeting ends. Vibe frames the same idea from its side: the server gives context when it is asked for, rather than pushing it in real time. By default the sheet exposes only reading, an observed floor rather than a promise. The directory's verification badge is not a security audit, and Anthropic says on every sheet that it does not choose a publisher's tools.
Need help connecting Vibe AI to Claude?
A person reads every message.