Connect Fathom to Crush
Give Crush governed access to Fathom’s 12 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Fathom to Crush in four steps
Admins approve the server once. Everyone in Crush then gets it through the same governed connection.
- 1
Add Fathom to Runlayer
Fathom isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Crush to Runlayer
Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches Fathom’s 12 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Crush setup guide - 3
Sign in to Fathom
Sign in the way Fathom requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Fathom from Crush
Fathom’s approved tools appear in Crush. Every call is checked against policy and recorded.
Tools
12 Fathom tools in Crush
Runlayer policy decides which of these Crush users can call.
Find person
Find a person by name across meeting speakers, then return contact info and compact summaries for matched meetings.
Find relevant meetings
Targeted ranked retrieval for specific facts, decisions, quotes, named projects, companies, products, people-plus-topic questions, or locating the best matching meetings.
Get identity
Returns the authenticated user's name and email address.
Get meeting summary
Returns the AI summary of a specific Fathom meeting.
Get meeting transcript
Returns the full transcript of a specific Fathom meeting.
Get recording by call ID
Resolve a Fathom call ID to a recording_id plus title, date, and url.
Get recording by URL
Resolve a Fathom URL to a recording_id plus title, date, and url.
Get relevant meetings result
Returns the find_relevant_meetings result for a search_id.
Control
What Runlayer can see and stop in Crush
Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.
Gateway policy (available)
Every Fathom call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.
Frequently asked questions
Connect more