Before you start

Create a personal access token first:

Open Settings → Integration.
In the Personal access tokens card, click Create token.
Pick an expiration (Never, 7 days, 30 days, 90 days, or 1 year) and click Create.
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://api.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

In `.mcp.json`:

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

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

Add a new MCP server with:

URL — `https://api.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.
get_meeting	Get details and permissions for a single meeting.
get_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.

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 memo isn't showing up in my agent.

Confirm Memos is toggled on in Settings → Integration.
Confirm the plugin is running and reports it is connected (look for a connected or socket-open message in the plugin logs).
Make sure the token in the plugin's config hasn't expired or been deleted. Check the Last used column on the token list — if it never updates, the plugin isn't reaching Vibe.
Claude Code only: make sure you started Claude Code with --dangerously-load-development-channels server:<name>, where <name> matches the key in .mcp.json. Without this flag, Claude Code silently ignores third-party MCP servers like the Vibe bridge.

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://api.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.

A memo reply from my agent didn't appear in Vibe.

Replies only land on memos owned by the user who issued the token. If you reply to a memo you don't own (for example, a memo shared with you), Vibe will reject the reply.

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.
Set an expiration. "Never" is convenient but a fixed expiration limits the blast radius if a laptop is lost.
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

Do I need both integrations? - No. They're independent. Many people only need one.
Will my agent see meetings I haven't joined? - No. The MCP server enforces the same permissions as the Vibe 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.
Does turning off the Memos toggle delete past memos in my agent? - No. It only stops new memos from being pushed. Past messages already in your agent's history are untouched.
Can I push other kinds of content besides memos? - Memos are the only push channel today. More channels may be added — when they appear, they'll show up as additional switches in the Push content to AI agents card.