Skip to main content

Connect Navattic to VS Code

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

Set up

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

    Add Navattic to Runlayer

    Navattic isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  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, Navattic’s 62 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 Navattic

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

  4. 4

    Use Navattic from VS Code

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

Tools

62 Navattic tools in VS Code

Runlayer policy decides which of these VS Code users can call.

  • Create brain asset

    Add a URL, FILE, or TEXT asset to an agent's brain.

  • Create launchpad share link

    Create a launchpad share link, sourced from either a set of custom flows or a demo.

  • Delete brain asset

    Permanently delete a Brain asset.

  • Get account

    Get a detailed profile for a specific company account by ID.

  • Get agent demo

    Get a Navattic agent's configuration — objective, personality, tone, FAQs, pronunciations, CTA, welcome screen, language, voice, avatar, escalation/interruption flags, and the linked environment.

  • Get agent demo session

    Get full details for a Navattic agent session: parsed transcript turns, qualifications, summary, sentiment, signals detected, outcome reached, status, end user, and the Steel session viewer URL for…

  • Get agent environment

    Get an agent environment and its folder/flow tree.

  • Get demo

    Get a specific demo.

See all 62 Navattic 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 Navattic 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