Skip to main content

Connect Profound to VS Code

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

Set up

Add Profound 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 Profound to Runlayer

    Profound 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, Profound’s 61 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 Profound

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

  4. 4

    Use Profound from VS Code

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

Tools

61 Profound tools in VS Code

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

  • Add knowledge base document

    Add ONE new document (inline markdown text) to a knowledge base.

  • Archive project

    Preview or archive (retire) a project — set it aside without deleting it.

  • Create agent definition

    Create a draft agent definition — preview first, then apply on confirmation.

  • Create doc

    Create a new document in the Profound platform from content you have written.

  • Create project task

    Preview or add a task ("play") to a project.

  • Create prompts

    Create one or more prompts in a category.

  • Get agent

    Get details of an agent, including its input_schema.

  • Get agent definition

    Read back an agent's full workflow graph so you can copy and edit it.

See all 61 Profound 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 Profound 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