Provider REST API

8 actions

Connect Claude to Fathom

Read recorded meetings, their AI summaries and transcripts, and manage the webhooks that deliver them. Toolspoke puts 8 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: API key
Actions exposed: 8
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Fathom
Open the marketplace in your workspace, add Fathom to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with api key. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Fathom shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Fathom asks for

API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

API keyRequired: Fathom → User Settings → API Access → generate an API key. The key sees the meetings its creator recorded and those shared with them or their team.

What Claude can do in Fathom

8 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 6Reads
Writes: 0Writes
Destructive: 2Destructive

Reads

Fetches data and changes nothing.

list_meetings
List recorded meetings, newest first, with title, times, recorder and calendar invitees. Filter by date, team, recorder, meeting type or invitee domain. Summaries and transcripts are left out by default - set include_summary or include_transcript, or call get_summary / get_transcript for one meeting. Page with next_cursor.
get_summary
Read one meeting's AI summary as markdown, with the name of the template that produced it.
get_transcript
Read one meeting's transcript as a list of lines, each with speaker name, matched invitee email and an HH:MM:SS timestamp.
list_meeting_types
List the meeting types this account uses, active and inactive. A type's name filters list_meetings.
list_teams
List the teams in this Fathom account.
list_team_members
List team members with their names and emails, optionally for one team.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

create_webhook
Register a URL that Fathom POSTs every new meeting's content to. Destructive rather than write: from then on, summaries and transcripts of other people's conversations go to that address automatically, with no further call. At least one include_ flag must be true.
delete_webhook
Delete a webhook. Meetings stop being delivered to its URL, and there is no undo.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 8 actions above are the whole of it. A call to any other name is refused before it reaches Fathom rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential: Toolspoke holds no access to Fathom of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Fathom: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Fathom. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Fathom's own rate limits. A call that Fathom refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Fathom?

8 named actions: 6 that only read and 2 that delete or permanently alter something. They include list_meetings, get_summary and get_transcript. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Fathom connector need?

API key. The connector asks for api key. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Fathom connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 8 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Fathom connector not do?

The 8 actions above are the whole of it. A call to any other name is refused before it reaches Fathom rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Fathom of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Fathom. An agent has to ask. Toolspoke does not retry, queue or back off around Fathom's own rate limits. A call that Fathom refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Fathom's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Fathom?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More productivity connectors

Browse all of them