Fathom MCP connector
The Fathom connector brings your recorded meetings, summaries and transcripts into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can ask about calls they already have access to and every request is logged.
- OAuth or API key
- Free 14-day trial
- No credit card
Claude
Elaichi connected
Summarize this week's Fathom meetings for the Sales team
Working in Fathom with Elaichi
-
List all Fathom teams
-
-
Governance
/
Audit log
Last 24 hours
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
ChatGPT · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Fathom to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
Fathom MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Fathom through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Fathom is logged.
-
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”
What connecting Fathom gets you
6 screens from Elaichi, each doing one job for your Fathom account.
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, Cursor or Microsoft Copilot
The agent
Ask about meetings, get answers back.
Plain language questions answered from live Fathom meetings, summaries and transcripts.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Fathom.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiToolsTool catalog
11 Fathom tools ready to call.
Meetings, teams, members, summaries, transcripts and webhooks, with no custom code.
ElaichiToolboxesToolboxes
Every team gets its own toolbox.
Curate which Fathom tools Sales, Support and Research each see.
ElaichiConnectionsShared connections
Teammates use Fathom without a credential.
See who connected each Fathom account and which teams and members share it.
ElaichiAudit logAudit log
Every Fathom call is on the record.
When, who, what happened, type and resource for each transcript and meeting read.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Fathom digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
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 Jake Morgan
Approve Deny -
Post the digest
Fathom
Queued
Automations
A schedule turns meetings into a digest.
Fathom meetings are fetched, grouped, drafted by an agent, approved, then posted back.
Fathom health
Refreshed 4 minutes ago · every 15 minutes · from the meetings collection
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%
Collections and dashboards
Fathom meeting numbers arrive without asking.
Four metrics, 14 days of recordings and a team breakdown, refreshed on schedule.
For IT and engineering
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.
| 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 | Free for one person; $15 per user per month on Gold. | 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.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 restrict creating or deleting Fathom notifications and leave reading meetings, summaries and transcripts open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot