Skip to main content

Connect Fathom to Hermes

Give Hermes governed access to Fathom’s 12 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Fathom to Hermes in four steps

Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.

  1. 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. 2

    Connect Hermes to Runlayer

    Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches Fathom’s 12 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Hermes setup guide
  3. 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. 4

    Use Fathom from Hermes

    Fathom’s approved tools appear in Hermes. Every call is checked against policy and recorded.

Tools

12 Fathom tools in Hermes

Runlayer policy decides which of these Hermes 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.

See all 12 Fathom tools

Control

What Runlayer can see and stop in Hermes

Some controls apply to every client at the gateway. Others depend on what Hermes exposes to Runlayer.

  • Gateway policy (available)

    Every Fathom call from Hermes passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Hermes as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Hermes runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output in Hermes and show a message in its place.

  • Redact output in place (not available)

    Hermes cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Hermes

  • Hermes can replace blocked tool output with a message, but its after-call event is for monitoring only.

Frequently asked questions

Connect more

Find another combination