> ## Documentation Index
> Fetch the complete documentation index at: https://onecli.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Read Fathom Meeting Summaries From AI Agents

> Let agents list Fathom meetings and read summaries and transcripts. Connect in one click with OAuth on OneCLI Cloud, with no API key to manage.

## Overview

OneCLI connects AI agents to [Fathom](https://fathom.video) through OAuth. Agents can list meetings and read recording summaries and transcripts. The gateway injects the token into every request, so your agent never sees it.

On OneCLI Cloud, connecting takes one click. Self-hosted, you first add your own Fathom app (see the bottom of this page).

## What you will set up

* A Fathom connection through OAuth
* Automatic token injection on every Fathom request
* Per-agent, per-tool access to meeting content

## Connect Fathom

**1. Click Connect**

In the OneCLI dashboard, open **Connections** > **Fathom** and click **Connect Fathom**.

![OneCLI connect window for Fathom, showing the setup guide link and the Connect to Fathom button.](https://mintcdn.com/chartdbinc/L4k9tYUENUtEpMY8/images/integrations/fathom/onecli-connect-fathom.png?fit=max\&auto=format\&n=L4k9tYUENUtEpMY8\&q=85\&s=ff12b05c6f23e8f1ece40e790f7b26a5)

The Fathom connect window in OneCLI.

**2. Authorize in Fathom**

Sign in to Fathom and click **Authorize**. You're done.

## What agents can do

| Area | What agents can do |
| - | - |
| **Meetings** | List meetings, read recording summaries and transcripts |
| **Team** | List teams and team members |
| **Webhooks** | Create and delete webhooks |

## Controlling access

[Grant](https://onecli.sh/docs/guides/agent-access.md) the connection to each agent that needs it, and choose per tool what runs freely, what needs approval, and what's blocked. Meeting content is sensitive, so grant only the agents that need it. Organization [rules](https://onecli.sh/docs/guides/rules.md) add guardrails on top. A blocked request never reaches Fathom.

To disconnect, remove the connection in **Connections** > **Fathom**, then revoke OneCLI in Fathom's connected apps settings.

***

## Self-hosted: use your own Fathom app

> [!NOTE]
>
> **Skip this section on OneCLI Cloud.** Self-hosted OneCLI needs either `FATHOM_CLIENT_ID` and `FATHOM_CLIENT_SECRET` on the server, or your own Fathom app added below.

> [accordion] 1. Register the Fathom app
>
> Open [fathom.video/marketplace\_applications/new](https://fathom.video/marketplace_applications/new) and register an app named `OneCLI`.

> [accordion] 2. Add the redirect URL
>
> In OneCLI, open **Connections** > **Fathom** > **Custom credentials** and copy the **Redirect URI**. Paste it into the Fathom app's redirect URL and save.
>
> ![OneCLI Custom credentials card for Fathom with the setup guide link, the Redirect URI and its copy button, and the client ID and secret fields.](https://mintcdn.com/chartdbinc/L4k9tYUENUtEpMY8/images/integrations/fathom/onecli-custom-credentials-fathom.png?fit=max\&auto=format\&n=L4k9tYUENUtEpMY8\&q=85\&s=be1d133d80f47ce63e6854a2b8514898)
>
> Copy the Redirect URI from Custom credentials in OneCLI.

> [accordion] 3. Connect with your app
>
> Copy the app's **Client ID** and **Client Secret** into **Custom credentials**, turn it on, then click **Connect Fathom**.

## FAQ

> [accordion] Do I need a Fathom API key?
>
> No. On OneCLI Cloud you connect with OAuth in one click. Self-hosted, you add your own Fathom app first. See [Self-hosted](#self-hosted).

> [accordion] Does the agent see my Fathom token?
>
> No. The token stays in OneCLI, and the gateway adds it to each request at the proxy. See [How it works](https://onecli.sh/docs/how-it-works.md).

> [accordion] How do I reconnect or revoke Fathom?
>
> Reconnect from **Connections** > **Fathom**. To revoke, remove the connection, then revoke OneCLI in Fathom's connected apps settings.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.