Set up Kabuken in GitHub Copilot and VS Code
What you need
Section titled “What you need”- A Kabuken account. Sign in or sign up.
- VS Code with GitHub Copilot chat. VS Code stores MCP servers in
mcp.json. - Sign-in method: OAuth is the default choice. The API key setup below uses an input prompt, which the GitHub Copilot coding agent (runs without a VS Code window) cannot use, so use OAuth there.
Sign in with OAuth
Section titled “Sign in with OAuth”- Open the Command Palette (
Ctrl+Shift+P, orCmd+Shift+Pon macOS) and run MCP: Add Server. - Choose HTTP (HTTP or Server-Sent Events).
- Enter the address
https://kabuken.intellics.ai/mcpand a name such askabuken. - Choose where to save it: your user profile, or the workspace (
.vscode/mcp.json). - VS Code starts the server and reports that sign-in is needed. Follow the prompt: a browser opens, sign in to Kabuken, then select Authorize. If no prompt appears, run MCP: List Servers, select kabuken, then Start Server.
The result in mcp.json:
{ "servers": { "kabuken": { "type": "http", "url": "https://kabuken.intellics.ai/mcp" } }}Use an API key
Section titled “Use an API key”Create a kbk_ key on the Account page: in the API Access section, select Generate Key. This configuration makes VS Code ask for the key once and store it, so the key is not written into the file:
{ "inputs": [ { "type": "promptString", "id": "kabuken-api-key", "description": "Kabuken API key", "password": true } ], "servers": { "kabuken": { "type": "http", "url": "https://kabuken.intellics.ai/mcp", "headers": { "Authorization": "Bearer ${input:kabuken-api-key}" } } }}First prompt
Section titled “First prompt”Open Copilot chat in agent mode, check that the Kabuken tools are enabled in the tools list, and ask:
What is Sony’s latest annual securities report?
Troubleshooting
Section titled “Troubleshooting”See Troubleshooting and Authentication.
Checked: 2026-10-29 against https://code.visualstudio.com/docs/copilot/reference/mcp-configuration