Connect Ken to VS Code and GitHub Copilot with MCP

In short Add https://mcp.ken.so/mcp as a remote MCP server in VS Code, then sign in to Ken in your browser.

1. 01

   Run MCP: Add Server

   Open the Command Palette and run MCP: Add Server, or open Chat: Open Customizations, go to MCP Servers and select Add Server. Choose HTTP.

2. 02

   Enter Ken's URL and a Server ID

   Paste the URL below, enter ken as the server ID, and pick where to save it. VS Code recommends a portable destination for new servers: Copilot Global (~/.copilot/mcp-config.json) for every workspace, or .mcp.json at the workspace root to share Ken with your team. The .mcp.json option appears when the experimental chat.mcp.workspaceRootConfig.enabled setting is on.

   https://mcp.ken.so/mcp

3. 03

   Check the Saved Entry

   In VS Code's own mcp.json format (.vscode/mcp.json or your user profile), which VS Code still offers but marks deprecated, the entry looks like this. The portable files use a top-level mcpServers key instead of servers.

   {
     "servers": {
       "ken": {
         "type": "http",
         "url": "https://mcp.ken.so/mcp"
       }
     }
   }

4. 04

   Start Ken and Sign In

   Start the server from MCP: List Servers if it does not start on its own, and trust it when VS Code asks. VS Code registers itself with Ken and opens the sign-in. Your browser opens the Ken sign-in. Sign in with the account you use in the Ken app, then select Allow access on the Ken approval screen. You never paste a client ID or secret.

5. 05

   Turn On Ken's Tools in Chat

   In the Chat view, select Configure Tools in the chat input and make sure Ken's tools are on.

In short Yes. VS Code can send your Ken API key as a Bearer token when a browser sign-in is not an option.

1. 01

   Use a Ken API Key Header Instead

   Create a key in the Ken app under Settings > Integrations > API Keys. VS Code asks for the input the first time the server starts and stores it securely, so the key never sits in the file. Input variables only work in VS Code's own mcp.json format (.vscode/mcp.json or your user profile), not in the portable files.

   {
     "inputs": [
       {
         "type": "promptString",
         "id": "ken-api-key",
         "description": "Ken API key",
         "password": true
       }
     ],
     "servers": {
       "ken": {
         "type": "http",
         "url": "https://mcp.ken.so/mcp",
         "headers": {
           "Authorization": "Bearer ${input:ken-api-key}"
         }
       }
     }
   }

In short Ask in plain language. The client picks the Ken tool, and Ken runs it with your workspace role.

In short Most failures come from a skipped sign-in step or a client setting.