Connect VS Code + GitHub Copilot

Optional IDE path — OAuth setup with click-path instructions. Share links still work for everyone else.

MCP is optional. Share links open a role in your ChatGPT, Claude, or Gemini—no install. Teammates get roles via org invite and the org marketplace. Connect VS Code + GitHub Copilot when you want the same roles in your IDE.

Setup steps

Connect chamelAIn to VS Code + GitHub Copilot with OAuth (recommended).

Open VS Code MCP settings
VS Code → Command Palette (Ctrl+Shift+P / Cmd+Shift+P) → MCP: Open User Configuration — or edit .vscode/mcp.json in your workspace.
Add the chamelAIn server
Under the top-level servers key, add the chamelAIn entry from the configuration below.
Enable agent mode tools
Open GitHub Copilot Chat, switch to Agent mode, and ensure MCP tools are enabled for the workspace.
Restart VS Code
Reload the window (Developer: Reload Window) after saving MCP settings.
Sign in on first connect
When Copilot invokes chamelAIn tools, complete browser OAuth sign-in and approve access on the consent screen.

Configuration

{
  "servers": {
    "chamelain": {
      "url": "https://mcp.chamelain.com/mcp"
    }
  }
}

Use the URL-only configuration. Do not add Authorization headers when using OAuth.

After connecting, ask your client to list chamelAIn personas, or type `#<tag>` (for example `#clarity-architect`) to load a persona.

For a fallback access key, open your dashboard → MCP CONNECT → choose VS Code + GitHub Copilot → Access key (fallback) tab.