# 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.

Source: https://elaichi.ai/connectors/fathom/

## Facts

| | |
| --- | --- |
| Application | Fathom |
| Category | Conversational Intelligence |
| AI tools | 7 |
| Authentication | OAuth or API key |
| Needs your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | Yes |

## What you can ask once Fathom is connected

- 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

## Connect Fathom in Elaichi

This happens once for the organization, before any client is involved.

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

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Fathom tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Connect Fathom to Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

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

## Connect Fathom to ChatGPT

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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.

## Connect Fathom to Cursor

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## Connect Fathom to any MCP client

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Fathom tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Fathom through Elaichi

### Catch up on a call you missed

Sales. 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.

### Prepare for a renewal conversation

Customer Success. 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.

### Turn a troubleshooting call into a ticket

Support. 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.

### Find what customers said about a feature

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

### See what the team recorded this week

Leadership. 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.

### Send new recordings to another system

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

## 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 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.

### 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.

## All 7 Fathom tools

Every tool below is callable through https://api.elaichi.ai/mcp once Fathom is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Fathom teams** (List). List teams in Fathom. Returns an array of teams where each team includes the fields name and created_at.
- **List all Fathom team members** (List). List team members in Fathom. Returns name, email, and created_at for each team member in the response.
- **List all Fathom meetings** (List). List meetings in Fathom. Returns key fields for each meeting including title, meeting_title, url, share_url, created_at, scheduled_start_time, scheduled_end_time, recording_start_time, recording_end_time, meeting_type, transcript_language, calendar_invitees, recorded_by, transcript, default_summary, action_items, and crm_matches.
- **Delete a Fathom webhook by ID** (Delete). Delete a webhook in Fathom using id. Returns no content if the webhook is deleted successfully.
- **Create a Fathom webhook** (Create). Create a webhook in Fathom to receive new meeting content. Requires destination_url and triggered_for. At least one of include_transcript, include_crm_matches, include_summary, or include_action_items must be true. Returns id, url, secret, created_at, include settings, and triggered_for in the response.
- **List all Fathom recording summary** (List). Get summary for a specific recording in Fathom using id. Returns template_name and markdown_formatted fields describing the meeting summary. If destination_url is sent, summary will be POSTed asynchronously.
- **List all Fathom recording transcript** (List). Get the transcript for a specific recording in Fathom using recording_id. Returns an array of transcript items containing speaker details (display_name, matched_calendar_invitee_email), spoken text, and timestamp.