Fathom MCP integration
AI meeting assistant for recordings, summaries, transcripts, teams, and meeting webhooks.
Sign in, add Fathom in Apps, then choose the account your AI can use.
Tools
| Name | Description |
|---|---|
validate_connectionValidate the Fathom API key with a minimal authenticated request. | Validate the Fathom API key with a minimal authenticated request. |
list_meetingsList Fathom meetings with official filters, cursor pagination, and optional transcript/summary/action item fields. | List Fathom meetings with official filters, cursor pagination, and optional transcript/summary/action item fields. |
find_meetingsFind Fathom meetings by date range, recorder, team, meeting type, or invitee domain. | Find Fathom meetings by date range, recorder, team, meeting type, or invitee domain. |
get_recording_summaryGet the Fathom AI summary for a recording directly as JSON. | Get the Fathom AI summary for a recording directly as JSON. |
get_recording_transcriptGet the speaker-attributed transcript for a Fathom recording directly as JSON. | Get the speaker-attributed transcript for a Fathom recording directly as JSON. |
list_meeting_typesList Fathom meeting type names and statuses for use with meeting filters. | List Fathom meeting type names and statuses for use with meeting filters. |
list_teamsList Fathom teams visible to the API key. | List Fathom teams visible to the API key. |
list_team_membersList Fathom team members, optionally filtered by team name. | List Fathom team members, optionally filtered by team name. |
Triggers
| Name | Description |
|---|---|
webhook_event_receivedReceive Fathom new-meeting-content webhook payloads from a manually configured Fathom webhook. | Receive Fathom new-meeting-content webhook payloads from a manually configured Fathom webhook. |
new_meeting_content_readyAutomatically create a Fathom webhook and trigger when new meeting content is ready. Signature verification requires raw request bodies and is not performed by this trigger runtime. | Automatically create a Fathom webhook and trigger when new meeting content is ready. Signature verification requires raw request bodies and is not performed by this trigger runtime. |
Quick Start
import { WeavzClient } from '@weavz-io/sdk'
const weavz = new WeavzClient({ apiKey: 'wvz_...' })
const result = await weavz.actions.execute('fathom', 'validate_connection', {
workspaceId: '550e8400-e29b-41d4-a716-446655440000',
integrationAlias: 'fathom',
input: { /* ... */ },
})Related Integrations
Works well with
Frequently Asked Questions
Is there a Fathom MCP server through Weavz?
Yes. Add the Fathom integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 8 Fathom actions.
What can an AI agent do with Fathom?
Available actions include Validate Connection, List Meetings, Find Meetings, Get Recording Summary, Get Recording Transcript, and more. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.
How do I connect Fathom to Claude or ChatGPT?
Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add Fathom, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.
Can I use Fathom through an API or SDK?
Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.
What authentication does Fathom require?
The catalog lists custom credentials for Fathom. Use Hosted Connect to authorize the intended account. Required permissions, provider app access and available connection methods depend on the integration.
How do I review sensitive Fathom actions?
Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.
What limits or costs apply to Fathom?
Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.
What Fathom triggers are available?
The catalog lists 2 triggers, including Webhook Event Received, New Meeting Content Ready. Configure the trigger and your event handler before using incoming events to start work.
Connect Fathom in minutes
Get 20,000 free action executions every month. No credit card required.