Connect Harmonic to VS Code
Give VS Code governed access to Harmonic’s 47 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Harmonic to VS Code in four steps
Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.
- 1
Add Harmonic to Runlayer
Harmonic isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 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, Harmonic’s 47 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code setup guide - 3
Sign in to Harmonic
Sign in the way Harmonic requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Harmonic from VS Code
Harmonic’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
47 Harmonic tools in VS Code
Runlayer policy decides which of these VS Code users can call.
Add companies to list
Add companies to an existing company list.
Add people to list
Add people to an existing people list.
Create company list
Create a new company list.
Create company list custom field
Create a custom field (column) for a company list.
Create global custom field
Create a new global custom field for companies or people.
Create list
Create an empty company, person, or investor list in the workspace's shared project.
Create list custom field
Create a custom field on any company, person, or investor list.
Create list entries
Add Harmonic companies, people, or investors to an existing list by creating list entries from their URNs.
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 Harmonic 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
