Fathom MCP

Live

OAUTH 2.0

AI

AI

Connect to Fathom MCP to access AI meeting notes, summaries, transcripts, and recordings from your AI workflows.

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Fathom MCP
agent · Acme Q3
Run
Find Person in Fathom MCP
S
fathommcp_find_person
85ms
Fathom MCP agent
Find a person by name across meeting speakers, then return contact info and compact summaries for matched meetings. sear.
Sources: Fathom MCP
fathommcpmcp
1 tool call
18:29
Message Claude...

Fathom MCP tools for AI agents

CALL ANY TOOL
9 tools covering find, get.
fathommcp_find_person
Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
token = client.agent.get_token(user_id="user_id", connector="fathommcp")
const token = await client.agent.getToken({ userId: "user_id", connector: "fathommcp" });
const token = await client.agent.getToken({ userId: "user_id", connector: "fathommcp" });
token = client.agent.get_token(user_id="user_id", connector="fathommcp")
Try these prompts
Paste any prompt into your agent to get started.
Get started
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
Fathom MCP
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 MCP
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 MCP
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 MCP
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
See the same per-user auth pattern across other connectors.
No items found.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought.
01.
Shared tokens break per-user analytics
“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 OAuth 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 AI 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.

Which recordings and transcripts can the agent fetch?
Only meetings visible to the authorizing user in Fathom. Summaries, transcripts, and recordings follow the user's team sharing settings. Other people's calls stay private.

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"": {
""fathommcp"": {
""url"": ""https://mcp.scalekit.com/fathommcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.fathommcp]
url = ""https://mcp.scalekit.com/fathommcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""fathommcp"": {
""url"": ""https://mcp.scalekit.com/fathommcp"",
""type"": ""http""
}
}
}