Continue.dev integration

Continue.dev supports MCP servers in Agent mode. Oka Reason works as a standard stdio MCP server.

Setup

1. Create the MCP config file

Create .continue/mcpServers/oka-reason.yaml in your project root:

name: Oka Reason
version: 0.0.1
schema: v1
mcpServers:
  - name: Oka Reason
    command: npx
    args:
      - "-y"
      - "@oka-core/reason"

Caution

Continue uses YAML, not JSON. The mcpServers field is an array (list of objects), not an object keyed by name.

2. Switch to Agent mode

MCP tools are only available in Agent mode, not in regular chat. Make sure you’re using Agent mode in Continue’s chat panel.

3. Authenticate

In 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.

CI/CD or headless?

Add OKA_API_KEY to the env section, or use Continue’s secrets syntax: OKA_API_KEY: ${{ secrets.OKA_API_KEY }}. See API key auth.

4. Verify the connection

In Agent mode, ask Continue to list its available tools. You should see Oka’s 19 tools (context, observe, decision, etc.).

Tips

• Set OKA_WORKSPACE in the env section to scope events to your project.
• Agent mode is required — MCP tools won’t appear in regular chat mode.
• Continue supports stdio, sse, and streamable-http transports, but @oka-core/reason uses stdio via npx, which works out of the box.