OAUTH 2.0
AI
Connect to Fathom MCP to access AI meeting notes, summaries, transcripts, and recordings from your AI workflows.
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")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.