LABSCO SUMMARY
The prompt hook is the product; the search is the delivery.
Plenty of servers give a coding assistant web search. What this one adds is that the search is not blind — the hook has already sent what you have open and what just failed, so a query about a library error can come back with the page that matches your version rather than the top result. That also means it sends session context out on every prompt by design, which is worth knowing before you install it on a private codebase.
What it is
An MCP server and prompt hook for Claude Code and Codex CLI. The search side lets the assistant pull current documentation and web results instead of relying on training data. The hint side is what makes it different: a prompt hook sends lightweight session context — files, errors, recent messages — on each prompt, so the results come back scoped to what you are actually stuck on.
What you get
- Web and documentation search the assistant can call mid-task, so answers reflect current docs rather than a training cutoff
- Contextual hints derived from your open session — the files, the errors, the recent messages — instead of generic advice for the topic
- Automatic context sync on every prompt through the installed hook, with no per-task setup
- An installer that writes the client config for you, in interactive or non-interactive form, targeting
--client claudeor--client codex, with--dry-runto preview the changes and automatic backups before anything is edited
Requirements
An API key from tomsindex.com/dashboard, in the form srch_.... Install with npx tomsindex — the npm package is tomsindex (0.3.0 in package.json) and ships a tomsindex binary. npx tomsindex doctor checks an existing setup, and npx tomsindex uninstall removes it from your tools. To confirm tool calls are landing in Codex, set TOMSINDEX_MCP_LOG to a file path and read it back.
Setup effort
One command plus a key — npx tomsindex, then supply credentials
USE CASES
01
Getting current docs into an assistant that has a training cutoff
Let it search the web and pull the live documentation page for the library version you are on, rather than reciting an older API.
02
Getting advice about the error in front of you
Ask for a hint while the failing file and the error output are in session, so the guidance is about your case rather than the general topic.
03
Wiring it into a second machine
Run the non-interactive install with your key and the client you use, and preview the config changes first if the machine is shared.
04
Working out why tool calls are not appearing
Run the doctor command, and in Codex set the log path and read the file to see whether the calls are being made at all.
BEFORE YOU INSTALL
What to know first
Requires
npx on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
npx tomsindexMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
npx tomsindex install --client claudeCodex
CODEX · TERMINAL
npx tomsindex install --client codex