MCP for other agents

The extension’s engine includes an MCP server that offers the same tools Copilot gets. Any MCP client can use it.

Set it up

1. Run Vegha: Set Up MCP for Other Agents… from the Command Palette.
2. If several folders are open, pick the one the agent should work in.
3. Choose a format. Vegha copies it to your clipboard:
   • Claude Code: a claude mcp add vegha -- … command to paste into a terminal.
   • JSON config: an mcpServers entry for Cursor, Claude Desktop, Windsurf and other clients.

The JSON has this shape (paths are filled in for your machine):

{
  "mcpServers": {
    "vegha": {
      "command": "<extension folder>/sidecar/vegha-sidecar",
      "args": ["--mcp", "--workspace", "<your project folder>"]
    }
  }
}

If you’ve set vegha.dataDirectory, the copied command includes --data-dir so the agent shares the same history and cookies.

Note

The command points into the installed extension version. After the extension updates, run Set Up MCP for Other Agents… again and replace the old entry.

Inside VS Code

Copilot already has the tools natively. If you use another agent that reads servers from VS Code’s own MCP support, turn on vegha.mcp.exposeInVSCode. It’s off by default because Copilot would otherwise see every tool twice.

Approvals and secrets

MCP clients apply their own approval prompts. The same redaction rules apply: secrets are shown as «redacted» and responses are marked as untrusted data. See Overview & safety.