VS Code Copilot integration

VS Code’s GitHub Copilot agent mode supports MCP servers, giving Copilot access to Oka’s 19 tools.

Setup

1. Create `.vscode/mcp.json`

Add this file to your project root:

{
  "servers": {
    "oka": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@oka-core/reason"]
    }
  }
}

2. Authenticate

In Copilot Chat’s Agent mode, use the login tool:

Use the login tool to authenticate with Oka

This opens your browser to id.oka.so where you sign in or create an account. Your credentials are stored locally and refresh automatically.

Set OKA_API_KEY in the env block, or use VS Code’s input prompts:

{
  "servers": {
    "oka": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@oka-core/reason"],
      "env": {
        "OKA_API_KEY": "${input:oka-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "oka-api-key",
      "description": "Oka API Key",
      "password": true
    }
  ]
}

See API key auth.

3. Verify the connection

Open the Command Palette (Cmd+Shift+P) and run MCP: List Servers. You should see oka with a running status and 19 tools listed.

Usage in Copilot

In Copilot Chat’s Agent mode (@workspace), Copilot automatically discovers and can call Oka’s tools. Prompt it directly:

“Check Oka context for the auth module before we start”
“Record a decision: we’re using streaming responses for the API”
“Search Oka for anything related to database migrations”

Global configuration

For user-wide setup (all projects), open the Command Palette and run MCP: Open User Configuration. The format is the same.

Tips

The "type": "stdio" field is required — VS Code won’t start the server without it.
VS Code supports ${workspaceFolder} and other predefined variables in the config.
Set OKA_WORKSPACE in the env block to scope events to your project.
VS Code IntelliSense works inside .vscode/mcp.json — use it.