Agents

Uteke for GitHub Copilot in VS Code

Microsoft · Coding agent · MCP + API key · Beta

Copilot agent mode in Visual Studio Code.

Beta: written from GitHub Copilot in VS Code's own documentation and not tested by us yet. If a step does not match what you see, follow GitHub Copilot in VS Code's docs and tell us at [email protected].

Set it up

  1. Create an API key at API keys in the Uteke portal.
  2. Add Uteke to your MCP config; VS Code asks for the key the first time and stores it:
    .vscode/mcp.json (or your user mcp.json) 
    {
  "inputs": [
    { "type": "promptString", "id": "uteke-key", "description": "Uteke API key", "password": true }
  ],
  "servers": {
    "uteke": {
      "type": "http",
      "url": "https://uteke.app/mcp",
      "headers": { "Authorization": "Bearer ${input:uteke-key}" }
    }
  }
}

  3. Open Copilot Chat in agent mode and check that the uteke tools are listed.

API keys are made at API keys in the portal; choose read-only if the agent only needs to recall. A key works only for your workspace.

Uteke's sign-in registers clients through their published client metadata (CIMD); this client's docs describe a different registration, so use an API key.

Try it

Ask GitHub Copilot in VS Code:

  • Remember that we release from main only, never from develop.
  • What did we decide about pricing last week?
  • Save this summary to the team room.

Then ask the same thing from another agent you connected: they share one memory.

Disconnect

Open Agents in the portal and choose Disconnect. It works for agents that signed in and for API keys; access is checked again within about 30 seconds. You can also remove Uteke in GitHub Copilot in VS Code's own settings.

GitHub Copilot in VS Code's documentation on MCP servers: https://code.visualstudio.com/docs/copilot/customization/mcp-servers

Other agents: see all agents or the general steps.