# Fathom MCP [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://api.fathom.ai/mcp  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-13

## Description
Give your AI assistant real meeting context via Fathom so every output grounded in your work

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "fathom-mcp": {
    "url": "https://api.fathom.ai/mcp"
  }
}
```

## Documentation

## What Fathom MCP MCP server does

Fathom MCP MCP server is intended to give AI assistants access to meeting context from Fathom. The available description positions that context as a way to ground assistant-generated output in the user’s work rather than relying only on the conversation at hand.

The supplied source is an MCP endpoint hosted at `https://api.fathom.ai/mcp`. No README or additional product documentation was provided, so the exact data exposed from Fathom and the operations available to an assistant cannot be confirmed from the listing.

## How it works

An MCP-compatible assistant connects to the Fathom endpoint and can use the meeting context made available through that connection. The listing does not specify whether the endpoint requires an API key, OAuth, another authentication method, or no additional credentials.

It does not identify request formats, response schemas, synchronization behavior, search semantics, or whether the server can perform actions in Fathom. Treat those details as requiring confirmation before implementation.

## Tools and capabilities

The documented capability is access to Fathom meeting context for grounding AI assistant output.

Based on the listing alone, supported use cases include:

- Supplying meeting context to an AI assistant
- Grounding generated work in information from Fathom
- Using an MCP connection as the access path to that context

No further claims about transcript search, summaries, recordings, participants, or meeting updates can be made without tool documentation.

## Setup and configuration

The published endpoint is `https://api.fathom.ai/mcp`.

Before deploying the Fathom MCP MCP server, verify which MCP clients support the endpoint, how credentials are supplied, and whether access is controlled by Fathom account permissions. The source listing does not state a license or provide a versioning policy.

## Limitations and notes

Tool coverage, supported meeting data, authentication, transport behavior, error handling, rate limits, and client compatibility are undocumented here.

Its documented purpose is narrow but clear: provide real meeting context from Fathom so an AI assistant’s output can be grounded in the user’s work. Any workflow that depends on particular fields or operations should be validated against the live endpoint or fuller documentation.

_Full upstream README: https://allmcps.com/mcp/mcp-13/readme_