Behavry Integration — VS Code + GitHub Copilot
VS Code 1.99+ supports MCP servers for use with GitHub Copilot Chat. The configuration file uses the key servers (not mcpServers like other clients).
Requires: VS Code 1.99 or later + GitHub Copilot extension.
Prerequisites
- Behavry stack running (
make devordocker compose up) - VS Code 1.99+
- GitHub Copilot extension installed and active subscription
- Python 3.11+
Config File Locations
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Code/User/mcp.json |
| Windows | %APPDATA%\Code\User\mcp.json |
| Linux | ~/.config/Code/User/mcp.json |
Quick Setup
make setup
This detects VS Code, provisions a vscode-local agent, and merges into the VS Code MCP config — all in one step.
After setup, reload the VS Code window: Command Palette → Developer: Reload Window
To connect only VS Code:
cd backend && poetry run python ../demos/setup/create_dev_agent.py --client vscode
Note: VS Code uses
"servers"(not"mcpServers") as the top-level key inmcp.json.
Verify
- Open Copilot Chat (
Ctrl+Alt+I) - Click the tools icon — Behavry servers should appear
- Ask: "Using the filesystem tool, list files in /workspace"
- Check http://localhost:5173 → Live Activity
Token Refresh
Tokens expire in ~8 hours. Refresh all enrolled editors at once:
make tokens
Then reload the VS Code window (Developer: Reload Window).
Troubleshooting
MCP servers not visible in Copilot Chat
- Confirm VS Code version is 1.99+:
Help > About - Confirm the Copilot Chat extension is installed and you are signed in
- Reload the window after applying the config
"servers" key vs "mcpServers"
VS Code uses "servers" (not "mcpServers"). If you copy config from another client, update the key name.
Backend not reachable
Run curl http://localhost:8000/health to confirm the Behavry stack is up.