Skip to main content
Fathom is a branded card in the Integrations gallery, in the Meetings category — Fathom’s own hosted MCP server, with the address and authentication already fixed by the card. An Org Admin adds the card to your organization; then each member connects their own Fathom account from My Integrations. There’s nothing to type.

​
What it gives the agent

Once you’ve connected and the integration is enabled on a project, the agent can search your recorded meetings and read their transcripts, summaries and action items, and answer questions in plain language (“what did we decide about the rollout on Tuesday’s call?”). Only meetings your Fathom account can already see are available. Fathom offers a single permission, mcp, and it cannot be narrowed. Fathom describes the connector as read-only, and Parlé’s card describes it as being for reading your meetings. Parlé has no approval step for tool calls, so each call runs as soon as the agent makes it, under the member whose conversation made the call.
Read this before you connect. Anything the agent reads from a meeting can appear in the project conversation, which every member of that project can see. A recording or transcript may contain other people’s words, including client-confidential or privileged material. You are responsible for having recorded those meetings lawfully and with the consent of the other participants; Parlé does not ask them, and their words may be surfaced to the agent and the project.

​
Choosing a scope

Fathom is User scope only. A recording is one person’s data, so each member connects their own Fathom account, and the integration cannot be shared organization-wide or project-wide. Parlé won’t register Fathom at Organization or Project scope. See Choosing who the credential belongs to for what User scope means, including the fan-out consequence.

​
Connecting

1

An Org Admin adds Fathom

An Org Admin goes to Org settings → Integrations → Tools, selects Add integration, and chooses the Fathom card. Only an Org Admin can add an integration to the organization.
2

Enable it on a project

A Project Admin switches Fathom on for the project from its Tools tab (see Part 3).
3

Each member connects their own account

Each member opens My Integrations, reads the warning beside Connect, and approves access at Fathom.
The connect flow is the same as any OAuth 2.0 integration — see Part 2 — Authentication for what Reconnect required and Reconnect recommended mean. A member who hasn’t connected yet gets a plain-language prompt to do so from My Integrations.
You’ll need: a Fathom account that can view the meetings you want the agent to read. Fathom’s own documentation doesn’t state a plan requirement for its MCP server. If you use Fathom through a team, check with your Fathom admin whether connectors are enabled.

​
Reconnecting and access renewal

Parlé renews Fathom’s access automatically in the background. If Fathom stops accepting the stored authorization, the card shows Reconnect required and Fathom stops working for you until you approve access again from My Integrations.

​
Disconnecting

Select Disconnect on your Fathom card in My Integrations. This deletes your stored credential from Parlé’s vault and removes your connection, so Parlé can no longer call Fathom for you. Fathom doesn’t offer a way for Parlé to revoke access on its side, so Parlé can’t withdraw it there. The access Fathom issued to Parlé may stay listed in your Fathom account, and may remain valid until it expires or you remove it. To end it at Fathom, remove Parlé’s access yourself: Fathom’s public documentation doesn’t say where in its settings to do this, so if you can’t find Parlé in your Fathom account’s connected apps, contact Fathom support at help@fathom.video. Removing the whole integration for your organization starts the same 14-day grace window as any other integration. See Part 5 — Maintaining an integration.