Skip to main content
Visual Studio Code supports MCP servers natively (Copilot Chat in agent mode, plus any MCP-compatible extension). You can connect Kavio in a few clicks.

​
Prerequisites

  • VS Code 1.101 or later (earlier versions don’t support OAuth for remote MCP servers)
  • GitHub Copilot extension (or another MCP-compatible extension)
  • A Kavio account with an active trial or subscription (no card required to start)

​
Setup

1

Create the MCP configuration file

In your project root, create or edit .vscode/mcp.json:
No Authorization header — VS Code discovers OAuth from the URL.
2

Reload VS Code

Reload the window so VS Code picks up the new configuration.
3

Sign in through your browser

Open the Accounts menu (bottom-left gear) or the Copilot Chat panel — VS Code prompts you to sign in to Kavio. Approve in the browser and the server flips to Connected.
4

Verify the connection

Open Copilot Chat in agent mode and ask:
VS Code uses "servers" as the top-level key (not "mcpServers"). This is different from most other MCP clients.

​
Global configuration

To make Kavio available across all projects, open the command palette and run MCP: Open User Configuration to add the server to your user-level settings.
For sandboxed or remote workspaces where the OAuth callback can’t return to VS Code, set a Personal Access Token explicitly:
Create the key from Settings > API Keys on the Kavio dashboard.