Fathom Integration Setup

What You’ll Get

When you connect Fathom to your MCP server, you unlock 3 additional tools:

• fathom_list_meetings - List meetings with summaries, participants, and metadata
• fathom_get_transcript - Get detailed transcripts with speaker names and emails
• fathom_get_meeting_details - Get comprehensive meeting information including action items

These tools work alongside the 8 core Mind Reasoner tools, giving you seamless access to your meeting data.

Choose Your Integration Approach

You have two options for working with Fathom data:

Option 1: MCP Server Integration (Recommended)

Best for: AI-driven workflows, natural language access, no coding

Benefits:

• Access Fathom meetings through simple AI commands
• Automatic authentication and error handling
• Seamless integration with Mind Reasoner mind creation
• Works in Claude Desktop, Claude Code, and other MCP clients

Setup: Follow the steps below to add Fathom credentials to your MCP server

Option 2: Direct Fathom API Integration

Best for: Custom applications, specialized workflows, full API control

Benefits:

• Complete control over API calls and data processing
• Build custom integrations with other services
• Implement specialized business logic

Resources:

• Fathom API Documentation
• Fathom API Reference
• Mind Reasoner REST API - Combine with Fathom data as needed

MCP Server Integration Setup

$
# Required - Mind Reasoner
$
MIND_REASONER_API_KEY=your_mind_reasoner_key
$
$
# Optional - Fathom Integration
$
FATHOM_API_KEY={{FATHOM_API_KEY}}

$
# Required
$
Authorization: Bearer YOUR_MIND_REASONER_KEY
$
$
# Optional - Fathom
$
X-Fathom-Api-Key: {{FATHOM_API_KEY}}

$
# Restart Claude Desktop or Claude Code
$
# The Fathom tools will be available automatically

"What Fathom tools do you have access to?"

"Show me my last 5 Fathom meetings from this week"

Authentication Details

How Fathom Authentication Works

Fathom uses API Key authentication with a simple, straightforward approach:

1. Your API key is sent in the X-Api-Key header with each request
2. Fathom validates the key against your account
3. If valid, the API returns data accessible to your account

This is simpler than Gong’s HMAC-SHA256 approach but still secure when used with HTTPS.

Security Best Practices

Troubleshooting

”Fathom tools not available”

Possible causes:

• Credentials not configured
• Environment variables not loaded
• MCP client not restarted after configuration

Solutions:

1. Verify environment variable is set correctly
2. Check for typos in variable name (FATHOM_API_KEY)
3. Ensure API key format is correct (starts with “fathom_”)
4. Restart your MCP client (Claude Desktop, Claude Code)
5. Ask: “What MCP tools are available?” to see current tool list

”Authentication failed” or 401 errors

Possible causes:

• Incorrect API key
• API key revoked or deleted
• Fathom account suspended

Solutions:

1. Verify API key matches exactly what’s shown in Fathom settings
2. Check for extra spaces or line breaks in the key
3. Generate a new API key in Fathom settings
4. Verify your Fathom account is active and has API access

”Rate limit exceeded” or 429 errors

Cause: Too many API requests to Fathom in a short time period

Solutions:

1. Wait for the time specified in the error message
2. Reduce the frequency of meeting list queries
3. Use date filtering to reduce result set sizes
4. Contact Fathom support to discuss rate limits for your account

No meetings returned from fathom_list_meetings

Possible causes:

• No meetings in the specified date range
• User permissions don’t include meeting access
• Fathom account has no recorded meetings

Solutions:

1. Try a wider date range or remove date filter
2. Verify your Fathom account has recorded meetings
3. Check that meetings are fully processed (not still transcribing)
4. Ensure you have access to the meetings (not shared with restrictions)

Transcript not available

Possible causes:

• Meeting still processing
• Transcription failed
• Meeting was recorded without audio

Solutions:

1. Wait a few minutes for transcription to complete
2. Check the meeting in Fathom web app to verify transcript exists
3. Verify meeting had audio and speakers
4. Try re-processing the meeting in Fathom if needed

Example Workflows

Once Fathom is connected, try these workflows:

List Recent Meetings

"Show me my last 10 Fathom meetings from this month"

AI uses: fathom_list_meetings with date filtering

Create Mind from Meeting

"Create a mind from my Fathom meeting with the Product Team from yesterday"

AI workflow:

1. Lists meetings and finds the matching meeting
2. Retrieves full transcript with fathom_get_transcript
3. Creates a new mind with create_mind
4. Uploads transcript data
5. Creates snapshot and waits for training

Get Meeting Summaries

"Show me summaries and action items from all my
 client meetings this week"

AI uses: fathom_list_meetings (includes summaries) + fathom_get_meeting_details for action items

Create Minds for Multiple Speakers

"Create separate minds for each participant in my
 leadership team meeting from Monday"

AI orchestrates:

1. Gets meeting transcript
2. Identifies all speakers
3. Creates a mind for each speaker
4. Uploads transcript segments for each speaker
5. Trains all minds in parallel

Weekly Team Analysis

"Create minds for everyone who spoke in my weekly
 team meetings over the last month"

AI workflow:

1. Lists all meetings from last month
2. Filters to weekly team meetings (by title/participants)
3. Gets transcripts for each meeting
4. Identifies unique speakers across all meetings
5. Creates minds and uploads relevant segments for each person

Meeting Data Access

What Data You Can Access

Fathom provides rich meeting data through the API:

• Meeting Metadata: Title, date, duration, participants, recording URL
• Transcripts: Full text with speaker attribution (names and emails)
• Summaries: AI-generated meeting summaries
• Action Items: Extracted tasks and follow-ups
• Key Topics: Important discussion points
• Participants: Names and email addresses of attendees

Data Privacy

When you connect Fathom:

• Only meetings you have access to are retrievable
• Transcripts are fetched in real-time from Fathom’s API
• Data is transmitted securely to Mind Reasoner for processing
• The MCP server does not store meeting data
• All data handling follows Mind Reasoner’s privacy policies

Next Steps

Official Documentation

For direct API integration or advanced use cases:

• Fathom API Documentation - Getting started guide
• Fathom API Reference - Complete endpoint reference
• Fathom Help Center - General Fathom support