VS Code (GitHub Copilot Agent mode)

VS Code supports MCP through GitHub Copilot in Agent mode. Configuration uses an mcp.json file with a top-level servers key. MCP support is generally available in VS Code 1.102+ and requires GitHub Copilot access.

Project Scope

For the configuration to work just within one project, create .vscode/mcp.json in the project root. This is useful if you wish to maintain multiple similar projects and define a different API key in each, e.g. if you have scoped the API key for a specific Veyo Project. This ensures the MCP will query the correct Veyo project.

{
  "servers": {
    "veyo-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@darkloop/veyo-mcp@latest"],
      "env": {
        "VEYO_API_URL": "https://portal.veyomcp.com",
        "VEYO_API_KEY": "YOURAPIKEYHERE"
      }
    }
  }
}

User Scope

This is the most simple, as it will add Veyo tools automatically to any project you open in VS Code, however it will always query the same Veyo project. To easily switch projects, modify the "Default Project" on your Veyo dashboard to match the dev project you're working on.

Open the Command Palette (Ctrl/Cmd+Shift+P) and run MCP: Open User Configuration, then add the same JSON as above.

CLI Alternative

You can install Veyo from the command line with:

code --add-mcp '{"name":"veyo-mcp","command":"npx","args":["-y","@darkloop/veyo-mcp@latest"],"env":{"VEYO_API_URL":"https://portal.veyomcp.com","VEYO_API_KEY":"YOURAPIKEYHERE"}}'

The first time you use Veyo, VS Code will prompt you to trust the server. Run MCP: List Servers from the Command Palette to verify the connection status.