Fathom

Search meetings and read AI summaries and verbatim transcripts.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Fathom connector does

The Fathom MCP server connects a Fathom meeting archive — recordings, AI summaries, action items and verbatim transcripts — to Claude, ChatGPT, Claude Code and any MCP-compatible agent. Anthropic's directory lists seven tools and every one reads. Sign-in is OAuth with dynamic client registration, under a single scope named mcp.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Fathom tools (7)

  • get_identity
  • list_teams
  • list_meetings
  • get_meeting_summary
  • get_meeting_transcript
  • find_person
  • search_meetings

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Fathom publishes no tool list for this server. The seven names come from Anthropic's directory. Fathom's four MCP documentation pages, its help article, its changelog and its OpenAPI document name none of them, so no two-way diff was possible. Fathom's help article does confirm the
  • One OAuth scope, and it separates nothing. Both Fathom's RFC 9728 resource descriptor and its authorization server metadata advertise scopes_supported as the single value mcp, observed live on 2026-08-22. There is no scope for meeting metadata versus verbatim transcripts. The only place to narrow access is the per-tool toggles in your MCP client.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so readOnlyHint, destructiveHint and every parameter name are unknown. The parameter detail on this page is inferred from Fathom's matching REST endpoints — that mapping is ours, not Fathom's.
  • The connector inherits your Fathom permissions and adds none of its own. It reaches meetings you recorded and meetings shared with you or your team. Where an admin has been granted view access to all shared calls, connecting an agent hands it that same reach in one grant.
  • Summaries are English-only and single-template. Fathom's schema states summaries are always displayed in English whatever language the call was in, and its FAQ states the API returns your account's default summary template with no way to request another or to get more than one.
  • Rate limits are documented for the REST API, not for MCP. Fathom publishes 60 calls per 60 seconds globally; summary and transcript reads are classed as heavy at 30 per 60 seconds, reduced to as low as 5 during elevated activity. Whether the MCP server shares those ceilings is not stated. A transcript-heavy agent session is the case most likely to hit them.
  • Pagination is fixed at ten. Fathom's FAQ states the default page size is 10 meetings with no parameter to raise it, so broad questions across a long archive mean many cursor round-trips against the limits above.
  • Nothing here shares, deletes or writes. If you wanted an agent that files the follow-up or updates the CRM record, this connector cannot do it; Fathom's own automations, CRM sync and webhooks are the paths for that, and they run on meeting completion rather than on a tool call.
  • destination_url exists one layer down. Fathom's REST summary and transcript endpoints accept a URL and POST the content there instead of returning it. We have no evidence the MCP tools expose it and could not read their schemas to rule it out. Check the tool inputs once connected.
  • Whether reading a transcript is logged or visible to the meeting host is unresolved. We found no Fathom documentation stating whether connector access is surfaced anywhere, and we did not test it. Treat it as unknown rather than as a no.

Frequently asked questions

How many tools does the Fathom MCP server have?

Seven, and Fathom corroborates the number without ever naming them. Anthropic's directory lists get_identity, list_teams, list_meetings, get_meeting_summary, get_meeting_transcript, find_person and search_meetings. Fathom's own help article says each of the 7 tools has its own on/off toggle inside the connector settings, which confirms the count from the vendor side while publishing no enumeration to diff against.

Can the Fathom MCP connector share a recording or send a follow-up email?

No. All seven listed tools read. No name carries a share, send, create, update or delete verb, and no tool takes a recipient or destination parameter. Fathom does auto-share summaries and recordings with calendar attendees, but that fires when a meeting finalizes, not on a tool call, so an agent cannot start it.

Can an AI agent read other people's speech through Fathom?

Yes, verbatim and speaker-attributed. get_meeting_transcript returns the transcript, and Fathom's transcript schema pairs every line with a speaker display name, a timestamp and, where it matches a calendar invitee, that person's email address. Everyone in the room consented to Fathom recording, not necessarily to an AI agent replaying what they said.

What OAuth scopes does the Fathom MCP server request?

Exactly one, called mcp, and it separates nothing. Fathom's RFC 9728 resource descriptor and its authorization server metadata both advertise scopes_supported as that single value, confirmed live on 2026-08-22. There is no scope for meeting titles versus verbatim transcripts, so narrowing has to happen client-side using the per-tool toggles.

What meetings can the Fathom connector see?

Only meetings you can already open in Fathom. The help article states the integration accesses meetings you have permission to view and adds no new categories of data. Fathom's API FAQ is more precise about the same boundary: meetings you recorded plus meetings shared with you or your team, never another user's private unshared calls.

Do I need a paid Fathom plan for the Claude connector?

No. Fathom's Claude integration page states the connector works on every plan, its API FAQ says API access is included on all plans, and the pricing comparison lists Public API and MCP without a plan restriction. The Free individual plan includes unlimited recordings and transcription, so a free account has meetings for the connector to read.

Why does Fathom show as connected in Claude but return no meetings?

Almost always because the tools are not enabled in that specific conversation. Fathom lists three causes: the connector is toggled off in the chat's Tools panel, the chat was started before you connected so its tool list never reloaded, or individual tools were switched off in the connector settings. Open a fresh conversation and confirm each of the 7 tools is on.

Does the Fathom MCP server cost money or consume a usage quota per call?

No call spends money or credits. Fathom bills per user per month, not per request, and the connector adds no metered operation. Rate limits do apply on Fathom's API side — 60 calls a minute overall, dropping to 30 for summary and transcript reads and as low as 5 under load — but Fathom publishes no MCP-specific ceiling and no tool reports usage.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Fathom to work.

Connect Fathom once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio