Before you start

VS Code 1.99 or later
GitHub Copilot subscription with Agent mode enabled
Node.js 18+ (for npx @agentvalet/register)
Note: MCP in VS Code requires Agent mode - it is not available in inline completions or regular Copilot Chat. Make sure Agent mode is enabled under GitHub Copilot > Agent in settings.

Add AgentValet to .vscode/mcp.json

VS Code uses the key servers (not mcpServers - that's a common mistake). Create .vscode/mcp.json in your project root.

.vscode/mcp.json
{
  "servers": {
    "agentvalet": {
      "url": "https://api.agentvalet.ai/mcp/v1/…",
      "type": "http"
    }
  }
}
Key name matters: VS Code uses "servers", not "mcpServers". If you've used Cursor before, double-check this - it's the most common setup mistake.

Get connected in 4 steps

1
Run npx @agentvalet/register in your project directory. This generates an RS256 keypair, records your agent in the registry, and outputs your OWNER_ID.
2
Create .vscode/mcp.json with the config above. Use "servers" as the root key and substitute your OWNER_ID.
3
Open the VS Code command palette (Cmd/Ctrl+Shift+P) and run "MCP: List Servers" to confirm agentvalet is loaded. If it doesn't appear, reload the VS Code window.
4
Open Copilot Chat in Agent mode. AgentValet tools are now available to the agent - platforms you've approved in the dashboard appear as callable tools.

Your agent, governed

Works with Cline & Continue
Any MCP-aware VS Code extension picks up AgentValet automatically - not just Copilot Agent mode.
No keys in .env
API keys never sit in your project directory. Credentials are decrypted in-memory inside the AgentValet proxy at call time.
Scoped per platform
Set exactly what each agent can do per platform. GitHub read-only stays read-only, even if the agent tries to write.
Full audit trail
Every call logged: agent, platform, action, timestamp. Revoke instantly from the dashboard if something looks wrong.

Ready to connect VS Code?

Register free, get your OWNER_ID, and drop in the config. Takes under 2 minutes.