Skip to main content
Book a demo

Connect Granola to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add Granola 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

    Approve Granola in Runlayer

    Add Granola from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect GitHub Copilot to Runlayer

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Granola

    Sign in the way Granola requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Granola from GitHub Copilot

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

Tools

7 Granola tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call. 4 read data only.

  • Get account info

    Get the email, active workspace, joined workspaces (names and IDs), and effective note-access scopes for the Granola account currently connected to this MCP session.

  • Get meeting transcript

    Get the full transcript for a specific Granola meeting by ID.

  • Get meetings

    Get detailed meeting information for one or more Granola meetings by ID.

  • List meeting folders

    List the user's Granola meeting folders.

  • List meetings

    List the user's Granola meeting notes within a time range.

  • Query Granola meetings

    Query Granola about the user's meetings using natural language.

  • Switch workspace

    Change your saved active Granola workspace.

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 Granola 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