Connectors · Marketing & media

Fathom MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Fathom and the rest of your systems. It gives your agent 11 Fathom actions (8 reads, 2 writes and 1 that wait for a confirmation) and holds the Fathom credential itself, so the agent never does. It paces Fathom's limits and records every call.

Connect Fathom free See pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp

11actionsin one signed file
8readlook, never change
2writecreate and update
1wait for a yesdestructive, confirmed first

Set up

Connect Fathom in three steps.

01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp
02
Connect Fathom.
API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
- api_keyFathom API key
```
account { op: "connections.requirements", service: "fathom" }
# free: exactly what to paste, and what is found for you
```

Make the first call. Check before a write.

Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

do    { action: "fathom.users.list" }# list users and their permissions · read · 1 upstream callcheck { action: "fathom.webhooks.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Fathom at a glance

Sign-in: API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide: api_key
Limits we pace to: 60 calls a minute, per connection
API covered: Fathom External API v1 (OpenAPI 3.1.1)api.fathom.ai/external/v1
Built from: Fathom's documentation, read 23 October 2026developers.fathom.ai developers.fathom.ai
Service file: Version 1.0.0, signed (Ed25519)
Cached reads: 7 of 8 reads, for up to 5 minutes; a write clears what it affects
Shared entities: 4, so ask can line Fathom up with your other systems
Data: Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Fathom.

11 actions in 8 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

8readlook, never change
2writecreate and update
1destructivewait for a confirmation

Recording downloads
2
1 read · 1 write · 0 destructive
Get a recording download's status · Request a recording download
Recordings
2
2 read · 0 write · 0 destructive
Get a recording's summary · Get a recording's transcript
Webhooks
2
0 read · 1 write · 1 destructive
Create a webhook · Delete a webhook
Meeting types
1
1 read · 0 write · 0 destructive
List meeting types
Meetings
1
1 read · 0 write · 0 destructive
List meetings
Team members
1
1 read · 0 write · 0 destructive
List team members
Teams
1
1 read · 0 write · 0 destructive
List teams
Users
1
1 read · 0 write · 0 destructive
List users and their permissions

Top actions

The Fathom API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 6 of Fathom's 6 action names are shared with at least one other connector, so an agent learns them once.

Action	What it does	Effect	Same name in
`fathom.users.list`List users and their permissions	List users and their permissions.	read	`identity.user.list`474 connectors
`fathom.teams.list`List teams	List teams.	read	`identity.group.list`262 connectors
`fathom.team_members.list`List team members	List team members.	read	`identity.group_member.list`103 connectors
`fathom.meetings.list`List meetings	List meetings.	read	`comm.meeting_recording.list`11 connectors
`fathom.webhooks.create`Create a webhook	Create a webhook.	write	`automation.webhook.create`209 connectors
`fathom.webhooks.delete`Delete a webhook	Delete a webhook.	destructive	`automation.webhook.delete`211 connectors
`fathom.meeting_types.list`List meeting types	List meeting types.	read	this connector
`fathom.recordings.get_summary`Get a recording's summary	Get summary.	read	this connector
`fathom.recording_downloads.get`Get a recording download's status	Get download status.	read	this connector
`fathom.recordings.get_transcript`Get a recording's transcript	Get transcript.	read	this connector
`fathom.recording_downloads.create`Request a recording download	Request a download.	write	this connector

Try it

Prompts to paste into Claude.

Each one names the Fathom actions it will call, so you know what it reads and what it changes before you send it.

Readread
Who has access in Fathom? List every user and their role.
callsfathom.users.list
Writewrite
Create a webhook in Fathom. Show me exactly what you will send before you save it.
callsfathom.webhooks.create

Governance for Fathom

Destructive actions wait for a yes.

1 Fathom action is destructive. This is it:

Delete a webhookfathom.webhooks.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dofathom.webhooks.deleteconfirm_policy: human

Delete a webhook?

intent: the user asked me to delete a webhook

run suspended · waiting for a named person · key fathom-agent cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

account {  op: "keys.create", name: "fathom-agent",  allowed_actions: ["fathom.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "fathom.webhooks.delete", approver: "[email protected]" }  ]}

Illustrative. Scoped to Fathom only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Fathom costs on actionlake.

Every Fathom action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Fathom refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

1upstream call per actionall 11 Fathom actions
11actions pageeach page of a long list is one call
7reads can be cacheda cache hit costs nothing
100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Fathom action.

11 actions by area: the id your agent calls, what it does, and its effect.

Recording downloads2

fathom.recording_downloads.createRequest a recording downloadwrite
fathom.recording_downloads.getGet a recording download's statusread

Recordings2

fathom.recordings.get_summaryGet a recording's summaryread
fathom.recordings.get_transcriptGet a recording's transcriptread

Webhooks2

fathom.webhooks.createCreate a webhookwrite
fathom.webhooks.deleteDelete a webhookdestructive

Meeting types1

fathom.meeting_types.listList meeting typesread

Meetings1

fathom.meetings.listList meetingsread

Team members1

fathom.team_members.listList team membersread

Teams1

fathom.teams.listList teamsread

Users1

fathom.users.listList users and their permissionsread

Questions

The Fathom MCP server, answered.

Is there a Fathom MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 11 Fathom actions across recording downloads, recordings, webhooks and meeting types, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Fathom.

What do I need to connect Fathom?

Fathom API key. The free call account { op: "connections.requirements", service: "fathom" } lists exactly what to paste.

Can an AI agent delete or change things in Fathom?

Only if its key allows it, and only with an explicit confirmation. 1 Fathom action is destructive, including delete a webhook. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Fathom API limit?

actionlake paces every call to the limits in the Fathom service file: 60 calls a minute per connection. Repeated reads are answered from cache (7 Fathom actions can be), which never reaches Fathom.

What does a Fathom action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (11 Fathom actions page). Cache hits, searches, dry runs and calls Fathom refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Fathom API does it cover?

The Fathom External API v1 (OpenAPI 3.1.1) at api.fathom.ai/external/v1. It is built from Fathom's documentation as read on 23 October 2026. 11 actions in 8 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Fathom data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Fathom credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Fathom today.

Connect Fathom free See pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

Fathom MCP server for AI agents.

Connect Fathom in three steps.

Add actionlake to Claude.

Connect Fathom.

Make the first call. Check before a write.

What an AI agent can do in Fathom.

Recording downloads

Recordings

Webhooks

Meeting types

Meetings

Team members

Teams

Users