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

# VS Code setup

> Connect GitHub Copilot Agent mode in VS Code to Fortress MCP.

Use VS Code when Fortress should be available to GitHub Copilot Agent mode.

## Choose config location

VS Code MCP configuration can live in the user profile or in a workspace file:

```text theme={"theme":"github-dark"}
.vscode/mcp.json
```

Use user-level config for personal bearer tokens. If you use workspace config, keep `.vscode/mcp.json` out of version control unless the token is replaced with a secure input variable.

## Add Fortress

Generate a **VS Code** setup snippet in Fortress and paste it into `mcp.json`:

```json theme={"theme":"github-dark"}
{
  "servers": {
    "fortress-agent": {
      "type": "http",
      "url": "https://api.fortressproductivity.com/mcp?agent_id=<agent-id>",
      "headers": {
        "Authorization": "Bearer ft_<token>"
      }
    }
  }
}
```

VS Code uses `servers`, not `mcpServers`, and HTTP servers require `type: "http"`.

## Verify

Open Copilot Chat, switch to Agent mode, enable the Fortress server in the tools picker, and ask Copilot to read `fortress://workspace/overview`.

See VS Code's [MCP configuration reference](https://code.visualstudio.com/docs/copilot/reference/mcp-configuration).