Connect VS Code (Copilot) to Caryvane

VS Code's agent mode speaks MCP over HTTP. One JSON file in the workspace, the key prompted for once and stored securely, and Copilot has every Caryvane tool.

Set up #

1. Create a key (console → your name → AI access keys) at the tier you want VS Code to have.
2. Add .vscode/mcp.json to the workspace:

   {
     "inputs": [
       { "id": "caryvane-key", "type": "promptString", "password": true,
         "description": "Caryvane access key" }
     ],
     "servers": {
       "caryvane": {
         "type": "http",
         "url": "https://console.caryvane.com/mcp/rpc",
         "headers": { "Authorization": "Bearer ${input:caryvane-key}" }
       }
     }
   }

   The inputs block means the key is never written to the file: VS Code asks for it once and keeps it in its secret storage. The file is safe to commit.
3. Start the server from the MCP: Servers view (or the code lens in the file), enter the key when prompted.
4. Open Copilot Chat in agent mode and tick the Caryvane tools in the tools picker.

Use #

The same tools and permission tiers as Claude. Typical in a workspace: "list the storage targets and which last tested OK", "why did job 14 warn last night?", "enrol this machine" (which returns the ready-to-run install command).

For every workspace #

Put the same servers block in your user settings.json under "mcp" instead, and it is available everywhere.

Microsoft 365 Copilot and Copilot Studio #

The Copilot your staff use in Teams and Outlook reaches Caryvane through Copilot Studio rather than a JSON file. Build an agent there, give it Caryvane as a tool, then publish the agent to Microsoft 365 Copilot.

1. Create a key in the console at the tier the agent should have. Read only is the right default for something a whole helpdesk can talk to.
2. In Copilot Studio, open your agent → Tools → Add tool → New tool → Model Context Protocol.
3. Server URL: https://console.caryvane.com/mcp/rpc.
4. Authentication: choose API key, with the location set to Header. Header name Authorization, value Bearer followed by your key. These are the same three values the console offered a copy button for.
5. Save and test in the Copilot Studio test pane, then publish the agent to Microsoft 365 Copilot for the people who need it.

Two things worth knowing. Copilot Studio has no OAuth path to Caryvane, so API key is the option to pick, not a fallback. And the agent inherits the key’s tier and the key owner’s customer visibility, so everyone talking to that agent sees what that one user sees — give it its own key rather than reusing a person’s.