This MCP server lets you access Fathom.video meeting transcripts, AI summaries, and action items directly from Cursor IDE using natural language. It enables you to list meetings, fetch full transcripts, export to markdown, search by participant or domain, manage teams, and configure real-time webhooks, all through simple prompts.

How to use

Use natural language to interact with your Fathom data through your MCP client. You can ask for a list of recent meetings, retrieve a specific transcript, export meetings to markdown, or pull action items. Examples include asking for summaries of recent meetings, exporting yesterday’s sessions to Markdown, or listing action items from this week.

Common patterns you can try in Cursor or any MCP-enabled client include:

• “List my last 5 Fathom meetings”
• “Get the transcript from my call with John”
• “Export yesterday's meetings to markdown”
• “Show me action items from this week” These requests are translated into the available MCP tools under the hood, returning structured results you can review or save. You can also combine queries, such as filtering by date or by participant domains, to narrow down results.

How to install

# 1. Get Your Fathom API Key
#   - Go to Fathom Settings
#   - Navigate to API Access
#   - Click Generate API Key

# 2. Install the MCP Server
git clone https://github.com/matthewbergvinson/fathom-mcp.git
cd fathom-mcp
npm install
npm run build

# 3. Configure Cursor
# Add the following to your Cursor MCP config (e.g., ~/.cursor/mcp.json)
# Replace paths and keys with your actual values
{
  "mcpServers": {
    "fathom": {
      "command": "node",
      "args": ["/path/to/fathom-mcp/dist/index.js"],
      "env": {
        "FATHOM_API_KEY": "your-api-key-here",
        "FATHOM_OUTPUT_DIR": "/path/to/export/transcripts"
      }
    }
  }
}

Note: Replace /path/to/fathom-mcp with the actual path where you cloned the project, and add your Fathom API key.

## Configuration and usage notes

Prerequisites: You need Node.js 18 or higher to run the MCP server and Cursor installed to use the MCP integration. Build and run steps are shown above. The MCP server runs locally and reads API keys and output settings from your Cursor configuration.

Exported transcripts are saved in Markdown format with a filename like `MeetingTitle_YYYY-MM-DD.md`, and include a metadata block, the AI-generated summary, action items, and the full transcript. You can adjust where transcripts are exported by setting `FATHOM_OUTPUT_DIR` in the MCP environment.

## Security and troubleshooting

Security:
- API keys are stored in Cursor's MCP configuration and should never be committed to version control.
- Webhook secrets, if used, should be stored securely.

Troubleshooting:
- If MCP not loading, restart Cursor after editing the MCP config and verify the path to the runtime index is correct.
- If you encounter fetch errors, ensure Node.js 18+ is installed and your network/API key permissions are valid.

## Development

Install dependencies

npm install

Build TypeScript

npm run build

Run in development/watch mode

npm run dev

## Available tools

### list\_meetings

List meetings with optional filters (date, team, external-only)

### get\_meeting

Get full meeting details including transcript, summary, and actions

### get\_transcript

Return just the transcript formatted as markdown

### search\_meetings

Search meetings by participant emails, domains, or teams

### export\_meeting

Export a single meeting to a Markdown file with a standardized filename

### export\_all\_meetings

Bulk export meetings with optional date filters

### get\_action\_items

Retrieve action items from a specific meeting or recent calls

### list\_teams

List all teams in the organization

### list\_team\_members

List members of a team, optionally filtered by team