Skip to main content
Make Keenable the only web search your agent has, and in most clients the only page fetch too, so every lookup goes through the Keenable MCP server. Claude Code, Codex, Cursor and OpenCode each ship their own web tools. If both sets are on, the agent picks between them from one call to the next. Set this up after you add the MCP server to your client. Then turn off the client’s own tools, and add a routing rule that names the Keenable tools.

What changes in each client

The Keenable CLI turns off the built-in tools in Claude Code and OpenCode for you. In Codex and Cursor, you change one setting yourself.

Turn off the built-in tools with the CLI

This command adds Keenable to Claude Code and OpenCode and turns off their built-in web tools. --yes skips the confirmation prompt:
For Claude Code, the CLI adds WebSearch and WebFetch to permissions.deny in ~/.claude/settings.json. It also removes them from the allow lists in the .claude/settings.local.json files it finds in ~/dev, ~/projects, ~/src, ~/repos, ~/work and ~/code, up to three folders deep, and in your home directory. For OpenCode, it sets permission.websearch to "deny". To include every client the CLI detects, use --all instead of the client flags. See MCP setup in the CLI for the file each client flag edits.

Turn off the built-in tools by hand

Pick your client:
Add both tools to the deny list in ~/.claude/settings.json. If the file already has a permissions block, add the two names to its deny list instead of adding a second block:
~/.claude/settings.json
To turn them off for one session without editing the file, start Claude Code like this:
See Claude for more on the Claude apps.

Add a routing rule

A routing rule names the Keenable tools in your agent’s instructions. It helps when an agent loads tool details only once it decides a tool is relevant, as Codex does, and when you keep the built-in tools on. Put the rule in CLAUDE.md for Claude Code, or in AGENTS.md for Codex and Cursor, at the root of your repository:
AGENTS.md
If you use the OpenCode plugin instead of the MCP server, its tools are keenable_search and keenable_fetch. Name those in the rule.

Check the setup

Run keenable configure-mcp with no flags. It lists each detected client and flags any problem, such as Standard tools (WebSearch, WebFetch) not disabled:
In Claude Code, this command prints the deny list from your settings:
You see "WebSearch" and "WebFetch" in the list. Then start a new chat and ask a question that needs the web. The agent calls search_web_pages without being told to.

Undo the change

keenable reset removes the Keenable MCP entry and turns the built-in tools back on. In Claude Code, it removes only the deny entries that configure-mcp added, so entries you wrote yourself stay. If an older CLI made the change, reset can’t tell which entries it added and removes both WebSearch and WebFetch:
To turn the built-in tools back on and keep Keenable, undo the setting by hand instead: