[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Fathom API and MCP server

> Fathom has a REST API and an official MCP server, but both only read your calls (checked 22 Oct 2026). The API lists meetings and returns summaries, transcripts and action items, requests recording downloads and manages webhooks. Its reference has no endpoint that edits an action item, shares a call or changes a setting.

AI notetaker that records Zoom, Google Meet and Microsoft Teams calls and writes a transcript, a summary, highlights and action items for each one.

## What is the Fathom API?

Cotlet's Fathom API exposes 14 endpoints for your own Fathom account: list calls, get a call, get a transcript, list action items, get call sharing, get settings, add an action item, update an action item, share a call, remove call access, set link access, regenerate a summary, update settings and delete a call. The list_calls endpoint returns calls from My Calls or Team Calls, newest first, with title, date, meeting type and open action items. Each endpoint takes simple JSON inputs like call_id, cursor or description and works both as an operation of the fathom_video_read or fathom_video_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Productivity & teams](https://cotlet.dev/integrations/category/productivity-teams.md)
- **Endpoints:** 14 (6 read, 8 write)
- **Updated:** 2026-10-22

Fathom has a REST API and an official MCP server, but both only read your calls (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Fathom with 14 endpoints (6 read, 8 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Fathom have an official API?

Fathom has a REST API and an official MCP server, but both only read your calls (checked 22 Oct 2026). The API lists meetings and returns summaries, transcripts and action items, requests recording downloads and manages webhooks. Its reference has no endpoint that edits an action item, shares a call or changes a setting.

| Task | Fathom official | Cotlet |
|---|---|---|
| List calls and read their summaries | Yes: API and MCP server; the API returns only your default summary template | Yes |
| Read transcripts | Yes: API and MCP server | Yes |
| Read action items | Yes: API, with completed and assignee; OAuth apps fetch them through the recordings endpoints | Yes |
| Add, edit or complete action items | No | Yes |
| Share a call or change its link access | No | Yes |
| Regenerate a summary with another template | No | Yes |
| Change settings such as auto-share | No | Yes |
| Delete a call | No | Yes |

Sources: [Fathom API: introduction and endpoint list](https://developers.fathom.ai/llms.txt), [Fathom API: FAQ](https://developers.fathom.ai/faq), [Fathom MCP: overview](https://developers.fathom.ai/mcp-docs), [Fathom Help: Fathom MCP, Connect Claude and ChatGPT](https://help.fathom.video/en/articles/11497793)

## For AI agents

```text
Fathom has a REST API and an official MCP server, but both only read your calls (checked 22 Oct 2026). The API lists meetings and returns summaries, transcripts and action items, requests recording downloads and manages webhooks. Its reference has no endpoint that edits an action item, shares a call or changes a setting.
Cotlet provides a hosted MCP server and REST API for Fathom: 14 tools (6 read, 8 write).
Access       Sign up at https://cotlet.dev/app/signup?app=fathom-video, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    fathom_video_read, fathom_video_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/fathom-video, each operation at its own route, e.g. POST /api/v1/fathom-video/calls/{call_id}/share
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_calls, get_call, get_transcript, list_action_items, get_call_sharing, get_settings, add_action_item, update_action_item, share_call, remove_call_access, set_link_access, regenerate_summary, update_settings, delete_call
Confirm      add_action_item, share_call, remove_call_access, set_link_access, regenerate_summary, update_settings, delete_call (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/fathom-video-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=fathom-video, requests Fathom in the Cotlet console and creates an API key there.
2. The user signs in to Fathom once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Fathom for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Fathom server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Fathom MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Fathom in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Fathom only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Fathom login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Fathom's terms; Cotlet is not affiliated with Fathom.
```

## What can an AI agent do in Fathom?

Cotlet is best for Fathom users who run many calls and want their AI agent to close action items, tighten sharing and rewrite summaries without running or fixing a server.

- **[Complete and update action items](https://cotlet.dev/integrations/fathom-video-api-mcp-server/update-action-items.md)** (runs: weekly): "Go through my Fathom calls from the last 7 days. For each open action item, check later calls for proof it is done, tick the done ones and list the rest with a reason." → `list_calls`, `list_action_items`, `get_transcript`, `update_action_item`, `add_action_item`
- **[Restrict call share links](https://cotlet.dev/integrations/fathom-video-api-mcp-server/restrict-share-links.md)** (runs: weekly): "List my Fathom calls from the last 30 days that anyone with the link can open. Set them to only people added, except calls with the meeting type Public webinar, and tell me who stays on each." → `list_calls`, `get_call_sharing`, `set_link_access`
- **[Rewrite call summaries for a client](https://cotlet.dev/integrations/fathom-video-api-mcp-server/rewrite-call-summaries.md)** (runs: weekly): "For my external Fathom calls this week, rewrite each summary in a formal tone for the client, with a Next steps section at the end. Show me the text before anything is shared." → `list_calls`, `get_call`, `regenerate_summary`
- **Share calls with attendees who missed them** (runs: weekly): "For calls this week where an invitee is not in the sharing list, share the call with them at Limited access and list who got it." → `list_calls`, `get_call`, `get_call_sharing`, `share_call`
- **Delete old calls**: "List my Fathom calls older than 12 months that have no open action items, show me titles, and delete the ones I approve." → `list_calls`, `list_action_items`, `delete_call`

## Can Fathom automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Fathom connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to complete and update action items, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/fathom-video/calls. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/fathom-video/calls with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Fathom.

### list_calls

Calls from My Calls or Team Calls, newest first, with title, date, meeting type and open action items. Access: read. REST: `GET /api/v1/fathom-video/calls`. MCP: `fathom_video_read → list_calls`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `scope` | enum | no | my_calls (default) or team_calls. |
| `created_after` | date | no | Only calls recorded on or after this date. |
| `created_before` | date | no | Only calls recorded before this date. |
| `meeting_type` | string | no | Name of a Meeting Type, as shown on the call. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists calls the way the My Calls and Team Calls pages show them, newest first; pass next_cursor back as cursor for the next page. scope team_calls works for accounts on a Team plan. meeting_type filters by one of your Meeting Types, and created_after and created_before bound the date. open_action_items counts the items on the call that are not completed. Use call_id with the other tools.

Example response:

```json
{
  "calls": [
    {
      "call_id": "610313346",
      "title": "Q4 pricing review",
      "recorded_at": "2026-10-21T15:00:00Z",
      "meeting_type": "External",
      "attendees": 4,
      "open_action_items": 3,
      "url": "https://fathom.video/calls/610313346"
    },
    {
      "call_id": "610298114",
      "title": "Vendor onboarding sync",
      "recorded_at": "2026-10-20T09:30:00Z",
      "meeting_type": "External",
      "attendees": 3,
      "open_action_items": 1,
      "url": "https://fathom.video/calls/610298114"
    }
  ],
  "next_cursor": "c_2"
}
```

### get_call

One call: attendees, who recorded it, the summary with its template name, highlights and action items. Access: read. REST: `GET /api/v1/fathom-video/calls/{call_id}`. MCP: `fathom_video_read → get_call`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `call_id` | string | yes | Call ID from list_calls: the number in the call address, fathom.video/calls/{call_id}. |

Returns the call page: title, date, attendees, recorder, meeting type, the summary in the template currently selected on the page (Markdown) and its highlights. action_items lists the Action Items section with each item completed or open. The call must be one your account can open, your own or shared with you. A summary that Fathom is still writing comes back with summary_status generating.

Example response:

```json
{
  "call_id": "610313346",
  "title": "Q4 pricing review",
  "recorded_at": "2026-10-21T15:00:00Z",
  "recorded_by": "Dana Whitfield",
  "meeting_type": "External",
  "attendees": [
    "Dana Whitfield",
    "Marc Ellery",
    "Priya Nair",
    "Tom Hale"
  ],
  "summary_template": "General",
  "summary_status": "ready",
  "summary": "## Summary\nWe agreed to move the Team plan to annual billing and to send the revised quote by Friday.",
  "highlights": [
    {
      "type": "Decision",
      "text": "Annual billing for the Team plan",
      "timestamp": "00:12:40"
    }
  ],
  "action_items": [
    {
      "item_id": "ai_8841",
      "description": "Send revised quote to Marc",
      "assignee": "Dana Whitfield",
      "completed": false
    }
  ]
}
```

### get_transcript

The transcript of a call with speaker names and timestamps. Access: read. REST: `GET /api/v1/fathom-video/calls/{call_id}/transcript`. MCP: `fathom_video_read → get_transcript`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `call_id` | string | yes | Call ID from list_calls: the number in the call address, fathom.video/calls/{call_id}. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the transcript of one call in order, one entry per turn with the speaker display name, the text and the timestamp as the call page shows it. Long calls come in pages of turns: pass next_cursor back as cursor. Speaker names are the display names the call page shows.

Example response:

```json
{
  "call_id": "610313346",
  "turns": [
    {
      "speaker": "Dana Whitfield",
      "text": "Let us revisit the annual billing option.",
      "timestamp": "00:12:31"
    },
    {
      "speaker": "Marc Ellery",
      "text": "Annual works if the quote reaches me by Friday.",
      "timestamp": "00:12:44"
    }
  ],
  "next_cursor": null
}
```

### list_action_items

The Action Items section of a call: text, assignee, whether it is done and whether a person wrote it. Access: read. REST: `GET /api/v1/fathom-video/calls/{call_id}/action-items`. MCP: `fathom_video_read → list_action_items`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `call_id` | string | yes | Call ID from list_calls: the number in the call address, fathom.video/calls/{call_id}. |

Returns every item in the Action Items section of one call. user_generated is true for items someone added by hand and false for items Fathom extracted after the call. completed is the state of the checkbox on the call page. timestamp is the moment in the recording the item was detected, when Fathom has one. A call without items returns an empty list, which is also what a Free account without Auto-Generate Action Items sees.

Example response:

```json
{
  "call_id": "610313346",
  "action_items": [
    {
      "item_id": "ai_8841",
      "description": "Send revised quote to Marc",
      "assignee": "Dana Whitfield",
      "completed": false,
      "user_generated": false,
      "timestamp": "00:14:05"
    },
    {
      "item_id": "ai_8842",
      "description": "Book legal review for annual terms",
      "assignee": "Priya Nair",
      "completed": true,
      "user_generated": true,
      "timestamp": null
    }
  ]
}
```

### get_call_sharing

Who can open a call: link access and each person added, with their access level. Access: read. REST: `GET /api/v1/fathom-video/calls/{call_id}/sharing`. MCP: `fathom_video_read → get_call_sharing`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `call_id` | string | yes | Call ID from list_calls: the number in the call address, fathom.video/calls/{call_id}. |

Returns the sharing details of the Share menu for one call. link_access is anyone_with_link, same_domain or only_people_added. people lists each person added by email with access limited, standard or admin. A call you can open but whose sharing details you cannot see, which is what Limited access gives, returns APP_PERMISSION_DENIED.

Example response:

```json
{
  "call_id": "610313346",
  "link_access": "anyone_with_link",
  "people": [
    {
      "email": "marc@example.com",
      "access": "standard"
    },
    {
      "email": "priya@example.com",
      "access": "admin"
    }
  ]
}
```

### get_settings

Your Fathom settings: which meetings are recorded, what is auto-shared and whether action items are generated. Access: read. REST: `GET /api/v1/fathom-video/settings`. MCP: `fathom_video_read → get_settings`.

No parameters.

Returns the settings from the Settings page that the agent can change: auto_record (all_meetings, external_meetings, internal_meetings or no_meetings), auto_share (summary_and_recording, summary_only or nothing), auto_generate_action_items and the default summary template. Fields that belong to a plan you are not on, such as auto-generate action items on Free, come back as null.

Example response:

```json
{
  "auto_record": "external_meetings",
  "auto_share": "summary_only",
  "auto_generate_action_items": true,
  "default_summary_template": "General"
}
```

### add_action_item

Add an action item to a call, as the plus icon on the call page does. Access: write, asks the user first. REST: `POST /api/v1/fathom-video/calls/{call_id}/action-items`. MCP: `fathom_video_write → add_action_item`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `call_id` | string | yes | Call ID from list_calls: the number in the call address, fathom.video/calls/{call_id}. |
| `description` | string | yes | Text of the action item. |

Adds one item to the Action Items section of a call, marked as written by a person. The item is open and assigned to you; assigning someone else is not part of this tool. If you connected a task manager or CRM in Settings, Fathom may sync the new item there. Nothing removes an item again through Cotlet, so each add waits for your OK. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "item_id": "ai_8843",
  "call_id": "610313346",
  "description": "Send NDA draft to Tom",
  "assignee": "Dana Whitfield",
  "completed": false,
  "user_generated": true
}
```

### update_action_item

Tick an action item as done or open again, or change its text. Access: write. REST: `PATCH /api/v1/fathom-video/items/{item_id}/action-item`. MCP: `fathom_video_write → update_action_item`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `item_id` | string | yes | Action item ID from list_action_items. |
| `completed` | boolean | no | true to mark done, false to reopen. |
| `description` | string | no | New text of the item. |

Sets completed on one item and, if you pass description, replaces its text. It reaches nobody and one more call puts it back, so it does not wait for your OK; if a task manager is connected in Settings, Fathom syncs the change itself. It works on items of calls you recorded, and on a team member's call only where your access lets you manage notes.

Example response:

```json
{
  "item_id": "ai_8841",
  "call_id": "610313346",
  "description": "Send revised quote to Marc",
  "completed": true
}
```

### share_call

Share a call with a person by email at the access level you choose. Access: write, asks the user first. REST: `POST /api/v1/fathom-video/calls/{call_id}/share`. MCP: `fathom_video_write → share_call`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `call_id` | string | yes | Call ID from list_calls: the number in the call address, fathom.video/calls/{call_id}. |
| `email` | string | yes | Email address of the person to share with. |
| `access` | enum | yes | limited, standard or admin. |

Adds one email address to the Share menu of the call at limited, standard or admin access, as in the Share dialog. Limited sees the transcript, summary and recording; standard also downloads the call and sees highlights and action items; admin also shares the link, trims the recording and edits the transcript. You need a role that allows sharing the call. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "call_id": "610313346",
  "email": "marc@example.com",
  "access": "standard",
  "status": "shared"
}
```

### remove_call_access

Take a person off the Share menu of a call. Access: write, asks the user first. REST: `DELETE /api/v1/fathom-video/calls/{call_id}/access`. MCP: `fathom_video_write → remove_call_access`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `call_id` | string | yes | Call ID from list_calls: the number in the call address, fathom.video/calls/{call_id}. |
| `email` | string | yes | Email address as shown by get_call_sharing. |

Clicks Remove next to one email in the sharing details, so that person can no longer open the call. It does not unsend the email they already got, and anyone with the link can still open a call whose link access is anyone_with_link. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "call_id": "610313346",
  "email": "marc@example.com",
  "status": "removed"
}
```

### set_link_access

Choose who can open the call link: anyone, your domain or only people added. Access: write, asks the user first. REST: `PUT /api/v1/fathom-video/calls/{call_id}/link-access`. MCP: `fathom_video_write → set_link_access`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `call_id` | string | yes | Call ID from list_calls: the number in the call address, fathom.video/calls/{call_id}. |
| `link_access` | enum | yes | anyone_with_link, same_domain or only_people_added. |

Sets the first choice of the Share menu on one call. anyone_with_link lets whoever holds the address view the recording. same_domain limits it to people on your email domain. only_people_added limits it to the people listed by get_call_sharing. People already added keep their access. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "call_id": "610313346",
  "link_access": "only_people_added",
  "previous": "anyone_with_link"
}
```

### regenerate_summary

Write the summary of a call again from a template, with extra instructions you give. Access: write, asks the user first. REST: `POST /api/v1/fathom-video/calls/{call_id}/summary/regenerate`. MCP: `fathom_video_write → regenerate_summary`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `call_id` | string | yes | Call ID from list_calls: the number in the call address, fathom.video/calls/{call_id}. |
| `template` | string | no | Name of a summary type as listed on the call page. Default: the one selected now. |
| `instructions` | string | no | Extra guidance for the AI, for example a tone or a section to add. |
| `apply_to_future` | boolean | no | true to keep the instructions for future summaries of this template. Default: false. |

Selects a summary template on the call page, adds your instructions with the gear icon and clicks Regenerate Summary. The new text replaces the summary shown on the call, including for people the call is shared with. Set apply_to_future to true to also click Apply to Future Summaries, which keeps the instructions for that template. Summary customization needs a Premium or Team plan. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "call_id": "610313346",
  "summary_template": "General",
  "applied_to_future": false,
  "summary": "## Summary\nThe client agreed to annual billing on the Team plan. Dana sends the revised quote by Friday."
}
```

### update_settings

Change which meetings Fathom records, what it shares after a call and whether it writes action items. Access: write, asks the user first. REST: `PATCH /api/v1/fathom-video/settings`. MCP: `fathom_video_write → update_settings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `auto_record` | enum | no | all_meetings, external_meetings, internal_meetings or no_meetings. |
| `auto_share` | enum | no | summary_and_recording, summary_only or nothing. |
| `auto_generate_action_items` | boolean | no | true to let Fathom extract action items after calls. |

Changes the Settings page fields that get_settings returns; fields you leave out stay as they are. auto_share decides what attendees on the calendar invite get after every call, so a change reaches other people. Auto-generate action items needs a Premium or Team plan. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "auto_record": "external_meetings",
  "auto_share": "nothing",
  "auto_generate_action_items": true,
  "default_summary_template": "General"
}
```

### delete_call

Delete a call recording and its notes. Access: write, asks the user first. REST: `DELETE /api/v1/fathom-video/calls/{call_id}`. MCP: `fathom_video_write → delete_call`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `call_id` | string | yes | Call ID from list_calls: the number in the call address, fathom.video/calls/{call_id}. |

Uses Delete Call from the three dots next to Share. Fathom removes the recording and all its notes, and says a deleted call cannot be recovered. People the call was shared with lose it too. Only calls you recorded, or any call an Account Admin can open, can be deleted. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "call_id": "610298114",
  "status": "deleted"
}
```

## How do I connect Fathom to Claude Code, Codex or Cursor?

Connecting Fathom takes three steps: sign up, sign in to Fathom once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Fathom to your agent.

1. **Create an account** Sign up and add Fathom in the console. Your API key is there too.

2. **Sign in to Fathom in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Fathom there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Fathom tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Go through my Fathom calls from the last 7 days. For each open action item, check later calls for proof it is done, tick the done ones and list the rest with a reason.
```

### Call Fathom from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/fathom-video with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/fathom-video/calls/610313346/share \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email":"marc@example.com","access":"standard"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "call_id": "610313346",
  "email": "marc@example.com",
  "access": "standard",
  "status": "shared"
}
```

## Why use Cotlet for Fathom?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Fathom yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Fathom changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Fathom to Cotlet?

Yes. You sign in to Fathom yourself, in your own Cloud Browser, and we never save your password. Your agents only get Fathom once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Fathom integration?**

No, Cotlet is independent of Fathom. Fathom's own API is too limited for this work. Cotlet works through your own Fathom account, the way you use Fathom in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Fathom in your console: your agents lose access at once and you stay signed in. Signing out of Fathom in the browser works too, and Reset browser deletes the whole profile.

## Is there a Fathom MCP server on GitHub?

Yes. Community Fathom MCP servers exist on GitHub, usually maintained by one person. Most wrap the same public API, so they read calls, summaries and transcripts and cannot change anything in a call. You install one yourself and keep it running; Cotlet hosts a server that works in your signed-in Fathom and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, create an API key in Fathom, add the server to each MCP client | Sign up, sign in to Fathom once, add one MCP server or API key |
| When Fathom changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Fathom access | An API key in a file on your computer, readable by any program you run | Your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Not an issue for a key; tools fail if you revoke or lose it | Your Cloud Browser keeps you signed in; if Fathom logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Fathom changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Fathom API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Fathom API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Fathom account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Fathom yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Fathom only after you enable it. When Fathom signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Fathom, sign out of Fathom in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Fathom's terms:** You use your own Fathom account and stay responsible for following Fathom's terms. Cotlet is independent and not affiliated with Fathom. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Fathom in the console and press Request access. Then you create your API key and connect Fathom there.

**Do I need to be technical?**

No. You sign in to Fathom once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Fathom to Cotlet?**

Yes. You sign in to Fathom yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Fathom once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Fathom sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Fathom cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Fathom's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Fathom sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Fathom login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Fathom offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Which Fathom plan do I need?**

Cotlet works in your own Fathom account on any plan, and your plan still sets what Fathom offers. Fathom documents Auto-Generate Action Items and summary customization as Premium and Team features, so on Free those tools return nothing or an error. Fathom says API access, keys and webhooks are on all plans.

**Which calls can my agent open?**

The calls your account can open: ones you recorded and ones shared with you or your team. Fathom keeps a private call visible to its host only, and an admin sees other people's calls only where the call is shared with them. Delete and sharing tools follow your role on each call.

**Can my agent post or send messages in Fathom without asking me?**

No. Every call to add_action_item, share_call, remove_call_access, set_link_access, regenerate_summary, update_settings or delete_call waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. update_action_item runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Fathom API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/fathom-video from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.