Skip to main content
Glama
Fathom MCP Server

Fathom MCP Server

by lukas-bekr

Fathom MCP Server

An MCP (Model Context Protocol) server that enables LLMs to interact with the Fathom.video API for meeting recording management, transcripts, summaries, and analytics.

Features

  • List and filter meetings - Access your Fathom meeting recordings with powerful filtering

  • Get transcripts and summaries - Retrieve AI-generated summaries and full transcripts

  • Team management - List teams and team members in your organization

  • Webhook management - Create and delete webhooks for real-time notifications

  • Search meetings - Full-text search across meeting content

  • Analytics - Get meeting statistics and participant insights

Related MCP server: Fathom MCP Server

Installation

# Clone or download the repository
git clone <repository-url>
cd fathom-mcp

# Install dependencies
npm install

# Build the project
npm run build

Configuration

Get Your Fathom API Key

  1. Log in to Fathom

  2. Go to Settings > API

  3. Generate or copy your API key

Claude Desktop Setup

Add the following to your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "fathom": {
      "command": "node",
      "args": ["/absolute/path/to/fathom-mcp/dist/index.js"],
      "env": {
        "FATHOM_API_KEY": "your-api-key-here"
      }
    }
  }
}

Environment Variable

Alternatively, set the environment variable:

export FATHOM_API_KEY=your-api-key-here

Available Tools

Core API Tools

Tool

Description

fathom_list_meetings

List meetings with filtering by date, team, domain, recorder

fathom_get_summary

Get AI-generated summary for a recording

fathom_get_transcript

Get full transcript with speaker identification

fathom_list_teams

List all teams in your organization

fathom_list_team_members

List members of a specific team

fathom_create_webhook

Create a webhook for meeting notifications

fathom_delete_webhook

Delete an existing webhook

Helper Tools

Tool

Description

fathom_search_meetings

Search across meeting titles, transcripts, and summaries

fathom_meeting_stats

Get analytics: duration stats, team breakdown, meeting types

fathom_participant_stats

Get participant frequency and domain analysis

Usage Examples

List Recent Meetings

"Show me my recent meetings"

Get Meeting Summary

"Get the summary for recording 123456789"

Search Meetings

"Search my meetings for discussions about 'quarterly budget'"

Filter by Team

"List all Sales team meetings from last month"

Get Analytics

"Show me meeting statistics for this quarter"

Create a Webhook

"Create a webhook to https://my-app.com/webhook for my recordings"

Response Formats

All tools support two response formats:

  • markdown (default): Human-readable formatted output

  • json: Structured data for programmatic processing

Specify the format using the response_format parameter.

Rate Limits

The Fathom API has a rate limit of 60 requests per minute. The server handles rate limiting gracefully and will return an error message if the limit is exceeded.

Development

# Install dependencies
npm install

# Development with auto-reload
npm run dev

# Build
npm run build

# Type checking
npm run typecheck

# Run the server
npm start

Project Structure

fathom-mcp/
├── src/
│   ├── index.ts           # Main entry point
│   ├── types.ts           # TypeScript interfaces
│   ├── constants.ts       # Configuration constants
│   ├── schemas/           # Zod validation schemas
│   ├── services/          # API client
│   └── tools/             # Tool implementations
├── dist/                  # Compiled output
├── package.json
├── tsconfig.json
├── PRD.md                 # Project requirements
├── CHANGELOG.md           # Version history
└── README.md

Error Handling

The server provides clear, actionable error messages:

  • 401: Authentication failed - check your API key

  • 404: Resource not found - verify the recording ID

  • 429: Rate limit exceeded - wait before retrying

  • Network errors: Connection issues with Fathom API

License

MIT

Available Tools

10 tools
fathom_create_webhookCreate Fathom WebhookA

Create a webhook to receive real-time notifications when meetings are processed in Fathom.

This tool creates a webhook subscription that will POST meeting data to your specified URL whenever new meeting content becomes available.

Args:

  • destination_url (string, required): The URL to receive webhook notifications

  • triggered_for (string[], required): At least one trigger type:

    • 'my_recordings': Your private recordings and those shared with individuals

    • 'shared_external_recordings': Recordings shared with you by external users

    • 'my_shared_with_team_recordings': Your recordings shared with teams

    • 'shared_team_recordings': Team recordings accessible to you

  • include_action_items (boolean): Include action items in payload (default: false)

  • include_crm_matches (boolean): Include CRM matches in payload (default: false)

  • include_summary (boolean): Include meeting summary in payload (default: false)

  • include_transcript (boolean): Include transcript in payload (default: false)

Returns: The created webhook details including:

  • id: Webhook ID (use this for deletion)

  • url: Destination URL

  • secret: Webhook secret for signature verification

  • created_at: Creation timestamp

Examples:

  • Basic webhook: { destination_url: 'https://your-app.com/webhook', triggered_for: ['my_recordings'] }

  • With all content: { destination_url: 'https://your-app.com/webhook', triggered_for: ['my_recordings', 'shared_team_recordings'], include_transcript: true, include_summary: true, include_action_items: true }

Notes:

  • Webhooks use HMAC-SHA256 signatures for verification

  • The secret is only shown once upon creation - save it securely

  • Webhooks must return 2xx status to acknowledge receipt

Inputs: destination_url (required), triggered_for (required), include_action_items, include_crm_matches, +2 more.

fathom_delete_webhookDelete Fathom WebhookA
DestructiveIdempotent

Delete an existing webhook from Fathom.

This tool removes a webhook subscription, stopping all future notifications to that endpoint.

Args:

  • id (string, required): The ID of the webhook to delete

Returns: Confirmation of successful deletion.

Examples:

  • Delete webhook: { id: 'ikEoQ4bVoq4JYUmc' }

Notes:

  • This action cannot be undone

  • The webhook will immediately stop receiving notifications

  • Any pending notifications may still be delivered

Inputs: id (required).

fathom_get_summaryGet Fathom Meeting SummaryA
Read-onlyIdempotent

Get the AI-generated summary for a specific Fathom recording.

This tool retrieves the summary that Fathom automatically generates for each meeting. The summary includes key discussion points, decisions made, and important topics covered.

Args:

  • recording_id (number, required): The ID of the recording to get the summary for

  • response_format ('markdown'|'json'): Output format (default: 'markdown')

Returns: The meeting summary with template name and formatted content.

Examples:

  • Get summary: { recording_id: 123456789 }

  • Get as JSON: { recording_id: 123456789, response_format: 'json' }

Notes:

  • The recording_id can be found in the meeting list response

  • Summaries are always in English regardless of the meeting's original language

Inputs: recording_id (required), response_format.

fathom_get_transcriptGet Fathom Meeting TranscriptA
Read-onlyIdempotent

Get the full transcript for a specific Fathom recording.

This tool retrieves the complete timestamped transcript of a meeting, including speaker identification and timestamps for each segment.

Args:

  • recording_id (number, required): The ID of the recording to get the transcript for

  • response_format ('markdown'|'json'): Output format (default: 'markdown')

Returns: Array of transcript entries, each containing:

  • speaker: Speaker name and optionally matched email

  • text: What was said

  • timestamp: When it was said (HH:MM:SS format)

Examples:

  • Get transcript: { recording_id: 123456789 }

  • Get as JSON: { recording_id: 123456789, response_format: 'json' }

Notes:

  • Transcripts can be large for long meetings

  • Speaker names are matched to calendar invitees when possible

  • Timestamps are relative to the recording start time

Inputs: recording_id (required), response_format.

fathom_list_meetingsList Fathom MeetingsA
Read-onlyIdempotent

List meetings from Fathom with optional filtering and pagination.

This tool retrieves meeting recordings from your Fathom account. You can filter by:

  • Company domains of calendar invitees

  • Internal vs external meetings

  • Date range (created_after/created_before)

  • Recorder email addresses

  • Team names

You can optionally include:

  • AI-generated summaries

  • Full transcripts

  • Action items

  • CRM matches (contacts, companies, deals)

Args:

  • calendar_invitees_domains (string[]): Filter by company domains

  • calendar_invitees_domains_type ('all'|'only_internal'|'one_or_more_external'): Filter by meeting type

  • created_after (string): ISO 8601 timestamp to filter meetings after

  • created_before (string): ISO 8601 timestamp to filter meetings before

  • cursor (string): Pagination cursor from previous response

  • include_action_items (boolean): Include action items (default: false)

  • include_crm_matches (boolean): Include CRM matches (default: false)

  • include_summary (boolean): Include summaries (default: false)

  • include_transcript (boolean): Include transcripts (default: false)

  • recorded_by (string[]): Filter by recorder emails

  • teams (string[]): Filter by team names

  • response_format ('markdown'|'json'): Output format (default: 'markdown')

Returns: Paginated list of meetings with requested details.

Examples:

  • List recent meetings: {}

  • External meetings only: { calendar_invitees_domains_type: 'one_or_more_external' }

  • With summaries: { include_summary: true }

  • Filter by team: { teams: ['Sales'] }

Inputs: calendar_invitees_domains, calendar_invitees_domains_type, created_after, created_before, +8 more.

fathom_list_team_membersList Fathom Team MembersA
Read-onlyIdempotent

List members of a specific team or all teams in Fathom.

This tool retrieves team member information including names, emails, and when they joined.

Args:

  • team (string): Filter by team name (optional - shows all members if not specified)

  • cursor (string): Pagination cursor from previous response

  • response_format ('markdown'|'json'): Output format (default: 'markdown')

Returns: Paginated list of team members with:

  • name: Member's display name

  • email: Member's email address

  • created_at: When the member was added

Examples:

  • List all members: {}

  • Filter by team: { team: 'Sales' }

  • Get as JSON: { response_format: 'json' }

Inputs: team, cursor, response_format.

fathom_list_teamsList Fathom TeamsA
Read-onlyIdempotent

List all teams accessible to the authenticated user in Fathom.

This tool retrieves the list of teams in your Fathom workspace. Teams are used to organize recordings and control access to meeting content.

Args:

  • cursor (string): Pagination cursor from previous response

  • response_format ('markdown'|'json'): Output format (default: 'markdown')

Returns: Paginated list of teams with:

  • name: Team name

  • created_at: When the team was created

Examples:

  • List all teams: {}

  • Get as JSON: { response_format: 'json' }

  • Next page: { cursor: 'eyJwYWdlX251bSI6Mn0=' }

Inputs: cursor, response_format.

fathom_meeting_statsGet Fathom Meeting StatisticsA
Read-onlyIdempotent

Get analytics and statistics about your Fathom meetings.

This tool calculates aggregate statistics about your meetings including duration metrics, team breakdowns, and internal vs external meeting ratios.

Args:

  • created_after (string): Filter to meetings after this ISO 8601 timestamp

  • created_before (string): Filter to meetings before this ISO 8601 timestamp

  • teams (string[]): Filter by team names

  • response_format ('markdown'|'json'): Output format (default: 'markdown')

Returns:

  • total_meetings: Number of meetings analyzed

  • duration_stats: Average, min, max, and total meeting duration in minutes

  • meetings_by_team: Count of meetings per team

  • internal_vs_external: Breakdown of internal vs external meetings

Examples:

  • All time stats: {}

  • This month: { created_after: '2024-11-01T00:00:00Z' }

  • Sales team: { teams: ['Sales'] }

Notes:

  • Duration is calculated from recording start to end time

  • Team breakdown based on recorder's team

  • External = one or more external participants

Inputs: created_after, created_before, teams, response_format.

fathom_participant_statsGet Fathom Participant StatisticsA
Read-onlyIdempotent

Get analytics about meeting participants and recorders in Fathom.

This tool analyzes who attends your meetings most frequently and which domains are most common.

Args:

  • created_after (string): Filter to meetings after this ISO 8601 timestamp

  • created_before (string): Filter to meetings before this ISO 8601 timestamp

  • limit (number): Max top participants/recorders to return (1-100, default: 10)

  • response_format ('markdown'|'json'): Output format (default: 'markdown')

Returns:

  • top_participants: Most frequent meeting attendees

  • domain_breakdown: Meeting count by email domain

  • top_recorders: Users who record the most meetings

Examples:

  • All time stats: {}

  • Top 20: { limit: 20 }

  • This quarter: { created_after: '2024-10-01T00:00:00Z' }

Inputs: created_after, created_before, limit, response_format.

fathom_search_meetingsSearch Fathom MeetingsA
Read-onlyIdempotent

Search across Fathom meeting titles, transcripts, and summaries.

This tool performs a text search across your meeting content to find relevant discussions, mentions, or topics.

Args:

  • query (string, required): Search string (2-200 characters)

  • created_after (string): Filter to meetings after this ISO 8601 timestamp

  • created_before (string): Filter to meetings before this ISO 8601 timestamp

  • teams (string[]): Filter by team names

  • limit (number): Max results to return (1-50, default: 10)

  • response_format ('markdown'|'json'): Output format (default: 'markdown')

Returns: Matching meetings with:

  • Meeting details

  • Where matches were found (title, transcript, summary)

  • Context snippets showing the matched text

Examples:

  • Search for topic: { query: 'quarterly budget' }

  • With date filter: { query: 'product launch', created_after: '2024-01-01T00:00:00Z' }

  • Limit results: { query: 'feature request', limit: 5 }

Notes:

  • Search is case-insensitive

  • Searches across transcripts and summaries (fetched automatically)

  • Limited to most recent meetings for performance

Inputs: query (required), created_after, created_before, teams, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct purpose with clear boundaries: webhook management (create/delete), meeting data retrieval (list, get summary/transcript, search), team management (list teams/members), and analytics (meeting/participant stats). There is no overlap or ambiguity between tools, making it easy for an agent to select the correct one.

    Naming Consistency5/5

    All tool names follow a consistent 'fathom_' prefix with snake_case and a clear verb_noun pattern (e.g., fathom_create_webhook, fathom_list_meetings, fathom_get_summary). This uniformity enhances readability and predictability across the toolset.

    Tool Count5/5

    With 10 tools, the server is well-scoped for managing Fathom meeting data, covering key operations like CRUD for webhooks, retrieval of meeting details, team management, analytics, and search. Each tool serves a unique and necessary function without bloat or gaps.

    Completeness5/5

    The toolset provides comprehensive coverage for the Fathom meeting domain, including full lifecycle management (create/delete webhooks), data access (list, get, search), team organization, and analytics. There are no obvious gaps; agents can perform all essential workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access Fathom AI meeting data including transcripts, summaries, teams, and team members. Provides tools to list meetings with filters, retrieve detailed transcripts and summaries, and manage team information.
      -
    • A
      license
      C
      quality
      D
      maintenance
      Enables access to Fathom.video meeting data including AI-generated transcripts, summaries, and action items. Supports searching meetings, exporting to markdown, and managing webhooks through natural language in Cursor IDE.
      11
      6
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides access to Fathom meeting recordings, enabling users to list meetings with filters, retrieve AI-generated summaries, and access full transcripts with speaker attribution and timestamps.
      3
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants access to Fathom meeting recordings, summaries, and transcripts via tools like list_meetings, get_meeting_summary, and get_meeting_transcript.
      MIT