Skip to main content
Book a demo

Connect Fathom to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add Fathom to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot 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 GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Fathom’s 12 tools through the plugin’s search and execute tools.

    GitHub Copilot 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 GitHub Copilot

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

Tools

12 Fathom tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot 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 GitHub Copilot

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination