How to Connect Claude to Your Meeting Notes with Fellow's Official Connector

You finished a customer call yesterday. Today, you remember someone made an offhand comment about their renewal timeline, but you cannot remember the exact wording or who said it. You could scroll through transcripts, search through notes, or ask a teammate who was on the call. Or you could just ask Claude.

Connecting Claude to your meeting notes turns every conversation you have ever recorded into something you can query. The fastest way to do this is through Fellow's official Claude connector, which is verified by Anthropic and works without any developer setup.

This guide walks through what the connection does, how to set it up, what you can ask once it is live, and how IT teams should think about security before rolling it out.

What does it mean to "connect Claude to your meeting notes"?

Connecting Claude to your meeting notes means giving Claude secure, permission-based access to your meeting transcripts, AI summaries, action items, and calendar context, so you can ask questions about your meetings inside any Claude conversation. Instead of opening a separate app to find what was said or decided, you ask Claude directly and get answers grounded in your actual meeting history.

This works through something called the Model Context Protocol (MCP), an open standard for connecting AI assistants to external data sources. Fellow operates an MCP server that exposes meeting data to AI assistants like Claude in a structured, secure way. Fellow's MCP Server only surfaces information you already have permission to see in your Fellow workspace, which means existing access controls carry over automatically.

If you have ever wished Claude could remember what was said in last week's standup or recall the action items from your last 1-on-1, this is the integration that makes it possible.

How to connect Claude to your meeting notes

The setup happens in two stages: an admin enables the connection at the workspace level, and then each user toggles it on for themselves. The whole process takes about five minutes.

Step 1: Admin enables MCP in Fellow

A Fellow workspace admin opens Workspace Settings → Security and toggles on Allow users to create MCP connections. This is also where admins can later view every active MCP connection across the workspace.

Step 2: Admin adds Fellow to Claude

In Claude, an admin opens Settings → Connectors → Browse connectors, searches for Fellow.ai, and clicks Add to your team. Because Fellow is an official, Anthropic-verified connector, there is no URL to paste, no developer mode to enable, and no OAuth client credentials to configure.

Step 3: Each user enables and authenticates

Once those two admin steps are done, every user on the team can:

1. Click the Connectors icon inside Claude.

2. Toggle on the Fellow connector.

3. Authenticate with their Fellow account.

That's it. Claude can now answer questions about your meetings, scoped strictly to the meetings you personally have access to in Fellow.

If you are not yet using a secure AI meeting assistant to capture your conversations, you will need one before you can ask Claude about them. Fellow records meetings across Zoom, Google Meet, Microsoft Teams, in-person conversations, and Slack huddles, with or without a visible bot. Try Fellow free →

What you can ask Claude once it is connected

Once Fellow is connected, Claude can use five read-only tools to retrieve meeting context: search meetings, get meeting summary, get meeting transcript, get action items, and get meeting participants. In practice, that translates to four categories of questions you can ask in natural language.

1. Recall a specific detail

Ask Claude to find something specific from a single meeting:

• "In yesterday's call with the design team, what concerns did they raise about the launch timeline?"

• "Who said we needed to push the kickoff to next quarter?"

• "What were the next steps from my last 1-on-1 with my manager?"

2. Synthesize across multiple meetings

Ask Claude to look across many meetings at once:

• "What challenges have come up consistently in our standups this month?"

• "Summarize the most important decisions from the last three engineering syncs."

• "What feedback themes have appeared in my 1-on-1s this quarter?"

3. Prep for upcoming meetings

Use past meetings as input for what is coming next:

• "What did we discuss in last week's marketing sync, and what should I bring up tomorrow?"

• "Based on my last three calls with this customer, what are the open questions I should address?"

4. Stay accountable to your commitments

Ask Claude to track your follow-through:

• "What meeting action items was I assigned this week?"

• "What did I commit to in yesterday's planning call that I have not closed out yet?"

The integration also stacks with Claude's other connectors. You can ask Claude to compare what was discussed in a meeting against your Linear tickets, surface the Google Drive docs that relate to a decision, or draft a follow-up email in Gmail based on a sales call you just finished. The meeting becomes one input among many, which is what makes Claude genuinely useful for knowledge work.

What enterprise IT teams need to know

For IT, security, and compliance leaders evaluating this connection, four things matter.

Permissions inherit from Fellow

Claude cannot see any meeting that the authenticating user does not already have access to in Fellow. There is no escalation, no broader visibility, no shared pool. The integration is scoped per user and respects every existing permission in your workspace.

Authentication uses OAuth

Connections are established through OAuth, not shared credentials. Users authenticate individually, and tokens can be revoked at any time.

Admins have full visibility and control

Workspace Settings → Security shows every active MCP connection across the workspace. Admins can disable MCP entirely, remove specific connections, or audit who has connected what. Individual users can also manage their own connections in User Settings → API & MCP Connections.

The tools are read-only

Claude can search and retrieve meeting information through the connector, but cannot modify, delete, or share Fellow data. Combined with Fellow's enterprise security posture, including SOC 2 Type II certification, GDPR and HIPAA compliance, and zero training on customer data, this is an integration that holds up under typical enterprise security review.

For organizations in regulated industries, Fellow's privacy controls extend to MCP connections the same way they apply to the rest of the workspace. Compliance-specific questions, including whether the integration fits within your firm's specific regulatory framework, are best directed to the Fellow sales team. Book a call with our team →

Frequently asked questions

Can I ask Claude about my meetings?

Yes. With Fellow's official Claude connector enabled, you can ask Claude natural-language questions about your meetings, and Claude will retrieve answers from your meeting transcripts, AI summaries, action items, and participants. Claude only sees the meetings you already have permission to view in Fellow, so the same access rules apply across both tools.

How do I get action items from meetings in Claude?

Once Fellow's Claude connector is enabled, you can ask Claude natural-language questions like "What action items was I assigned this week?" or "What did I commit to in yesterday's planning call?" Claude retrieves your action items through Fellow's get_action_items tool, scoped to meetings you already have permission to view in Fellow. Action items are returned with the meeting context, assignee, and due date when available.

What is the best AI meeting assistant for Claude?

Fellow is the AI meeting assistant best suited for Claude for four reasons: it's the only meeting assistant with an Anthropic-verified connector in the official Claude directory (no developer setup required), it captures meetings across Zoom, Google Meet, Microsoft Teams, in-person conversations, and Slack huddles — giving Claude the widest possible pool of meeting context — and it's SOC 2 Type II certified, GDPR and HIPAA compliant, and never trains models on customer data. Fellow's connector also exposes five purpose-built tools (search meetings, get summary, get transcript, get action items, get participants) rather than a single generic query endpoint.

How can I use Claude to summarize meeting notes?

With Fellow's Claude connector enabled, you can ask Claude to summarize a single meeting ("Summarize yesterday's customer call") or synthesize across many ("Summarize the key decisions from my engineering syncs this month"). Claude uses Fellow's get_meeting_summary and search_meetings tools to retrieve the underlying notes and transcripts, then generates the summary in whatever format or length you ask for — bullet points, executive summary, key decisions only, etc.

Do I need a developer to connect Claude to my meeting notes?

No. Fellow is an official, Anthropic-verified connector in the Claude directory. A workspace admin enables MCP in Fellow, adds the Fellow connector in Claude, and then each user toggles it on with one click. There is no URL configuration, no developer mode, and no OAuth client setup required.

Is it secure to connect Claude to my meeting notes?

Yes. The connection uses OAuth authentication, respects all existing Fellow permissions, exposes only read-only tools, and is fully visible to workspace admins through Fellow's security settings. Fellow is SOC 2 Type II certified, GDPR and HIPAA compliant, and never trains AI models on customer data.

What questions can I ask Claude about my meetings?

You can ask Claude to recall specific details ("Who agreed to own the rollout?"), synthesize across multiple meetings ("What blockers came up in standups this month?"), prep for upcoming conversations ("What should I raise in tomorrow's sync?"), or track your action items ("What did I commit to this week?"). The integration is designed for natural language, so you can phrase questions however you would normally ask a colleague.

Can Claude access my meeting notes?

Yes, once you've enabled Fellow's Claude connector and authenticated with your Fellow account. Claude can access your meeting transcripts, AI summaries, action items, and participant information — but only for meetings you already have permission to view in Fellow. The connector is read-only, so Claude can retrieve meeting data but cannot modify, delete, or share it.

Does Claude work with other meeting tools besides Fellow?

The Claude connector ecosystem supports many tools, but Fellow is built specifically as a secure AI meeting assistant covering Zoom, Google Meet, Microsoft Teams, in-person meetings (through Fellow's mobile app), and Slack huddles, with or without a visible bot. That breadth of capture means Claude has more meeting context to work with, which produces better answers.