Cursor integration

Cursor supports MCP servers via its settings. Oka Reason works as a standard MCP server — no Cursor-specific adapter needed.

Setup

1. Open Cursor settings

Go to Cursor → Settings → MCP (or search “MCP” in the command palette).

2. Add Oka as an MCP server

Add a new server with:

Name: oka
Command: npx
Args: -y @oka-core/reason

Or edit ~/.cursor/mcp.json directly:

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

3. Authenticate

After restarting Cursor, use the login tool in AI chat:

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.

Usage in Cursor

Cursor’s AI will discover Oka’s tools automatically. You can prompt it:

“Use the context tool to check what we know about the auth module”
“Record a decision: we’re using pgvector instead of Pinecone”
“Search Oka for anything related to webhook reliability”

Cursor Rules integration

Add Oka instructions to your .cursorrules file (Cursor’s equivalent of CLAUDE.md):

## Oka Reason
- Before starting any task, call context() for the relevant area
- Record architectural decisions with the decision tool
- Record deviations from expected behavior with the deviation tool
- Call done() when completing tasks with outcome notes

Tips

Cursor may not always call MCP tools proactively. Be explicit in your prompts: “Use the Oka context tool to check…”
The OKA_WORKSPACE environment variable controls workspace scoping. Set it to your project name for precise context queries.