mcp-fathom

This MCP server provides a natural language interface over your Fathom AI meetings data. It exposes tools that let Claude search across meeting titles, summaries, transcripts, and action items, list meetings with filters, and optionally include full transcripts in results. The server connects directly to Fathom via your API key to fetch up-to-date information in real time. To use it, configure an MCP client (like Claude Desktop) to point at the built server entry (dist/index.js) and supply your Fathom API key in the environment. Claude will automatically select the most appropriate tool based on your query (e.g., list_meetings for structured filters, or search_meetings for keyword-based queries), returning concise results suitable for conversational prompts.

Prerequisites:

• Node.js 18+ installed on your system
• npm (or yarn) for package management
• A Fathom AI account with API access to obtain an API key

Installation steps:

1. Clone the repository and install dependencies

git clone https://github.com/sourcegate/mcp-fathom-server.git
cd mcp-fathom-server
npm install

2. Build the project for production

npm run build

3. Prepare environment variables

cp .env.example .env

Edit the .env file to include your Fathom API key (the server reads FATHOM_API_KEY from the environment).

4. Run or configure the MCP server for your environment

• If you’re using the MCP config approach, ensure your mcp_config matches the following:

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

• Alternatively, run the built server directly with Node (after build):

node dist/index.js

5. Integrate with Claude Desktop

• Edit Claude Desktop configuration to include your MCP server, e.g.:

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

6. Restart Claude Desktop and start querying against your Fathom data.

Notes and tips:

• Environment variables: Ensure FATHOM_API_KEY is kept secret and not committed to source control.
• Build outputs: The runtime entry point is dist/index.js after running npm run build. If you change source files, re-run the build step.
• API rate limits: The server handles typical rate limiting from Fathom; if you hit limits, implement retry logic or stagger queries.
• Troubleshooting: If Claude reports that tools are missing, verify that the MCP server process is running and the environment variables are correctly set in the Claude Desktop configuration.
• Security: Consider restricting API key permissions to only the necessary endpoints in Fathom if your environment supports scoped keys.