Oko

bartlomein14starsClaim this server

Better code search for coding agents: Claude Code, Codex, Cursor, OpenCode and Pi spend fewer tokens, tool calls and time.

Developer Tools

Add to Cursor Add to VS Code Run on PlugMCPClaim this server

GitHub

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "bartlomein-oko": {4      "command": "mcpb",5      "args": [6        "https://github.com/bartlomein/oko/releases/download/v0.9.1/oko-v0.9.1-macos.mcpb"7      ],8      "env": {9        "TYPESAFE_API_KEY": "<secret>"10      }11    }12  }13}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

mcpb https://github.com/bartlomein/oko/releases/download/v0.9.1/oko-v0.9.1-macos.mcpb

Credentials from the publisher

TYPESAFE_API_KEY — TypeSafe AI key for ranking with Jev.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1TYPESAFE_API_KEY=<secret> claude mcp add bartlomein-oko -- mcpb https://github.com/bartlomein/oko/releases/download/v0.9.1/oko-v0.9.1-macos.mcpb

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "bartlomein-oko": {4      "command": "mcpb",5      "args": [6        "https://github.com/bartlomein/oko/releases/download/v0.9.1/oko-v0.9.1-macos.mcpb"7      ],8      "env": {9        "TYPESAFE_API_KEY": "<secret>"10      }11    }12  }13}

claude_desktop_config.json

Local · mcpbPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
API key: TYPESAFE_API_KEY
Last checked: 2026-11-05

Stars: 14
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Oko?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Oko need an API key?

The publisher lists these environment variables: TYPESAFE_API_KEY.

What transport does Oko use?

Oko runs locally over stdio.

When was Oko last checked?

Last checked 2026-11-05. Better code search for coding agents: Claude Code, Codex, Cursor, OpenCode and Pi spend fewer tokens, tool calls and time.

From the publisher

Documentation

Quick start

brew install bartlomein/tap/oko
cd your-project
oko setup --client claude     # or codex, cursor, opencode, pi, all

Without Homebrew: curl -fsSL https://raw.githubusercontent.com/bartlomein/oko/main/install.sh | sh.

Then use your coding tool as usual. Setup asks for a TypeSafe AI key the first time, connects your tool to Oko for this project, and checks the connection. Run it once per project; oko upgrade keeps everything current (with Homebrew, run brew upgrade oko first).

The first time you open the project, Codex shows Hooks need review. Choose Trust all and continue. If you skipped it, /hooks brings it back.

Cursor adds a project's tools switched off. Open Customize > MCPs, click oko and turn it on.

Pi 1.0 or later. Trust the project when Pi asks, then check /mcp. Pi setup.

Start a new session after setup.

macOS (Apple Silicon and Intel) and Linux (ARM64 and x64, glibc 2.35+). The installer puts oko in ~/.local/bin; add it to your PATH if needed. Other install options · Connect a tool by hand · Keys and configuration. For search without a key, add --no-jev: local keyword ranking only.

Results

The same task given to the same coding tool twice, once with its own search and once with Oko, in the same run. Means per session.

Coding tool	Time	Tokens	Tool calls	Tasks passed (without → with)
Claude Code	47% less12.1 → 6.4 s	44% less24,271 → 13,627	89% less3.5 → 0.4	19 → 20 of 20
Codex	26% less13.8 → 10.2 s	43% less45,395 → 26,004	80% less3.0 → 0.6	20 → 20 of 20
OpenCode	47% less18.0 → 9.6 s	43% less13,196 → 7,528	87% less3.7 → 0.5	21 → 21 of 21
Pi	51% less16.7 → 8.2 s	33% less9,737 → 6,495	85% less3.6 → 0.5	20 → 21 of 21
Cursor	6% less52.3 → 49.2 s	40% less182,940 → 109,520	65% less8.0 → 2.8	26 → 24 of 27

Models: Claude Sonnet 5.5 (Claude Code), GPT-6.1 Sol (Codex, OpenCode, Pi), Grok 4.7 High (Cursor), at their default or low effort. Cursor's row is from its own run on the previous release; the others are from October 2026. Each tool counts tokens its own way, so compare within a row. Small benchmark; your results will vary. Method, per-task results and caveats · raw data.

Other benchmarks

Benchmark	What it tests	Oko	Best comparison
Sense's agent benchmark	Six multi-step tasks, Claude Opus 4.7, run against Sense the same evening	Found 88% of the locations to cite, at half the cost	Sense: 63%
Agent Retrieval Bench	345 tasks: find the files a developer needs next	Right file ranked first most often: 0.40, checked by the benchmark's maintainers	Best published method: 0.24
SWE-Explore	848 real issues: rank the code fixing agents needed	One search ranks it within the range of agents that explore for many turns: 0.82	Agents: 0.72–0.95

Where Oko helps less

Cursor's own search is already fast, so Oko saves less time there: mostly tokens and tool calls.
Duplicated code can mislead it. When two files hold identical copies of a function, Oko may show the wrong one first; one Astro edit task in our benchmark fails this way.
Big changes across many files: one search returns five places, so an issue touching many files still needs the agent's own exploring.

Use it from your terminal

oko ask "where is authentication handled?"
oko ask "how are retries handled?" --json
oko stats                     # what ranking has cost you

How it works

Oko searches your project locally (keywords, symbols and file structure), then asks Jev, TypeSafe AI's relevance model, which of the candidates actually answer the question, and returns those excerpts with exact line numbers. oko setup connects it to your tool as an MCP server, adds short guidance to the instructions your tool reads, and installs a hook that answers a code question as you send it. What setup changes · Privacy.

Documentation

I want to…	Guide
Install, upgrade or troubleshoot	Installation
Connect a tool by hand, or understand the MCP tool	Client setup · MCP reference
Configure keys, `.env` or caching	Configuration
Search from the terminal, or rank my own documents	Search · Document ranking
See every benchmark and how it was run	Benchmark results
Know what leaves my machine	Privacy

Contributing

Bug reports and ideas are welcome: open an issue with your OS and oko --version, without keys or private code. To build and test, see CONTRIBUTING.md.

License

MIT. Dependency attributions are in THIRD_PARTY_NOTICES.md.

Oko

bartlomein14starsClaim this server

Better code search for coding agents: Claude Code, Codex, Cursor, OpenCode and Pi spend fewer tokens, tool calls and time.

Developer Tools

Add to Cursor Add to VS Code Run on PlugMCPClaim this server

GitHub

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "bartlomein-oko": {4      "command": "mcpb",5      "args": [6        "https://github.com/bartlomein/oko/releases/download/v0.9.1/oko-v0.9.1-macos.mcpb"7      ],8      "env": {9        "TYPESAFE_API_KEY": "<secret>"10      }11    }12  }13}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

mcpb https://github.com/bartlomein/oko/releases/download/v0.9.1/oko-v0.9.1-macos.mcpb

Credentials from the publisher

TYPESAFE_API_KEY — TypeSafe AI key for ranking with Jev.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1TYPESAFE_API_KEY=<secret> claude mcp add bartlomein-oko -- mcpb https://github.com/bartlomein/oko/releases/download/v0.9.1/oko-v0.9.1-macos.mcpb

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "bartlomein-oko": {4      "command": "mcpb",5      "args": [6        "https://github.com/bartlomein/oko/releases/download/v0.9.1/oko-v0.9.1-macos.mcpb"7      ],8      "env": {9        "TYPESAFE_API_KEY": "<secret>"10      }11    }12  }13}

claude_desktop_config.json

Local · mcpbPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
API key: TYPESAFE_API_KEY
Last checked: 2026-11-05

Stars: 14
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Oko?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Oko need an API key?

The publisher lists these environment variables: TYPESAFE_API_KEY.

What transport does Oko use?

Oko runs locally over stdio.

When was Oko last checked?

Last checked 2026-11-05. Better code search for coding agents: Claude Code, Codex, Cursor, OpenCode and Pi spend fewer tokens, tool calls and time.

From the publisher

Documentation

Quick start

brew install bartlomein/tap/oko
cd your-project
oko setup --client claude     # or codex, cursor, opencode, pi, all

Without Homebrew: curl -fsSL https://raw.githubusercontent.com/bartlomein/oko/main/install.sh | sh.

The first time you open the project, Codex shows Hooks need review. Choose Trust all and continue. If you skipped it, /hooks brings it back.

Cursor adds a project's tools switched off. Open Customize > MCPs, click oko and turn it on.

Pi 1.0 or later. Trust the project when Pi asks, then check /mcp. Pi setup.

Start a new session after setup.

Results

The same task given to the same coding tool twice, once with its own search and once with Oko, in the same run. Means per session.

Coding tool	Time	Tokens	Tool calls	Tasks passed (without → with)
Claude Code	47% less12.1 → 6.4 s	44% less24,271 → 13,627	89% less3.5 → 0.4	19 → 20 of 20
Codex	26% less13.8 → 10.2 s	43% less45,395 → 26,004	80% less3.0 → 0.6	20 → 20 of 20
OpenCode	47% less18.0 → 9.6 s	43% less13,196 → 7,528	87% less3.7 → 0.5	21 → 21 of 21
Pi	51% less16.7 → 8.2 s	33% less9,737 → 6,495	85% less3.6 → 0.5	20 → 21 of 21
Cursor	6% less52.3 → 49.2 s	40% less182,940 → 109,520	65% less8.0 → 2.8	26 → 24 of 27

Other benchmarks

Benchmark	What it tests	Oko	Best comparison
Sense's agent benchmark	Six multi-step tasks, Claude Opus 4.7, run against Sense the same evening	Found 88% of the locations to cite, at half the cost	Sense: 63%
Agent Retrieval Bench	345 tasks: find the files a developer needs next	Right file ranked first most often: 0.40, checked by the benchmark's maintainers	Best published method: 0.24
SWE-Explore	848 real issues: rank the code fixing agents needed	One search ranks it within the range of agents that explore for many turns: 0.82	Agents: 0.72–0.95

Where Oko helps less

Cursor's own search is already fast, so Oko saves less time there: mostly tokens and tool calls.
Duplicated code can mislead it. When two files hold identical copies of a function, Oko may show the wrong one first; one Astro edit task in our benchmark fails this way.
Big changes across many files: one search returns five places, so an issue touching many files still needs the agent's own exploring.

Use it from your terminal

oko ask "where is authentication handled?"
oko ask "how are retries handled?" --json
oko stats                     # what ranking has cost you

How it works

Documentation

I want to…	Guide
Install, upgrade or troubleshoot	Installation
Connect a tool by hand, or understand the MCP tool	Client setup · MCP reference
Configure keys, `.env` or caching	Configuration
Search from the terminal, or rank my own documents	Search · Document ranking
See every benchmark and how it was run	Benchmark results
Know what leaves my machine	Privacy

Contributing

Bug reports and ideas are welcome: open an issue with your OS and oko --version, without keys or private code. To build and test, see CONTRIBUTING.md.

License

MIT. Dependency attributions are in THIRD_PARTY_NOTICES.md.