Skip to main content
Book a demo

Connect Fireflies to VS Code

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

Book a demo VS Code setup guide

Set up

Add Fireflies 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 Fireflies in Runlayer

    Add Fireflies 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, Fireflies’s 8 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 Fireflies

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

  4. 4

    Use Fireflies from VS Code

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

Tools

8 Fireflies tools in VS Code

Runlayer policy decides which of these VS Code users can call. 8 read data only.

  • Get meeting details

    Fetches detailed meeting transcript by ID, with optional field filtering.

  • Get meeting summary

    Fetches meeting summary by ID, with optional field filtering.

  • Search meetings

    Queries multiple meeting transcripts using filter properties (date, keyword, email, etc.).

  • Get user details

    Fetches user account details.

  • Get user groups

    Fetches user groups for the authenticated user or their team.

  • Get user contacts

    Fetches contact list for the authenticated user.

  • Search meeting transcripts

    Advanced search for meeting transcripts using a mini grammar.

  • Fetch meeting details

    Retrieve complete meeting transcript with full conversation, metadata, and insights for a specific meeting ID.

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