Skip to main content
Book a demo

Connect Lucid to VS Code

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

Book a demo VS Code setup guide

Set up

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

    Add Lucid 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, Lucid’s 42 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 Lucid

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

  4. 4

    Use Lucid from VS Code

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

Tools

42 Lucid tools in VS Code

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

  • Create embed

    Internal tool for MCP Apps extension only.

  • Create embed session token

    Internal tool for MCP Apps extension only.

  • Exchange legacy embed session

    Internal tool for MCP Apps extension only.

  • Fetch Lucid document content

    Retrieves the structured content of a specific Lucid document by its ID.

  • Get MCP resource

    Reads a resource from this MCP server by URI.

  • List document thread comments

    List comments on a specific collaboration thread of a Lucid document.

  • List document threads

    List collaboration threads on a Lucid document.

  • Add block

    Add a new block (shape) to a Lucid document.

See all 42 Lucid tools

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