Vibe AI

Read meeting transcripts, summaries and memos from a Vibe workspace.

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 Vibe AI connector does

The Vibe AI MCP server connects a Vibe workspace — the meeting memory captured by Vibe's Bot and Dot recording hardware — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 10 tools, and every one of them reads: meetings, transcripts, summaries, outlines and memos. Sign-in is OAuth against Vibe's own authorization server.

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.

Vibe AI tools (10)

  • get_meeting
  • get_meeting_outline
  • get_memo
  • get_summary
  • list_meetings
  • list_memos
  • list_summaries
  • search_meeting_transcript
  • search_meetings
  • search_memos

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

Limits

  • Vibe publishes no tool list for this server. The 10 names come from Anthropic's directory. We could not diff them against a vendor enumeration in either direction, because none exists — not as a feature list, not as an exclusion list, and not as a screenshot. Vibe's 571-page sitemap contains no MCP page at all.
  • The nominated documentation URL is dead. vibe.how/en/articles/14865506 redirects to help.vibe.us and returns HTTP 404, as does the help centre root and the sitemap.xml its own robots.txt names. The robots.txt pattern Disallow: /[helpCenterIdentifier]/ shows an Intercom help centre whose workspace path we could not resolve. The entire help centre appears to be offline, so a vendor tool list may exist and be unreachable.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request. No parameter-level detail on this page is verified, and no readOnlyHint or destructiveHint was observed.
  • access:ufs is undocumented. One of three OAuth scopes names a capability Vibe defines nowhere. It is not an unbounded wildcard, but it is not demonstrably a read either.
  • Whether MCP reads consume AI Credits is unresolved. Vibe meters "fetching deep knowledge" as an agentic feature and does not say whether this connector's reads count. The free Starter tier carries no credits at all.
  • Memory retention is plan-gated. 7 days on Starter, 12 months on Pro, permanent on Max. Vibe states this governs the Memory Graph's active context rather than file deletion, so an older meeting may exist while being outside what the AI can reason over.
  • Deleted content persists briefly. Vibe's privacy policy states deleted customer content is "retained for up to 7 days after deletion to support operational recovery and integrity".
  • The connector reads other people's speech. Everything it returns was said by someone, and Vibe's own consent flow — not this connector — is what governs whether they agreed to it.
  • This connector was promoted to partner tier within the last week. It was listed at community tier in our 2026-08-16 snapshot and appears at partner on 2026-08-23, with an identical tool list. The review it received is recent.

Frequently asked questions

Is the Vibe AI connector the same thing as vibe coding?

No, and the name collision is worth stating plainly. This connector belongs to Vibe Inc, the company at vibe.us that sells the Vibe Board S1 smart whiteboard and the Vibe Bot and Vibe Dot recording devices. It has no relationship to vibe coding, to Vibe Prospecting or to Viberate, which are separate entries in the same directory.

Can the Vibe AI connector change or delete a meeting recording?

No. All 10 tools Anthropic lists carry get, list or search verbs, and the server's own OAuth descriptor advertises read:meetings and read:memos. There is no create, update, delete, share or export verb anywhere in the listing or the scope set, so the connector reads your meeting memory and writes nothing back to it.

Can the connector share a Vibe meeting or board by link?

No tool does. Vibe's security page documents link sharing on Canvas, its whiteboard product, and states admins can disable it to stop anyone outside the organization reaching company files. That sharing lives in the Canvas application, not in this connector. No listed tool and no advertised scope reaches a share, publish or invite operation.

What OAuth permissions does the Vibe AI MCP server request?

Three, and two of them are explicitly read-only. The server's RFC 9728 descriptor advertised read:meetings, read:memos and access:ufs on 2026-08-24, and Vibe's authorization server advertises the identical three. Vibe documents access:ufs nowhere, so what it grants is unresolved. It is the one scope that cannot be shown to be narrow.

Does using the Vibe AI connector consume AI Credits?

Vibe does not say, and the question matters. Vibe's pricing page states that agentic tasks including fetching deep knowledge consume AI Credits, while passive transcription consumes minutes. Reading meeting memory is exactly that kind of fetch. The free Starter plan includes no AI Credits at all, so a metered read would fail rather than bill.

What personal data does the Vibe AI connector expose?

Recorded speech from everyone in the room. The tools return meeting transcripts, summaries, outlines and memos captured by Vibe Bot and Vibe Dot hardware, which means words spoken by colleagues, customers and anyone else present. Vibe's privacy policy names OpenAI as its AI processor under no-training and no-retention terms.

How long does Vibe keep meeting memory the connector can read?

It depends on the plan, and only the active context expires. Vibe's pricing page lists 7-day memory retention on the free Starter tier, 12 months on Pro at $9 per seat per month, and permanent retention on Max at $29. Vibe states retention governs the Memory Graph's active context, not deletion of the underlying files.

Why does the documentation URL for the Vibe AI connector not work?

Because the page Anthropic's directory nominates is gone. The listed URL vibe.how/en/articles/14865506 redirects to help.vibe.us and returned HTTP 404 on 2026-08-24, as did the help centre root and its sitemap. Vibe's product pages at vibe.us are live and served this page's documentation instead.

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 Vibe AI to work.

Connect Vibe 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.