{
  "markdown": "It was fun while it lasted! Fathom now has an offical mcp: https://developers.fathom.ai/mcp-docs\n\nHowever, I plan on adding very customizable tools to this mcp so it will be kept alive and expanded on once I have time or if anyone else contributes.\n\n<div align=\"center\">\n\n# Fathom AI MCP Server\n\n**Connect Claude to your Fathom meetings, transcripts, and AI summaries.**\n\n[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)\n[![Node.js](https://img.shields.io/badge/Node.js-18+-green.svg)](https://nodejs.org)\n[![MCP](https://img.shields.io/badge/MCP-Compatible-purple.svg)](https://modelcontextprotocol.io)\n[![MCP Registry](https://img.shields.io/badge/MCP_Registry-Published-green.svg)](https://registry.modelcontextprotocol.io)\n\n[Get Started](#get-started) | [Available Tools](#available-tools) | [API Docs](https://www.fathom-mcp-server.com/docs) | [Self-Hosting](#self-hosting) | [Contributing](CONTRIBUTING.md)\n\n[![Security](https://img.shields.io/badge/🔒_Your_data_is_100%25_secure_🔒-grey?style=flat)](#security)\n\n</div>\n\n---\n\n## Get Started\n\nThis server is published to the [MCP Registry](https://registry.modelcontextprotocol.io) as `io.github.agencyenterprise/fathom-mcp-server`.\n\n### Claude Desktop (Streamable HTTP)\n\nConnect in under 60 seconds:\n\n```\nhttps://www.fathom-mcp-server.com/mcp\n```\n\n1. Open **Claude Desktop**\n2. Go to **Settings > Connectors > Add Custom Connector**\n3. Paste the URL above\n4. Authenticate with Fathom\n\nThat's it. Ask Claude about your meetings.\n\n> **Organizations**: Admins must add the connector via organization admin settings, not personal settings.\n\n### Perplexity Desktop and other SSE clients\n\nFor clients that use the legacy SSE transport (such as Perplexity Desktop for Mac), use the SSE endpoint:\n\n```\nhttps://www.fathom-mcp-server.com/sse\n```\n\nRefer to your client's documentation for how to add a remote SSE connector.\n\n## Available Tools\n\n| Tool                | Description                                             | Docs                                                                                    |\n| ------------------- | ------------------------------------------------------- | --------------------------------------------------------------------------------------- |\n| `list_meetings`     | List meetings with filters (date, team, recorder, etc.) | [Fathom API](https://developers.fathom.ai/api-reference/meetings/list-meetings)         |\n| `search_meetings`   | Search meetings by title, host, or attendee information | [MCP Custom](#custom-mcp-tools)                                                         |\n| `get_transcript`    | Get full transcript for a recording                     | [Fathom API](https://developers.fathom.ai/api-reference/recordings/get-transcript)      |\n| `get_summary`       | Get AI-generated summary for a recording                | [Fathom API](https://developers.fathom.ai/api-reference/recordings/get-summary)         |\n| `list_teams`        | List all accessible teams                               | [Fathom API](https://developers.fathom.ai/api-reference/teams/list-teams)               |\n| `list_team_members` | List members of a team                                  | [Fathom API](https://developers.fathom.ai/api-reference/team-members/list-team-members) |\n\n### Custom MCP Tools\n\n#### `search_meetings`\n\nSearch Fathom meetings by title, meeting title, host name, host email, or attendee name/email. 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.\n\nSee the [Fathom MCP Server documentation](https://www.fathom-mcp-server.com/docs) for full request and response parameters.\n\n### Example Usage in Claude\n\n> \"Show me my meetings from last week\"\n\n> \"Get the transcript from my standup yesterday\"\n\n> \"Summarize my meeting with the design team\"\n\n## Security\n\n**Your Fathom data is never stored or exposed by this server.**\n\n| Data                             | Stored? | Exposed? | Details                                                  |\n| -------------------------------- | ------- | -------- | -------------------------------------------------------- |\n| Meetings, transcripts, summaries | No      | No       | Fetched from Fathom and passed directly to Claude        |\n| Team and member info             | No      | No       | Fetched from Fathom and passed directly to Claude        |\n| OAuth tokens                     | Yes     | No       | Encrypted at rest (AES-256-GCM), never logged or exposed |\n\n- **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\n- **Encryption at rest**: The only stored data (OAuth tokens) is encrypted using AES-256-GCM before being written to the database\n- **HTTPS only**: All communication between Claude, this server, and Fathom is encrypted in transit\n\nSee our full [Privacy Policy](PRIVACY.md) for details on data collection, usage, and your rights.\n\n## Permissions\n\nThis 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.\n\nThe 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.\n\n## Limitations\n\n- `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.\n- You can always ask the LLM what query params are avaialable.\n\n## Self-Hosting\n\nFathom OAuth apps require HTTPS redirect URIs, so local development with `http://localhost` isn't possible. Deploy to a hosting provider to test.\n\n### 1. Deploy to a Hosting Provider\n\nRailway (recommended), Render, or any platform that provides:\n\n- Node.js 18+ runtime\n- PostgreSQL database\n- HTTPS URL\n\n**Railway setup:**\n\n1. Fork/clone this repo\n2. Create a new Railway project (you can deploy directly from your forked Github repo)\n3. Add a PostgreSQL database service in project\n4. Connect Database url to deployed repo in project and setup other envs\n\n### 2. Create a Fathom OAuth App\n\n1. Go to [Fathom Developer Portal](https://developers.fathom.ai/oauth)\n2. Click \"Register your app\" (requires Fathom admin access)\n3. Set the redirect URI to `https://your-app-url.railway.app/oauth/fathom/callback`\n4. Note your Client ID and Client Secret\n\n### 3. Configure Environment Variables (locally and in Railway)\n\nSet these in your hosting provider's dashboard (as well as your local .env file to test build and start commands locally before pushing changes)\n\n| Variable               | Description                                                            |\n| ---------------------- | ---------------------------------------------------------------------- |\n| `DATABASE_URL`         | PostgreSQL connection string (auto-set by Railway - use public db url) |\n| `BASE_URL`             | Your app's public URL (e.g., `https://your-app.railway.app`)           |\n| `TOKEN_ENCRYPTION_KEY` | 32-byte hex key (generate with `openssl rand -hex 32`)                 |\n| `FATHOM_CLIENT_ID`     | From step 2                                                            |\n| `FATHOM_CLIENT_SECRET` | From step 2                                                            |\n\n### 4. Initialize Database\n\nRun migrations after first deploy:\n\n```bash\nnpm run db:migrate\n```\n\nOr via Railway CLI:\n\n```bash\nrailway run npm run db:migrate\n```\n\n### 5. Connect Claude\n\nAdd your deployed URL as a custom connector in Claude Desktop:\n\n```\nhttps://your-app.railway.app/mcp\n```\n\nFor SSE clients (Perplexity Desktop, etc.):\n\n```\nhttps://your-app.railway.app/sse\n```\n\n## Development\n\n```bash\nnpm run dev          # Start dev server with hot reload only for testing\nnpm run build        # Build for production\nnpm run start        # Run production build\nnpm run lint         # Check for linting errors\nnpm run lint:fix     # Fix linting errors\nnpm run typecheck    # Run TypeScript type checking\nnpm run ci           # Run all CI checks (lint, typecheck, test, build)\nnpm run format       # Format code with Prettier\nnpm run db:studio    # Open Drizzle Studio for database inspection\nnpm run db:generate  # Generate migrations from schema changes\nnpm run db:migrate   # Run pending migrations\nnpm run db:push      # Push schema directly (dev only)\n```\n\n> **Tip**: Run `npm run ci` before pushing to ensure your changes pass GitHub Actions.\n\n## Beta Testing\n\nFor pre-release features, use the staging URLs:\n\n```\nhttps://fathom-mcp-staging.up.railway.app/mcp\n```\n\n```\nhttps://fathom-mcp-staging.up.railway.app/sse\n```\n\n## Fathom AI Deep dive\n\nhttps://developers.fathom.ai/llms.txt\n\n## Contributing\n\nSee [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and guidelines.\n\n## Releasing\n\nSee [RELEASING.md](RELEASING.md) for version and release instructions.\n\n## Future Development Plans\n\n- **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.\n- **Action item aggregation** — Aggregate action items across meetings with filters. \"Show all my incomplete action items from this week.\"\n- **Meeting analytics** — Calculate stats like total meeting time, meeting frequency, and top attendees.\n- **Speaker time analysis** — Analyze transcripts to show who spoke most in a meeting.\n- **Meeting comparison** — Compare two meeting summaries to highlight what changed over time.\n- **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.\n\nContributions toward these goals are welcome. See [CONTRIBUTING.md](CONTRIBUTING.md).\n\n## License\n\nMIT License - see [LICENSE](LICENSE) for details.\n",
  "bytes": 10066,
  "sha": "0682f7b5b5cf8aa78109703b4f6c64e567a83a5e0609261e12c7d4a8254a7518",
  "repo_slug": "agencyenterprise/fathom-mcp-server",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_agencyenterprise_fathom_mcp_se_4954d79d/readme"
}