Fathom MCP Server

The Fathom AI MCP Server is a tool that connects Claude to Fathom meetings, transcriptions, and AI summaries. It enables direct data transfer through secure OAuth authentication without storing user data.

Communication tools Knowledge management and memory #Meeting management #AI summary #Data security #Team collaboration .TypeScript

rating : 2.5 points

downloads : 0

update time : 2026-03-12

Open Site

What is the Fathom AI MCP Server?

The Fathom AI MCP Server is a bridge that connects the Claude AI assistant to the Fathom meeting platform. It allows you to directly query and analyze your meeting records, transcribed texts, and AI-generated summaries through Claude without manually logging in to Fathom or copying and pasting content. This server uses a secure direct-pass architecture. Your data is never stored or cached and only serves as a secure proxy between Claude and Fathom.

How to use the Fathom AI MCP Server?

It's very simple to use, just follow three steps: 1. Add a custom connector in Claude Desktop. 2. Connect using the provided URL. 3. Authorize access to your Fathom account. After completing the setup, you can directly ask Claude any questions about your meetings, such as 'Which meetings did I have last week?' or 'Get the summary of yesterday's design team meeting'.

Use cases

The Fathom AI MCP Server is particularly suitable for the following scenarios: • Project managers who need to quickly review the content of multiple meetings. • Team leaders who want to analyze meeting patterns and trends. • Team members who need to find specific discussion points. • Individual users who hope to automate meeting summaries and action item tracking. • Researchers who need to search for content across multiple meetings.

Main features

View meeting list

Filter and view the meeting list by various conditions such as date, team, and recorder. Support paged browsing for easy management of a large number of meeting records.

Intelligent meeting search

Search for meetings through multiple dimensions such as title, host, and participant information. Even if the Fathom API does not provide a native search function, this server can perform intelligent client-side filtering.

Get full transcription

Get the full text transcription of any recording, supporting detailed dialogue analysis and content extraction.

Generate AI summary

Get the meeting summary generated by Fathom AI to quickly understand the core content and decision points of the meeting.

Team management function

View the list of all accessible teams and team member information for easy team-level meeting management.

Secure direct-pass architecture

Adopt a zero-storage design. Your data flows directly from Fathom to Claude without any caching or persistent storage in between.

Advantages

Seamless integration: Access Fathom data directly in Claude without switching applications

Data security: Adopt a direct-pass architecture. Your meeting data is never stored or exposed

Easy to use: Complete the setup in 60 seconds without complex configuration

Comprehensive functions: Cover the main Fathom API functions to meet most use cases

Enterprise-friendly: Support organizational-level deployment and management

Limitations

Search limitations: The search_meetings function performs filtering on the client side, which may be inefficient for a large number of meetings

Read-only access: Currently only supports read operations and cannot create or edit meetings

Dependent on Fathom API: The functions are limited by the availability and rate limits of the Fathom API

Requires HTTPS: Local development requires deployment to a platform that supports HTTPS

Organizational permissions: Organizational users need administrators to configure the connector

How to use

Open Claude Desktop settings

Launch the Claude Desktop application, click the settings icon in the upper right corner, and enter the settings menu.

Add a custom connector

Find the 'Connectors' option in the settings and click 'Add Custom Connector'.

Enter the server URL

Enter the following in the URL field: https://www.fathom-mcp-server.com/mcp

Complete Fathom authorization

Follow the prompts to complete the Fathom OAuth authorization process and allow Claude to access your meeting data.

Start using

After authorization is completed, you can directly query your Fathom meeting data in Claude.

Usage examples

Weekly meeting review

Project managers need to quickly review the key decisions and action items of all team meetings from last week.

Search for specific discussion points

Team members need to find the detailed content of a specific function discussion in previous meetings.

Cross-team meeting analysis

Team leaders want to analyze the meeting patterns and collaboration frequencies between different teams.

Frequently Asked Questions

Is my Fathom data secure?

What are the differences in settings between organizational users and individual users?

Why does the search_meetings function sometimes return results slowly?

Can I deploy this server myself?

Does this server support write operations?

Related resources

Official documentation

Complete API documentation and usage guide

GitHub repository

Open-source code repository containing the complete source code

MCP registry

View this server in the official MCP registry

Fathom developer documentation

Fathom official API reference documentation

Contribution guide

How to contribute code to the project

🚀 Fathom AI MCP Server

Connect Claude to your Fathom meetings, transcripts, and AI summaries, enabling seamless interaction and access to valuable meeting insights.

Get Started | Available Tools | API Docs | Self-Hosting | Contributing

🚀 Quick Start

This server is published to the MCP Registry as io.github.agencyenterprise/fathom-mcp-server.

Connect in under 60 seconds:

https://www.fathom-mcp-server.com/mcp

Open Claude Desktop
Go to Settings > Connectors > Add Custom Connector
Paste the URL above
Authenticate with Fathom

That's it. You can now ask Claude about your meetings.

⚠️ Important Note

For organizations, admins must add the connector via organization admin settings, not personal settings.

✨ Features

📦 Available Tools

Property	Details
`list_meetings`	List meetings with filters (date, team, recorder, etc.). Fathom API
`search_meetings`	Search meetings by title, host, or attendee information. MCP Custom
`get_transcript`	Get full transcript for a recording. Fathom API
`get_summary`	Get AI-generated summary for a recording. Fathom API
`list_teams`	List all accessible teams. Fathom API
`list_team_members`	List members of a team. Fathom API

Custom MCP Tools

`search_meetings`

Search Fathom meetings by title, meeting title, host name, host email, or attendee name/email. It automatically scans up to 5 pages of results. This is an MCP-native tool that performs client-side filtering since Fathom's API doesn't provide a search endpoint.

See the Fathom MCP Server documentation for full request and response parameters.

💻 Usage Examples

Basic Usage

In Claude, you can use the following commands:

"Show me my meetings from last week" "Get the transcript from my standup yesterday" "Summarize my meeting with the design team"

🔧 Technical Details

Security

Your Fathom data is never stored or exposed by this server.

Data	Stored?	Exposed?	Details
Meetings, transcripts, summaries	No	No	Fetched from Fathom and passed directly to Claude
Team and member info	No	No	Fetched from Fathom and passed directly to Claude
OAuth tokens	Yes	No	Encrypted at rest (AES-256-GCM), never logged or exposed

Pass-through architecture: This server acts as a secure proxy, your Fathom data flows directly from Fathom to Claude without being stored, cached, or logged.
Encryption at rest: The only stored data (OAuth tokens) is encrypted using AES-256-GCM before being written to the database.
HTTPS only: All communication between Claude, this server, and Fathom is encrypted in transit.

See our full Privacy Policy for details on data collection, usage, and your rights.

Permissions

This MCP server defines a custom scope called fathom:read for tokens it issues to Claude. This is not a Fathom API scope - it's specific to this MCP server to describe read-only access to your Fathom data.

The Fathom API itself only provides read access via its public_api scope. Write operations (creating/editing meetings, transcripts, etc.) are not available in the Fathom API.

Limitations

search_meetings performs client-side filtering since Fathom's API doesn't provide a search endpoint. For users with many meetings, use list_meetings with date filters instead.
You can always ask the LLM what query params are available.

📦 Installation

Self-Hosting

Fathom OAuth apps require HTTPS redirect URIs, so local development with http://localhost isn't possible. Deploy to a hosting provider to test.

1. Deploy to a Hosting Provider

Use Railway (recommended), Render, or any platform that provides:

Node.js 18+ runtime
PostgreSQL database
HTTPS URL

Railway setup:

Fork/clone this repo.
Create a new Railway project (you can deploy directly from your forked Github repo).
Add a PostgreSQL database service in the project.
Connect the Database URL to the deployed repo in the project and setup other envs.

2. Create a Fathom OAuth App

Go to Fathom Developer Portal.
Click "Register your app" (requires Fathom admin access).
Set the redirect URI to https://your-app-url.railway.app/oauth/fathom/callback.
Note your Client ID and Client Secret.

3. Configure Environment Variables (locally and in Railway)

Set these in your hosting provider's dashboard (as well as your local .env file to test build and start commands locally before pushing changes)

Variable	Description
`DATABASE_URL`	PostgreSQL connection string (auto-set by Railway - use public db url)
`BASE_URL`	Your app's public URL (e.g., `https://your-app.railway.app`)
`TOKEN_ENCRYPTION_KEY`	32-byte hex key (generate with `openssl rand -hex 32`)
`FATHOM_CLIENT_ID`	From step 2
`FATHOM_CLIENT_SECRET`	From step 2

4. Initialize Database

Run migrations after the first deploy:

npm run db:migrate

Or via Railway CLI:

railway run npm run db:migrate

5. Connect Claude

Add your deployed URL as a custom connector in Claude Desktop:

https://your-app.railway.app/mcp

📚 Documentation

Development

npm run dev          # Start dev server with hot reload only for testing
npm run build        # Build for production
npm run start        # Run production build
npm run lint         # Check for linting errors
npm run lint:fix     # Fix linting errors
npm run typecheck    # Run TypeScript type checking
npm run ci           # Run all CI checks (lint, typecheck, build)
npm run format       # Format code with Prettier
npm run db:studio    # Open Drizzle Studio for database inspection
npm run db:generate  # Generate migrations from schema changes
npm run db:migrate   # Run pending migrations
npm run db:push      # Push schema directly (dev only)

💡 Usage Tip

Run npm run ci before pushing to ensure your changes pass GitHub Actions.

Beta Testing

For pre-release features, use the staging URL:

https://fathom-mcp-staging.up.railway.app/mcp

Fathom AI Deep dive

https://developers.fathom.ai/llms.txt

Contributing

See CONTRIBUTING.md for development setup and guidelines.

Releasing

See RELEASING.md for version and release instructions.

Future Development Plans

Transcript vectorization — Enable vectorization of large transcripts so LLMs can parse and understand them more efficiently. Would be implemented as a stateless worker to ensure no user data is persisted.
Action item aggregation — Aggregate action items across meetings with filters. "Show all my incomplete action items from this week."
Meeting analytics — Calculate stats like total meeting time, meeting frequency, and top attendees.
Speaker time analysis — Analyze transcripts to show who spoke most in a meeting.
Meeting comparison — Compare two meeting summaries to highlight what changed over time.
Fathom API changelog monitoring — Automated detection of Fathom API changes via GitHub Action that periodically checks their API reference and creates an issue if changes are detected.

Contributions toward these goals are welcome. See CONTRIBUTING.md.