How to Connect Claude with Meetbook

Your meetings are a goldmine of context. Decisions. Commitments. Objections. Ideas that someone threw out in the last three minutes of a call and then everyone forgot about.

But most of that context is locked away — scattered across Zoom recordings you'll never rewatch, transcripts you'll never read, and action items that evaporated the moment the call ended.

Meetbook already captures all of it. It joins your meetings on Zoom, Google Meet, and Microsoft Teams, transcribes every word with speaker labels, flags action items and decisions, and builds a searchable archive.

Now you can plug all of that directly into Claude.

No copying transcripts. No exporting PDFs. No writing custom scripts with the Anthropic API. When you connect Claude to Meetbook, your entire meeting history becomes something Claude can reason about — in plain English, right in your conversation.

Before you start

You need two things:

• A Meetbook account with at least one recorded meeting
• Claude Desktop, claude.ai, or any Claude client that supports MCP connectors

That's it. No API keys. No code. No paid add-on.

Connect Claude to Meetbook in 3 steps

The integration uses the Model Context Protocol (MCP) — the same standard Anthropic built so AI assistants can talk to external tools. Meetbook runs an MCP server that Claude connects to directly.

Step 1: Copy your MCP server URL

Open Meetbook, go to Settings > AI Connect, and copy the MCP server URL:

https://api.veeboo.in/mcp

Step 2: Add it to Claude

In Claude Desktop or claude.ai, go to Settings > Integrations > Add more, paste the URL, and click Connect.

Step 3: Authorize Meetbook

Claude will redirect you to a Meetbook authorization page. Review the permissions (read meeting summaries, search transcripts, access action items) and click Allow Access.

That's it. The connection is live. Claude now has a set of tools it can call to pull data from your Meetbook account — and it'll use them whenever you ask about your meetings.

What to ask Claude once you're connected

The real power is in how you use it. Here are prompts that work across different roles.

For sales

• "Summarize my last three discovery calls and tell me which objections came up more than once."
• "What commitments did I make on the Acme call last Tuesday?"
• "Find every meeting where we discussed pricing in Q1."

For engineering leads

• "What were the action items from this week's standups?"
• "Pull the technical decisions we made in the architecture review last month."
• "Which teams raised concerns about the API migration?"

For customer success

• "What issues have come up in onboarding calls this month?"
• "Show me the key takeaways from my last five client check-ins."
• "Which customers mentioned frustration with reporting?"

For executives

• "What decisions were made in the board meeting last quarter?"
• "Summarize the Q2 planning sessions across all departments."
• "How much time did we spend on operational topics versus strategy this month?"

For anyone

• "What are my open action items across all meetings this week?"
• "Search my meetings for any mention of the budget reallocation."
• "Show me the transcript from the candidate interview on Monday."

Claude calls Meetbook's tools behind the scenes — get_meetings_list to find meetings, get_meeting_summary for recaps, get_action_items for tasks, get_meeting_transcript for the full conversation — and then synthesizes the answer in natural language.

How it works under the hood

When you ask Claude a question about your meetings, it doesn't search blindly. It uses specific MCP tools that Meetbook exposes:

• get_meetings_list — retrieves your meetings with filters for date, platform, tags, and more
• get_meeting_summary — returns the AI-generated overview, chapters, and key bullets
• get_action_items — pulls tasks, decisions, and follow-ups with status and owner
• get_meeting_transcript — retrieves the full raw transcript when you need the exact words

Claude decides which tool to call based on what you asked. It can chain multiple calls — for example, searching for a meeting first, then pulling the action items from it.

What makes this different

Most "Claude meeting integration" guides tell you to copy-paste transcripts or build a custom pipeline with the Anthropic API. Both work, but they're fragile and manual.

Meetbook's approach is different for three reasons:

It's zero-maintenance. Once connected, Meetbook keeps recording your meetings. Claude always has access to the latest data — no re-upload, no re-export.

It works across platforms. Zoom, Google Meet, Microsoft Teams — Meetbook joins them all. One connection gives Claude visibility into every meeting, regardless of where it happened.

It respects permissions. Claude only accesses meetings that belong to your Meetbook account. In a team setup, that means each person's Claude connection is scoped to what they can already see. You can revoke access anytime from Settings.

Disconnect anytime

Not what you expected? Go to Settings > AI Connect in Meetbook and click Disconnect. The MCP session is revoked immediately, and Claude loses access to your meeting data.

To reconnect, just repeat the three steps above.

Need help? Reach out to our team at team@meetbook.app or check the Meetbook docs.