Fathom

Live

BEARER TOKEN

CALL INTELLIGENCE

Every call recording, transcript, and AI summary your team captures lives in Fathom. Fathom MCP gives your agent authenticated access to call data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Fathom account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Fathom
agent · Acme Q3
Run
What action items came out of my last three customer calls this week?
S
fathom_action_items
82ms
Meeting intelligence agent
9 action items across 3 calls. Top: send pricing deck to Acme (you, due Fri), schedule follow-up with Globex (Sarah, open), share onboarding doc with Initech (you, open).
Sources: 3 calls, this week
fathommcp
9 items
18:29
Message Claude...

Tools your meeting intelligence agent reaches for on Fathom, scoped per user.

CALL ANY TOOL
List calls, fetch transcripts, retrieve AI summaries, and pull action items from recorded meetings.
fathom_calls_list
List calls
List recorded calls with optional date range and participant filters.
Parameters
Name
Type
Required
Description
limit
integer
Optional
Max calls to return
after
string
Optional
ISO 8601 lower bound
before
string
Optional
ISO 8601 upper bound
fathom_call_get
Get call
fathom_call_transcript
Get transcript
fathom_call_summary
Get summary
fathom_action_items
Get action items
Build your Agent
Drop the toolkit in, point it at the user, and your meeting intelligence agent can use Fathom from the first run.
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["fathom"], toolNames: ["fathom_calls_list", "fathom_call_get", "fathom_call_transcript"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["fathom"], toolNames: ["fathom_calls_list", "fathom_call_get", "fathom_call_transcript"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["fathom"], toolNames: ["fathom_calls_list", "fathom_call_get", "fathom_call_transcript"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/fathom",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Fathom.
Search & recall
Copy the prompt
Copied
List all calls recorded this week.
Copy the prompt
Copied
Find calls with [person name].
Copy the prompt
Copied
Get the transcript from [call name].
Copy the prompt
Copied
Which calls had [topic] discussed?
Summaries & actions
Copy the prompt
Copied
Summarize my last 5 sales calls.
Copy the prompt
Copied
Get action items from [call name].
Copy the prompt
Copied
Which action items are still open from this week?
Copy the prompt
Copied
What were the key decisions in [call name]?
Coaching & reporting
Copy the prompt
Copied
Which calls lasted over 60 minutes?
Copy the prompt
Copied
Find calls where pricing came up.
Copy the prompt
Copied
List all calls with [account name] this month.
Copy the prompt
Copied
Summarize what was discussed with [company].
SEE HOW AUTH WORKS
Users authorize Fathom once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Fathom
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Fathom
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Fathom
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Fathom
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other meeting intelligence agents and MCP connectors. Working code, live demos, fork what fits.
SALES
Deal intelligence agent
Combine Gong, Attio, and Slack signals to surface deal risks and next-best actions. Updated after every call.
SALES
Sales call prep agent
Pull Granola notes and Attio contact history to draft a pre-call brief before every sales meeting. Zero rep input.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Fathom today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Fathom as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Fathom bearer token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Fathom?
Yes. Pass a tool name filter to listScopedTools so the meeting intelligence agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Fathom.

What happens when a user revokes Fathom access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent surface recordings from other reps in the workspace?
Only recordings the authorizing user can see in Fathom. Personal recordings stay per-user. Shared recordings appear only if explicitly shared with the authorizing user in the workspace.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""fathom"": {
""url"": ""https://mcp.scalekit.com/fathom"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.fathom]
url = ""https://mcp.scalekit.com/fathom""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""fathom"": {
""url"": ""https://mcp.scalekit.com/fathom"",
""type"": ""http""
}
}
}