If you've searched for this before, you've probably run into a wall of confusing terminology. "MCP server," "Claude connector," "custom connector," "native integration" — vendors use these terms loosely, and sometimes incorrectly, to describe very different levels of access.
Here's the distinction that actually matters: MCP (Model Context Protocol) is the open standard Anthropic published — any vendor can build an MCP server on top of it. A native (or "built-in") Claude connector is different: it means Anthropic has reviewed and listed that integration in Claude's own connector directory, so you connect it with a single OAuth click, no manual setup, no pasted URLs or API keys. A custom connector, by contrast, is something a user adds manually by typing in a remote MCP server address — it works, but it's a meaningfully higher-friction, lower-trust setup, and it's not vetted by Anthropic the way a directory listing is.
This list covers only tools with a confirmed native, Anthropic-listed Claude connector — verified directly against Anthropic's own connector pages (claude.com/connectors) rather than vendor marketing claims. Several well-known meeting tools market an "MCP server" or even call it a "native connector" in their own blog copy, but on inspection require you to manually paste an API key or a remote server URL into Claude's custom-connector field. We've excluded those from this list, even where the vendor's own materials use the word "native" — the label doesn't match what Anthropic's directory shows. We note a couple of these cases below so you know why a tool you might expect to see here isn't included.
Methodology
We evaluated tools against four criteria, checked directly rather than taken from vendor copy:
- Connector verification — Confirmed via claude.com/connectors listings, not vendor blog claims. Several tools (MeetGeek, Avoma, Gong) describe themselves as having a "native" or "Claude-ready" MCP integration but are, per their own setup documentation, added as custom connectors (manual API key or MCP server URL entry). We excluded these.
- What the connector actually does — read-only vs. read/write, and what data it exposes (transcripts, summaries, action items, analytics).
- Security and compliance posture — certifications (SOC 2, HIPAA), and any active litigation or disclosed security incidents, checked against recent court filings and reporting rather than vendor security pages alone.
- Pricing and platform coverage — current published pricing where available; flagged where sources conflict or figures couldn't be independently confirmed.
Top AI Meeting Note Takers with Claude Connectors:
Fellow
Claude connector: Native, confirmed at claude.com/connectors/fellow-ai. Read access to meeting transcripts, summaries, and action items, with natural-language search across meeting history — surfacing past discussions, decisions, and multi-meeting summaries. Fellow's MCP server also includes a limited write capability added around August 2026: Claude can create and edit agenda items directly in a Fellow meeting note (admin-toggleable, with audit logging), rather than only surfacing suggested agenda content back in the chat window. As of this writing, that's a narrow, specific write action — agenda items only, not general read/write access to transcripts, recordings, or other meeting data — and based on available documentation, Fellow appears to be the only tool in this list with any write capability at all.
Fellow is an AI meeting assistant built with both bot and botless capture across Zoom, Teams, and Google Meet. It holds SOC 2 Type II certification, is GDPR-ready, and offers HIPAA compliance via BAA — along with configurable zero-day retention, transcript redaction, consent-capture logging, and information-barrier policies aimed at regulated teams. It also has one of the deeper integration footprints on this list: 50+ native integrations including Salesforce, HubSpot, Jira, Linear, and Glean, alongside the Claude connector.
Limitations: HIPAA compliance, zero-day retention, and the Super Admin API are gated to Business/Enterprise tiers — not available company-wide on every plan, so verify tier requirements against your specific compliance need before assuming coverage. Botless capture requires the desktop app, which can create adoption friction for teams used to a browser-only tool. Pricing on the compliance-heavy tiers is enterprise-custom with no self-serve trial. Fellow was named Wirecutter's pick specifically for "transcribing meetings into notes" — a subcategory endorsement, not an overall best-in-category pick, and it's worth being precise about that distinction. We found no active litigation against Fellow.
Best for: Compliance-conscious and regulated-industry teams that need governance controls (retention policy, redaction, information barriers) alongside the Claude connector.
Circleback
Claude connector: Native, confirmed at claude.com/connectors/circleback. Search and pull meeting notes, transcripts, calendar events, and contact/company context into Claude.
Circleback's standout feature is dedicated mobile capture — a lock-screen widget for one-tap in-person recording on iOS and Android, which most competitors on this list don't offer natively. It holds SOC 2 Type II certification and is HIPAA compliant, and several sources also cite EU-U.S. Data Privacy Framework certification, though that particular claim is worth confirming directly with Circleback before treating it as settled.
Limitations: No free tier — only a short trial before you hit a paywall. Pricing runs higher than most of this list (roughly $20.83/user/month for Individual, ~$25/user/month for Team, annual billing). It's a bot-based tool (joins the call as a visible participant), so it doesn't offer a botless option for teams that want to avoid that.
Best for: Teams that specifically need in-person and mobile meeting capture alongside video calls.
Fathom
Claude connector: Native, confirmed at claude.com/connectors/fathom. Read access to meeting summaries, transcripts, and action items, exposed as seven separate toggleable tools inside the connector settings.
Note: this is Fathom.video, the AI meeting assistant — a different company from Fathom Analytics or the Fathom recently acquired by QuestionPro (April 2026). Fathom.video has the most generous free tier on this list by most third-party comparisons: unlimited recordings and transcripts, with a handful of free AI summaries per month. We found no active privacy or biometric-privacy litigation against Fathom as of late August 2026.
Limitations: SOC 2 certification status for Fathom could not be independently confirmed as of the most recent reporting we found (February 2026) — worth asking directly before relying on it for a compliance-sensitive use case. Paid tier pricing is reported inconsistently across third-party sources (figures range from roughly $19 to $29/user/month depending on tier and source), so confirm current pricing directly with Fathom rather than from any one comparison site, including this one.
Best for: Individuals and small teams who want a genuinely usable free tier before committing to a paid plan.
Fireflies
Claude connector: Native, confirmed at claude.com/connectors/fireflies. Review meeting decisions, flag client concerns, and extract feature requests across calls via natural language.
Fireflies is the most CRM-integration-heavy tool on this list, with deep native connections to Salesforce, HubSpot, and Pipedrive. Several third-party comparisons cite SOC 2 Type II certification and HIPAA compliance, though we'd encourage confirming current certification status directly with Fireflies rather than relying solely on secondhand comparisons.
Litigation: Fireflies faces an active BIPA (Illinois Biometric Information Privacy Act) class action — Cruz v. Fireflies.AI Corp., No. 3:25-cv-03399, filed December 2025 — alleging its "Speaker Recognition" feature creates and retains voiceprints (biometric identifiers) without the written notice, consent, and retention-schedule disclosures BIPA requires, including from meeting participants who never created a Fireflies account. Sources disagree on which Illinois district court is hearing this case: several legal-industry sources (National Law Review, Workplace Privacy Report, Epstein Becker Green) cite the Central District of Illinois, while at least one (Amundsen Davis) cites the Northern District. The docket number format is consistent with Central District of Illinois numbering conventions, but this should be confirmed against the actual docket before publication. A second, related suit was filed in the Northern District of Illinois.
Limitations: The recording bot joins calls automatically by default and has to be manually disabled if you don't want that. Free tier storage is limited to three months.
Best for: Sales teams that want meeting data auto-logged into an existing CRM.
Granola
Claude connector: Native, confirmed at claude.com/connectors/granola.
Granola's core differentiator is architectural: it doesn't join meetings as a visible bot. Instead it runs locally on your device and listens to your computer's own audio, then expands the sparse notes you type yourself into a full AI-generated summary using calendar and meeting context. It holds SOC 2 Type 2 certification (achieved July 2025) and is GDPR-compliant, with an organization-wide model-training opt-out available for Enterprise workspaces. Audio is reportedly deleted immediately after transcription, which narrows what's retained.
Compliance gap: By Granola's own published security documentation, it is not currently HIPAA compliant and cannot sign Business Associate Agreements — the company describes HIPAA support as something it's evaluating for a future release, not something available today. This is a meaningful disqualifier for healthcare, financial services, or other PHI-handling use cases, regardless of how strong its other certifications are.
Litigation: Granola faces an active proposed class action — Chamberlain v. Granola, Inc., filed July 30, 2026 in the U.S. District Court for the Northern District of California, the same district hearing the Otter case. The complaint alleges Granola recorded meeting participants who were never told an AI notetaker was present, and that meeting content is used by default for commercial purposes, including AI model training, unless a user actively opts out. Notably, the complaint's central exhibits are screenshots of Granola's own marketing copy telling prospective customers that other people on a call "won't know it's there" — used to argue the product was designed around avoiding disclosure rather than defaulting to it. As with the other litigation noted in this piece, nothing has been decided on the merits; the case is at the pleading stage.
Limitations: No built-in export function — getting notes out of Granola is a copy-paste operation, and native integrations with tools like Slack and Notion are comparatively limited. The free plan is capped at a lifetime total of roughly 25 meetings (not a monthly allowance), which functions more as a trial than an ongoing free tier. Paid plans run from roughly $14/user/month (Business) to $35+/user/month (Enterprise).
Best for: Individuals who want a discreet, no-bot note-taking experience and don't have HIPAA or BAA requirements — with the pending litigation above factored into that decision.
Otter.ai
Claude connector: Native, confirmed at claude.com/connectors/otter-ai. Summarize meetings and search across transcripts via natural language.
Otter has the longest track record of live, real-time transcription on this list, and per third-party comparisons holds SOC 2 Type II certification and achieved HIPAA compliance in mid-2025.
Litigation: Otter faces a consolidated federal wiretap class action — In re Otter.AI Privacy Litigation, pending in the U.S. District Court for the Northern District of California before Judge Eumi K. Lee — alleging its bot joined Zoom, Teams, and Google Meet calls and recorded participants without all-party consent. This is a meaningfully live risk, not a dismissed nuisance suit: on August 13, 2026, the court denied Otter's motion to dismiss on the core claims. The federal Wiretap Act claim, the California Invasion of Privacy Act (CIPA) claim, and both Illinois biometric-privacy (BIPA) claims survive and are proceeding to discovery; separate claims under the Computer Fraud and Abuse Act, California's CDAFA, and the Washington Privacy Act were dismissed, but with leave to amend. Nothing has been decided on the merits, and no liability has been found — but the central consent theory has cleared its first serious court test.
Limitations: The bot joins as a visible call participant by default. Free tier caps out at 300 minutes/month, tighter than several competitors here.
Best for: Teams that prioritize live, in-meeting transcription accuracy and are comfortable with the litigation currently in progress.
Read AI
Claude connector: Native, confirmed at claude.com/connectors/read-ai. Full transcripts, summaries, action items, key questions, topics, and engagement metrics, queryable across your meeting history.
We found no active privacy or biometric-privacy litigation against Read AI as of late August 2026.
Limitations: Read AI has a well-documented pattern of uninvited-bot complaints. Because the bot joins meetings via calendar sync as soon as one participant connects their calendar, other attendees are frequently recorded without having opted in themselves or sometimes without knowing Read AI is present at all. This shows up starkly in review data: Read AI sits around 4.0/5 on G2 (a platform skewed toward people who chose the tool) but roughly 1.4/5 on Trustpilot, where the large majority of reviews are 1-star and several describe the bot's spread through their meetings as "viral" or compare it to a virus. Worth weighing seriously for any team where consent optics with external participants (clients, candidates, partners) matter.
Best for: Internal teams that want rich engagement/participation analytics, used carefully around any meeting with outside attendees.
tl;dv
Claude connector: Native, confirmed at claude.com/connectors/tldv. Fetch transcripts and notes from Google Meet, Zoom, and Teams meetings.
tl;dv has one of the more generous free tiers in the category — unlimited video recordings and transcripts across all three major platforms — plus multi-meeting pattern analysis as a paid-tier feature.
Security incident: tl;dv disclosed (via independent security researcher BobDaHacker, later reported by Dark Reading) a serious, unresolved data exposure. A missing Firestore database security rule allowed any authenticated tl;dv user to query meeting metadata belonging to other customers — reportedly 181,874 meeting records across 84,312 users and 35,003 domains, including government, university, and corporate accounts in 23 countries. The exposure included the ability to identify and join live in-progress calls the researcher was never invited to. The issue was first reported to tl;dv on January 28, 2026; as of the most recent reporting we could verify (early August 2026), it remained unpatched, with tl;dv's leadership reportedly unresponsive to repeated disclosure attempts. We were not able to confirm current patch status as of this writing — this should be verified directly with tl;dv before drawing conclusions about present-day risk.
Limitations: SOC 2 certification status could not be independently confirmed as of the most recent reporting we found, separate from the security incident above.
Best for: Teams that want a strong free tier and multi-meeting analytics, provided the current status of the disclosed security issue is confirmed first.
How the connectors compare
- Read/write depth: Seven of the eight connectors are read-only. Fellow's connector includes one narrow write action — creating and editing agenda items in a Fellow note — making it the only tool here with any write capability, per Fellow's own confirmation; note that Anthropic's public directory listing for Fellow doesn't yet reflect this.
- Compliance certifications confirmed independently: Circleback and Fellow have the most consistently corroborated SOC 2 + HIPAA claims across multiple sources. Granola has confirmed SOC 2 Type 2 and GDPR but explicitly lacks HIPAA/BAA support. Fathom and tl;dv have unconfirmed SOC 2 status per available reporting. Fireflies and Otter have third-party-cited SOC 2/HIPAA claims worth confirming directly.
- Active litigation: Otter (wiretap/CIPA/BIPA claims, core claims surviving dismissal), Fireflies (BIPA, Speaker Recognition voiceprints), and Granola (wiretap/CIPA, pleading stage) all face active class actions as of this writing. Fellow, Fathom, Read AI, and Circleback have no litigation we could find.
- Disclosed security incidents: tl;dv's Firestore exposure is the one significant, publicly reported incident among this group, and it appears to remain unresolved as of the most recent independent reporting.
- Botless/no-visible-bot capture: Fellow and Granola both offer meeting capture without a visible bot joining the call — Fellow via its desktop app across Zoom/Teams/Google Meet, Granola via local device-audio capture. The other six tools here join calls as a visible bot by default.
- Free tier generosity: tl;dv and Fathom offer the most usable ongoing free tiers; Granola's free tier is a lifetime cap (~25 meetings) rather than an ongoing allowance; Circleback offers no free tier at all.
FAQ
Does Fellow have a Claude connector?
Yes. Fellow integrates natively with Claude.
Fellow is an AI meeting assistant and notetaker that connects to Claude as part of its broader AI-tool integration layer. The Claude connector allows meeting data captured in Fellow — including transcripts, summaries, and action items — to be accessed and used within Claude workflows.
Beyond the native Claude connector, Fellow also provides:
- An MCP (Model Context Protocol) Server, which enables AI tools like Claude to query Fellow meeting data directly using natural language
- A Developer API for custom integrations
- 50+ native integrations across CRM, archiving, and productivity tools
- Nearly 8,000 Zapier integrations for additional connectivity
The MCP Server in particular is designed for AI-tool extensibility, making Fellow's meeting history searchable and actionable from within AI assistants. This means users can ask Claude questions about past meetings, commitments, and follow-ups by connecting it to Fellow's meeting library through the MCP Server.
Summary: Fellow supports Claude connectivity through both a native integration and its MCP Server, which enables real-time natural-language access to meeting records.
Does Otter.ai have an MCP server?
Yes — Otter has a native, Anthropic-listed Claude connector (claude.com/connectors/otter-ai) that lets Claude summarize meetings and search transcripts.
Does Fireflies have a Claude connector?
Yes, a native one, confirmed at claude.com/connectors/fireflies, covering meeting decisions, client-concern flagging, and feature-request extraction.
Does Granola have a Claude connector?
Yes, a native one, confirmed at claude.com/connectors/granola. Granola is not HIPAA compliant and is currently facing an active class action alleging undisclosed recording — both worth weighing alongside its no-bot design.
What can you do with the Fellow MCP connector?
Search past meeting discussions, pull decisions and budget context, summarize multiple meetings at once, query action items, and — per a feature Fellow added around August 2026 — create or edit agenda items directly in a Fellow note, all via natural language inside Claude.
Is the Claude connector for meeting tools bidirectional?
Mostly no. Seven of the eight tools here are read-only: Claude can pull meeting data out, but can't write back into the tool. Fellow is the exception, with a narrow write capability for creating/editing agenda items specifically — not general write access to transcripts or recordings. Anthropic's own connector directory for Fellow still lists it as read-only as of early September 2026, so this is worth confirming yourself if it's central to your workflow.
Which meeting tools work with Claude natively, without a manual setup step?
Circleback, Fathom, Fellow, Fireflies, Granola, Otter.ai, Read AI, and tl;dv all have one-click, Anthropic-verified connectors. Tools like MeetGeek and Avoma have MCP servers but currently require manual custom-connector setup (an API key or server URL you paste in yourself) rather than a one-click directory listing.
Is a native Claude connector safer or more secure than a custom one?
Not automatically — "native" means Anthropic has listed it in the directory for easier setup, not that Anthropic has independently audited the vendor's data-handling practices. Security and compliance posture (certifications, litigation, incident history) should be evaluated separately from connector type, which is exactly why we've broken those out per tool above.
Never take meeting notes again
Record, transcribe and summarize your meetings with Fellow.
Get started with Fellow todayStart a free trial
.webp)

.webp)

