Skip to main content
Book a demo

Connect Granola to VS Code

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

Book a demo VS Code setup guide

Set up

Add Granola to VS Code in four steps

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

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Granola’s 7 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code 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 VS Code

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

Tools

7 Granola tools in VS Code

Runlayer policy decides which of these VS Code 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 VS Code

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

  • Gateway policy (available)

    Every Granola call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, VS Code 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 VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination