Connect Carta to VS Code
Give VS Code governed access to Carta’s 18 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Carta to VS Code in four steps
Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.
- 1
Approve Carta in Runlayer
Add Carta from the catalog and choose who can use it and which of its tools are allowed.
- 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, Carta’s 18 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code setup guide - 3
Sign in to Carta
Sign in the way Carta requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Carta from VS Code
Carta’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
18 Carta tools in VS Code
Runlayer policy decides which of these VS Code users can call.
Call tool
Run a Carta tool that search_tools found.
Cap table chart
Show a visual cap table summary with ownership breakdown by share class.
Discover
List available Carta commands or views across all domains.
Fetch
Execute a named Carta read command.
Get current user
Get the currently authenticated Carta user's profile.
List accounts
List all companies and organizations the current user has access to.
List contexts
Show which firms you have access to in Carta Fund Admin and which one is currently active.
List resources
List all available resources and resource templates.
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 Carta 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