Fathom for AI agents
Fathom is an AI meeting assistant that records, transcribes, and summarizes calls, giving teams searchable notes after every meeting instead of relying on manual note-taking. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Fathom.
Pull a meeting's summary
Get a recording's summary to share key takeaways with someone who missed the call.
Read a meeting transcript
Get a recording's full transcript to search for a specific commitment made during the call.
Read-only meeting history
List meetings as a read-only step before pulling the transcript for a specific one.
7 Fathom actions, graded by risk.
Every Fathom action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- fathom.list_teamsList Teams
- fathom.list_meetingsList Meetings
- fathom.list_team_membersList Team Members
- fathom.get_recording_summaryGet Recording Summary
- fathom.get_recording_transcriptGet Recording Transcript
write
1Create and change things. Allow, or ask the user first.
- fathom.create_webhookCreate webhook for meeting content
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- fathom.delete_webhookDelete Webhook
Fathom in three steps.
- 01Your users connect FathomThey sign in to Fathom on Arc0 Connect, under your brand, and approve the access you ask for.
- 02You set the rulesReads run, writes like “create webhook for meeting content” can wait for the user, and “delete Webhook” can be denied outright.
- 03Any agent can actYour agent calls Fathom through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('fathom', { read: 'allow', write: 'ask', // create_webhook destructive: 'deny', // delete_webhook }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Fathom connects.
Users sign in to Fathom on Arc0 Connect and approve the scopes you request. Build with Arc0’s Fathom OAuth app, or bring your own so the Fathom consent screen names you. Tokens refresh automatically, and you can export them whenever you want.
The same Fathom connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key · OAuth 2.0
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Fathom from any agent.
Fathom and Arc0, answered.
Can I use Fathom with Claude, ChatGPT or Cursor?
Yes. Connect Fathom to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Fathom actions you allow.
How do users connect Fathom?
Users sign in to Fathom on Arc0 Connect and approve the scopes you request. Build with Arc0’s Fathom OAuth app, or bring your own so the Fathom consent screen names you. Tokens refresh automatically, and you can export them whenever you want.
Which Fathom actions can my agent take?
7 in total: 5 read, 1 write and 1 destructive, such as “create webhook for meeting content”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Fathom?
Yes. Actions like “delete Webhook” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Fathom too?
Yes. The same Fathom connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Fathom into your agent.
Your users connect Fathom once, under your brand. Your agent gets 7 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan