Connect Sumble to VS Code
Give VS Code governed access to Sumble’s 38 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Sumble 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 Sumble to Runlayer
Sumble 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, Sumble’s 38 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code setup guide - 3
Sign in to Sumble
Sign in the way Sumble requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Sumble from VS Code
Sumble’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
38 Sumble tools in VS Code
Runlayer policy decides which of these VS Code users can call.
Add contacts to list
Add people to an existing contact list.
Add organizations to list
Add organizations to an existing list.
Create contact list
Create a new contact list (people list).
Create organization list
Create a new organization list.
Find match and enrich jobs
The primary jobs tool: look up jobs by id or search the jobs corpus, and return exactly the attributes you ask for, with optional related people.
Find match and enrich organizations
Find, match, and enrich organizations in one call.
Find match and enrich people
The primary people tool: resolve people and return exactly the attributes you ask for, with optional related people and contact reveals.
Find match and enrich teams
Find the teams inside an organization and return selected attributes, related people, and job postings.
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 Sumble 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
