Is this an official Fathom Video MCP server?

No. It is Memtro's MCP server with Memtro's Fathom Video connector behind it: the connector reads Fathom Video through its API with the credentials you connect on Dashboard → Connections, and Fathom Video publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Fathom Video?

Not yet. Today every Fathom Video tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Email, calendar and chat

Fathom Video MCP server

Fathom Video in any MCP client, through Memtro: Fathom Video does not publish this server. Memtro's Fathom Video connector reads Fathom Video through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only Fathom AI meeting notes: recorded meetings with who recorded and was invited, external or internal, Fathom's summary and action items, a bounded slice of a transcript by speaker, and the teams and meeting types.

Reads

fathomvideo_list_meetingsMeetings recorded with Fathom that the key's user can see: title, meeting type, when, length, who recorded it (by name)…
fathomvideo_get_summaryFathom's AI summary of one recorded meeting, as Markdown (always in English).
fathomvideo_get_transcriptPart of a Fathom meeting's transcript: speaker name, time into the recording and what was said, a window of lines at a time (default the first 150…
fathomvideo_list_teamsFathom teams the key can see, with when each was made.
fathomvideo_list_team_membersMembers of the Fathom account, or of one team, by name, with when they joined.
fathomvideo_list_meeting_typesThe organisation's Fathom meeting types (active and inactive).

Connect it

First connect Fathom Video on Dashboard → Connections, then add Memtro to your client once. The Fathom Video tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Fathom Video connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What was agreed on Tuesday's call with Northwind?
› What action items came out of this week's calls with Acme?
› Which calls last week had someone external from Brightwave Ltd invited?
› What exactly did Dan Fletcher say about pricing on the BigCo call?
› Which meetings did Priya Sharma record this month?

Questions

Is this an official Fathom Video MCP server?: No. It is Memtro's MCP server with Memtro's Fathom Video connector behind it: the connector reads Fathom Video through its API with the credentials you connect on Dashboard → Connections, and Fathom Video publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Fathom Video?: Not yet. Today every Fathom Video tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.