> ## Documentation Index
> Fetch the complete documentation index at: https://docs.versuno.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# VS Code

> Connect Versuno MCP to VS Code with GitHub Copilot.

VS Code supports MCP through GitHub Copilot's agent mode. Config lives in an `mcp.json` file that can be scoped to a workspace or to your user profile.

## Workspace config

Create `.vscode/mcp.json` in your project:

```json theme={null}
{
  "servers": {
    "versuno": {
      "command": "npx",
      "args": ["-y", "versuno-mcp"],
      "env": {
        "VERSUNO_API_KEY": "uk_live_xxx"
      }
    }
  }
}
```

## User config

For a setup that applies to every workspace, open the command palette and run **MCP: Open User Configuration**. VS Code opens the user-level `mcp.json`.

Note the key is `servers`, not `mcpServers` like Cursor and Claude. This is a VS Code-specific variation.

## Remote (hosted HTTP)

To use Versuno's hosted server instead of `npx`, use the `http` type with your key as a bearer token:

```json theme={null}
{
  "servers": {
    "versuno": {
      "type": "http",
      "url": "https://mcp.versuno.ai/mcp",
      "headers": {
        "Authorization": "Bearer uk_live_xxx"
      }
    }
  }
}
```

The hosted server provides the read/query tools only — `pull_asset` and `push_asset` need local disk access, so use the `npx` config above for those.

## Enabling agent mode

1. Install the GitHub Copilot extension if you haven't already.
2. Open the Copilot chat panel.
3. Switch the mode selector from "Ask" to "Agent".

The Versuno tools appear in the tool picker. Agent mode asks for approval before running each tool.

## Reloading after changes

Run **MCP: Reload Servers** from the command palette after editing `mcp.json`, or reload the VS Code window.

## Troubleshooting

Check the **MCP** output channel (View > Output, then select "MCP" from the dropdown) for stderr from the server. See [Troubleshooting](/mcp/setup#troubleshooting) for common causes.