Before you start

Create a personal access token first:

Open Settings → Integration.
In the Personal access tokens card, click Create token.
Copy the token immediately. Vibe shows it only once. Treat it like a password — anyone with this token can act as you against the Vibe API.
Click Done to close the dialog. The token now appears in the list by its short prefix, along with when it was created, last used, and when it expires.

Caption: A personal access token is shown only once. Copy it before closing the dialog.

💡 Note:

To revoke a token, click the trash icon next to it in the list. Any integration using that token will stop working immediately.
You can create as many tokens as you need — one per device or per agent is a good habit, so revoking one doesn't break the others.

Pull meeting data with the remote MCP server

Vibe exposes meeting data through a hosted MCP (Model Context Protocol) server. Any MCP-capable client can connect to it and ask Vibe for your meetings, transcripts, and AI summaries on demand.

This is the right choice if you want your agent to fetch context when it needs it (for example, "summarize my last meeting with Acme") rather than receive a real-time push.

Step 1 — Get a personal access token

Follow the steps in Before you start if you haven't already. You can reuse the same token you used for memo push, or create a separate one — both work.

Step 2 — Point your MCP client at Vibe

Connect your MCP client to:

https://mcp.vibe.us/mcp

Authenticate with the personal access token using a standard Authorization: Bearer header. Most MCP clients have a field for the URL and one for the bearer token.

Example — Claude Code

Add it to your user-level config from the command line

claude mcp add --transport http --scope user vibe-chorus \
 https://mcp.vibe.us/mcp \
 --header "Authorization: Bearer xxxxx"

or edit .mcp.json in your project root:

{
 "mcpServers": {
  "vibe-meetings": {
      "type": "http",
      "url": "https://mcp.vibe.us/mcp",
      "headers": {
        "Authorization": "Bearer xxxxx"
      }
    }
  }
}

For verifying, you can restart Claude Code and type /mcp — you should see vibe-chorus ✔ connected with 10 tools. The first tool call asks for permission; choose "always allow" and it won't ask again (every tool is read-only, so this is safe).

Example — Claude Desktop, Cursor, and other MCP-capable apps

Add a new MCP server with:

URL — `https://mcp.vibe.us/mcp`
Transport — HTTP / streaming HTTP (whichever your app calls it)
Auth — Bearer token, value is your Vibe personal access token

What your agent can do

Once connected, your agent has access to these tools:

Tool	What it does
list_meetings	List all Chorus meetings you can access.
search_meetings	Search meetings with optional filters.
get_meeting	Get details and permissions for a single meeting.
get_meeting_outline	Preview a meeting’s timeline segments before pulling transcripts.
search_meeting_transcript	Fetch the full transcript of a meeting.
list_summaries	List every AI summary that exists for a meeting.
get_summary	Fetch one summary, by template.
list_memos	List all memos you can access.
search_memos	Search memos with optional filters.
get_memo	Get detail content for a single memo.

All tools respect Vibe's access controls — your agent can only see meetings, transcripts, and summaries that you can already see in the Vibe app.

Try it

In your MCP-capable agent, ask something like:

"List my five most recent Vibe meetings."
"Pull the transcript for my last meeting with the design team and summarize the action items."
"Show me the customer-call summary template for meeting `<id>`."

The agent will call the relevant tools under the hood and answer from real meeting data.

Troubleshooting

My agent says it can't authenticate to the MCP server.

The token is expired, revoked, or mistyped. Create a fresh token and update the agent's config.
Confirm the URL is exactly `https://mcp.vibe.us/mcp` (no trailing slash variants, no extra path).

My agent connects but `list_meetings` returns nothing.

The token belongs to a user who has no accessible meetings. If you have multiple Vibe accounts, double-check you created the token while signed in as the right one.

I want to disconnect everything fast.

Delete the personal access token from Settings → Integration → Personal access tokens. Every integration using it stops immediately.

Security tips

One token per integration. Create a separate token for each agent or device, so you can revoke one without breaking the others.
Don't paste tokens into chat or screenshots. Once a token is exposed, revoke it and create a new one — the displayed value can't be recovered later.
Rotate periodically. Create a new token, swap it into your plugin's config, then delete the old one.

FAQ

Will my agent see meetings I haven't joined? - No. The MCP server enforces the same permissions as the Vibe AI app — your agent sees exactly what you see.
Can multiple agents share one token? - Yes, but we recommend one token per agent so revocation is targeted.