Can my team share one Fathom connection?

Yes. One person connects Fathom in Elaichi and shares the connection with a team, and nobody else ever handles the API key or sign-in. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who read a transcript, not the connection.

Conversational Intelligence

Fathom MCP connector

The Fathom connector brings your recorded meetings, summaries and transcripts into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask about calls they already have access to and every request is logged.

Connect on Elaichi How to connect

How it connects. OAuth or API key. The credential goes into a vault nobody reads back.
One address. https://api.elaichi.ai/mcp, the same for every user.
Their own access. An agent never gets more than the person it acts for.

11 tools

How to connect

How to connect Fathom to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Fathom once

Open Connections, choose Add connection, and pick Fathom.
Optionally set Share with to give a team access, then press Connect.
Approve it in Fathom. Fathom's own window opens. Whoever approves it decides what this connection can reach.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

fathom

All categories

Fathom

Anthropic

AssemblyAI

Chorus

Circleback

Fellow

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Fathom MCP connector for Claude

1

Open Customize, then Connectors.
2

Press Add.
3

Name it, paste the MCP server URL, then Continue.

https://api.elaichi.ai/mcp
4

Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Fathom MCP connector for ChatGPT

1

Open Plugins, then press the + button.
2

Name it and paste the endpoint into Server URL.

https://api.elaichi.ai/mcp
3

Leave Authentication on OAuth, then tick the risk acknowledgement.
4

Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Fathom MCP connector for Cursor

1

Open ~/.cursor/mcp.json.
2

Add the endpoint under mcpServers.

https://api.elaichi.ai/mcp
3

Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Fathom to any MCP client

1

Add the endpoint as a remote MCP server.

https://api.elaichi.ai/mcp
2

Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Connect Fathom on Elaichi See pricing

Use cases

What teams do with Fathom through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

Sales

Catch up on a call you missed

Ask for the summary and transcript of yesterday's discovery call with a prospect, then pull out the objections, the budget comment and the next step the rep promised.
Customer Success

Prepare for a renewal conversation

Gather the last three calls with an account, read what the customer asked for each time, and walk into the renewal knowing which promises are still open.
Support

Turn a troubleshooting call into a ticket

Take the transcript of a screen-share session with a customer and draft a clear write-up of the problem, the steps tried and what was agreed.
Product

Find what customers said about a feature

Search across recent customer call summaries for mentions of a specific feature or complaint, and collect the exact quotes for the roadmap discussion.
Leadership

See what the team recorded this week

List the meetings each team member recorded this week, read the summaries, and spot the deals or accounts that need a second look before the pipeline review.
Operations

Send new recordings to another system

Set up a notification so that each finished Fathom recording is announced to another connected application, and remove it when the workflow changes.

Try asking

“Summarize this week's Fathom meetings for the Sales team”
“Which Fathom team members ran the most meetings last month?”
“Pull the transcript from yesterday's customer call”

See all 11 Fathom tools below

Compare

Elaichi vs Zapier MCP vs Composio for Fathom

All three can connect Fathom to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Fathom, by what to check
What to check	Elaichi	Zapier MCP	Composio
Where the AI connects	One address for the whole organization. `https://api.elaichi.ai/mcp`	A server per member, created at sign-in.	An MCP endpoint per team, or an SDK.
Control over Fathom tools	Allow or restrict single Fathom tools, per role or user.	App and action restrictions on the account.	Role permissions, down to the action.
Record of calls	One audit entry per Fathom call.	A History tab of tool calls.	A log of every tool call.
Single sign-on	SAML or OIDC, plus SCIM, on Gold.	SAML on Enterprise.	SAML and OIDC on Enterprise.
Price	$15 per user per month.	2 tasks per successful call.	Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Fathom tools for your AI agents

11 tools are ready to call through Elaichi's MCP endpoint the moment you connect Fathom, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Fathom gets you

6 screens from the product, each doing one job for your Fathom account.

The agent

Ask about meetings, get answers back.

Plain language questions answered from live Fathom meetings, summaries and transcripts.

meetings
transcripts
summaries
teams

Ask Elaichi to work across your apps.

Summarize this week's Fathom meetings for the Sales team

Which Fathom team members ran the most meetings last month?

Pull the transcript from yesterday's customer call

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Fathom.

One governed MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients

Claude

ChatGPT

Cursor

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emily Carter	• Connected	4 minutes ago
Cursor	M Megan Brooks	• Connected	2 hours ago
ChatGPT	R Ryan Hayes	• Connected	Yesterday

Tool catalog

11 Fathom tools ready to call.

Meetings, teams, members, summaries, transcripts and webhooks, with no custom code.

List all Fathom teams
List all Fathom team members
List all Fathom meetings
Delete a Fathom webhook by ID

ElaichiTools

Tool	Action	Description
List all Fathom teams	List	List the teams in your fathom account. Returns team records including their id and team-specific attributes; the team names returned here are the values accepted by the teams[] filter on other endpoints.
List all Fathom team members	List	List Fathom team members. Returns a paginated list of member records, each with an id and attributes containing the upstream-defined team-member fields.
List all Fathom meetings	List	List Fathom meetings recorded across your org, filterable by company domain, meeting type, recorder, and team. Returns each meeting with its id, recording_id, and created_at, plus optional action_items, highlights, summary, and transcript sections when the matching include flags are set.
Delete a Fathom webhook by ID	Delete	Delete a Fathom webhook by id. Returns an empty 204 response on success. Required: id.
Create a Fathom webhook	Create	Create a Fathom webhook to receive new meeting content. Returns the created webhook object including its id, destination_url, triggered_for, and include flags. Required: destination_url, triggered_for. At least one of include_transcript, include_crm_matches, include_summary, or include_action_items must be true.

Toolboxes

Every team gets its own toolbox.

Curate which Fathom tools Sales, Support and Research each see.

Sales
Customer Success
Support
Product Research

ElaichiToolboxes

Name	Source template	Tools	Created
Sales toolbox Fathom · deal calls and follow ups	Fathom starter	18	Mar 4, 2026
Customer Success toolbox Fathom · renewal and check in meetings	—	9	Mar 2, 2026
Support toolbox Fathom · escalation call transcripts	—	24	Feb 27, 2026
Product Research toolbox Fathom · discovery interview summaries	Fathom starter	6	Feb 19, 2026
Marketing toolbox Fathom · customer story quotes	—	31	Jan 30, 2026
Revenue Operations toolbox Fathom · team and meeting reporting	—	12	Jan 22, 2026

Shared connections

Teammates use Fathom without a credential.

See who connected each Fathom account and which teams and members share it.

Sales EMEA
Sales AMER
Customer Success
Support

ElaichiConnections

Connection	Scope	Status	Access
FA Fathom (Sales EMEA) Connected by Emily Carter	Personal	• Active	1 team · 6 members
FA Fathom (Sales AMER) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
FA Fathom (Customer Success) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
FA Fathom (Support) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
FA Fathom (Product Research) Connected by Ryan Hayes	Personal	• Active	Not shared
FA Fathom (Marketing) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit log

Every Fathom call is on the record.

When, who, what happened, type and resource for each transcript and meeting read.

When
Who
What happened
Type

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter emily.carter@northwind.io	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan jake.morgan@northwind.io	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks megan.brooks@northwind.io	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed tyler.reed@northwind.io	Fathom Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes ryan.hayes@northwind.io	Fathom Meetings Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker ashley.parker@northwind.io	Fathom Meetings List	Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns meetings into a digest.

Fathom meetings are fetched, grouped, drafted by an agent, approved, then posted back.

Fathom digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

Run now

✓

Schedule

Every weekday at 8:00 AM

0.2s
✓

Fetch meetings

Fathom

1.4s
✓

Group by owner

Transform

0.1s
✓

Draft the digest

Agent step

Ran with 4 tools, returned a structured summary

6.2s
Approve the digest

Needs approval

Assigned to Michael Brennan

Approve Deny
Post the digest

Fathom

Queued

Collections and dashboards

Fathom meeting numbers arrive without asking.

Four metrics, 14 days of recordings and a team breakdown, refreshed on schedule.

Fathom health

Refreshed 4 minutes ago · every 15 minutes · from the meetings collection

Live

Meetings

1,284 ↓ 12%

Transcripts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Meetings created

Last 14 days

By team

Share of activity

Sales EMEA 34%

Sales AMER 27%

Customer Success 21%

Support 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Fathom to Claude?

Connect Fathom in Elaichi first: Fathom either opens its own sign-in screen for you to approve, or you paste an API key from your Fathom settings, and there is no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. From that point Claude can read your Fathom meetings, summaries and transcripts as you.

Does Fathom work with ChatGPT and Cursor as well as Claude?

Yes. Once Fathom is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Fathom once and every client you use picks it up.

What can an AI agent actually do with my Fathom data?

Through this connector an agent can list your Fathom meetings, read the summary of any recording, read the full transcript, and see the teams and team members in your Fathom account. It can also set up or remove a notification that tells another application when a new Fathom recording is ready. It cannot delete meetings or edit recordings.

Does connecting Fathom give the AI every meeting in the company?

No. The AI sees only the Fathom meetings the signed-in person can already open, because every request runs under that person's own Fathom access. Elaichi can narrow that further, for example to summaries only, but it can never widen it beyond what the person already has in Fathom.

Can I stop an agent from deleting or changing things in Fathom?

Yes. Restrictions in Elaichi apply per action, so you can block creating or deleting Fathom notifications and leave reading meetings, summaries and transcripts open. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client, so no prompt can reach it.

What happens to a Fathom connection when someone leaves?

Offboarding the person in Elaichi ends their access to Fathom through every client at once. If they had shared a Fathom connection with a team, it keeps working for everyone else. Disconnecting Fathom once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Does the Fathom MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Fathom is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Fathom?

Yes. Both let Claude, ChatGPT or Cursor use Fathom. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Fathom call.

How is Elaichi different from Composio for Fathom?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Fathom: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Fathom in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Fathom Talk to us

Works with: and any other MCP client, or the Elaichi Agent.
When the trial ends: Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.