--- title: "Connect Ken to VS Code and GitHub Copilot with MCP" description: "Add Ken's remote MCP server to VS Code with OAuth or an API key: exact steps checked against the vendor's docs, example prompts and fixes." path: /mcp/vs-code family: mcp updated: 2026-10-17 html: /mcp/vs-code sources: - "https://code.visualstudio.com/docs/copilot/customization/mcp-servers" - "https://code.visualstudio.com/docs/copilot/reference/mcp-configuration" - "https://code.visualstudio.com/api/extension-guides/ai/mcp" - "https://docs.github.com/en/copilot/how-tos/provide-context/use-mcp/extend-copilot-chat-with-mcp" facts: client: "VS Code by Microsoft" transport: "Remote HTTP" auth: "OAuth sign-in, or an API key header from an input variable" server_url: "https://mcp.ken.so/mcp" client_plan_needed: "Any Copilot plan. Copilot Business and Enterprise need the MCP servers in Copilot policy, which is off by default." platforms: "VS Code desktop with GitHub Copilot" --- # Connect Ken to VS Code and GitHub Copilot with MCP VS Code with GitHub Copilot connects to Ken's remote MCP server over HTTP. Run MCP: Add Server, choose HTTP, paste Ken's server URL, then start it and sign in to Ken. Copilot Business and Enterprise need the MCP servers in Copilot policy turned on. ## How Do You Connect Ken to VS Code? **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. **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. **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. **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. **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. **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. ## Can You Use a Ken API Key Instead of OAuth? **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. **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}" } } } } ``` ## What Can You Ask Ken From VS Code? **In short:** Ask in plain language. The client picks the Ken tool, and Ken runs it with your workspace role. **Example requests in VS Code and the Ken MCP tool that answers each one** | Ask | Ken tool used | What the tool does | | --- | --- | --- | | Find VPs of Sales at US software companies with 50 to 200 employees. | search_read | Searches Ken's people and company database and returns filter facets. | | Load Ken's campaign-planning skill and plan a 3-step cold email campaign for that list. | load_skill | Loads one Ken workflow skill, such as campaign-planning, into the chat. | | Before I launch, preview who lands in the Series B segment. | segments_read | Previews which contacts land in a campaign segment. | | How many emails a day can this campaign send with the inboxes it has? | campaign_flow_read | Estimates how many emails a campaign can send with its inboxes. | | Which of my campaigns are running right now? | campaigns_read | Lists campaigns and reads one campaign's settings and status. | | How did my campaigns do this week? Show sends, replies and bounces for each one. | analytics_read | Reads campaign performance, engagement, deliverability and reply classifications. | Admins and members get read and write tools. View-only members get read tools plus inbox replies. ## What If Ken Does Not Connect in VS Code? **In short:** Most failures come from a skipped sign-in step or a client setting. **Common VS Code connection problems and fixes** | Problem | Fix | | --- | --- | | Ken shows an error in the Chat view | Run MCP: List Servers, select ken and choose Show Output to read the log. | | Ken does not start in a workspace | Workspace MCP servers follow Workspace Trust and are blocked in Restricted Mode. Trust the workspace, or run MCP: Reset Trust and start Ken again. | | The Ken sign-in keeps failing after a reinstall | Run Authentication: Remove Dynamic Authentication Providers, remove Ken's entry, then start the server again so VS Code registers a fresh client. | | A Ken tool answers "Missing scope" | Part of the Ken approval screen was declined. Remove Ken from the client, add it again and select Allow access. | ## Frequently Asked Questions ### Which GitHub Copilot plans can use Ken over MCP? Copilot Free, Pro, Pro+ and Max are not governed by the MCP policy. On Copilot Business and Enterprise, an admin must turn on the MCP servers in Copilot policy, which is off by default. ### Where should I save Ken in VS Code? Save it to Copilot Global to have Ken in every workspace, or to .mcp.json at the workspace root to commit Ken for your team. VS Code still offers .vscode/mcp.json and the user-profile mcp.json, but marks both deprecated. Each person still signs in with their own Ken account. ### Does VS Code ask before Ken runs a tool? VS Code can ask you to confirm each tool call in chat, and Configure Tools lets you switch individual Ken tools off. ### What can Copilot change in my Ken workspace? Only what your Ken role allows. Admins and members get read and write tools, including campaign launches. View-only members get read tools plus inbox replies. Ken checks your role on every call, so a role change applies right away. ## Related - [Ken MCP server](/mcp): What Ken's MCP server does and every client it works with - [Claude MCP: Connect Ken as a Custom Connector](/mcp/claude) - [ChatGPT MCP: Connect Ken as a Custom MCP Server](/mcp/chatgpt) - [Claude Code MCP: Connect Ken](/mcp/claude-code) - [Cursor MCP: Connect Ken](/mcp/cursor) - [Codex MCP: Connect Ken to OpenAI Codex](/mcp/codex) - [Gemini CLI MCP: Connect Ken](/mcp/gemini-cli) - [Connect Ken to Perplexity with MCP](/mcp/perplexity) - [Connect Ken to Claude Desktop with MCP](/mcp/claude-desktop) - [Ken pricing](/pricing): Plans and credit prices ## Sources | Source | URL | Checked | | --- | --- | --- | | VS Code docs: add and manage MCP servers | https://code.visualstudio.com/docs/copilot/customization/mcp-servers | 2026-10-17 | | VS Code docs: MCP configuration reference | https://code.visualstudio.com/docs/copilot/reference/mcp-configuration | 2026-10-17 | | VS Code docs: MCP developer guide | https://code.visualstudio.com/api/extension-guides/ai/mcp | 2026-10-17 | | GitHub Docs: extend Copilot Chat with MCP | https://docs.github.com/en/copilot/how-tos/provide-context/use-mcp/extend-copilot-chat-with-mcp | 2026-10-17 | ## Changelog - 2026-10-17: Page published.