home / mcp / fathom mcp server

Fathom MCP Server

Provides an MCP server to access Fathom AI meeting data through tools for meetings, transcripts, summaries, and teams.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "bondjacobbond-fathom-mcp": {
      "url": "https://fathom-mcp.vercel.app/api/mcp",
      "headers": {
        "FATHOM_API_KEY": "YOUR_FATHOM_API_KEY"
      }
    }
  }
}

You run an MCP server that exposes Fathom AI meeting data to agents, enabling you to search meetings, retrieve transcripts and summaries, and inspect teams and members through a consistent MCP API.

How to use

Connect your MCP-enabled agent or client to either the remote HTTP endpoint or the local dev server. You will access five tools that let you list meetings, fetch meeting transcripts, retrieve summaries, and inspect teams and their members. Use the HTTP URL for production or the local server during development, and authenticate with a Bearer token when required.

How to install

Prerequisites: Node.js and npm installed on your machine. You should have a modern operating system with network access.

1. Clone the project repository and open it.

git clone <your-repo-url>
cd fathom-mcp-server
npm install

Configure environment

Prepare your environment file and add your Fathom API key.

cp .env.example .env.local
Edit .env.local and set FATHOM_API_KEY=your_fathom_api_key_here

Run locally

Start the local MCP server for development. It will be available at the MCP route.

npm run dev

Deploy to production

Deploy to a hosting environment that supports MCP endpoints. Use the built-in deployment flow or your preferred provider. Ensure your FATHOM_API_KEY is set in the deployment environment.

npm install -g vercel
vercel

Usage notes for deployment URL

Production MCP endpoint (example) is exposed at a remote URL such as https://fathom-mcp.vercel.app/api/mcp. Use this URL from your MCP client configuration to connect to the server in production.

Additional configuration and tooling

The server is implemented with TypeScript and uses a strict validation layer to ensure input conforms to the expected schemas. Environment variables are kept secure and are not committed to source control.

Security considerations

HTTPS is provided by the hosting platform. API keys are stored in environment variables and never embedded in client-side code. Inputs are validated to prevent malformed requests, and rate limiting is respected when communicating with the underlying data sources.

Troubleshooting

If you encounter issues, verify that your FATHOM_API_KEY is set in your environment, check for proper network access, and confirm that the MCP route URL is reachable from your client. For development, enable verbose logs to diagnose problems.

Testing

During development, you can test the MCP server locally and validate the route works with your MCP client. Use the development server URL http://localhost:3000/api/mcp to perform local tests.

Project structure

The server is organized to separate the MCP route, the Fathom API client, and configuration. This keeps integration clean and testable.

Available tools

fathom_list_meetings

List meetings with optional filters such as date ranges and invitees to discover relevant meetings.

fathom_get_summary

Retrieve the summary for a specific meeting by its recording ID.

fathom_get_transcript

Fetch the meeting transcript with speaker information and timestamps for a given recording ID.

fathom_list_teams

List all teams within the organization.

fathom_list_team_members

List members for a specific team by team ID.