Name: Deep Search MCP
Author: just-every

LABSCO SUMMARY

One call for the fact you are missing, another for the write-up you were dreading.

The two tools are deliberately different jobs: deep_search answers a question that outran the model's knowledge cutoff, while comprehensive_research goes away and assembles an investigation across sources. Choosing between them is the whole interface, and modelClass is the dial on the expensive one.

What it is

A two-tool search server: a direct multi-provider web search, and an agent-driven research pass over a topic

What you get

Real-time web search across multiple providers with the provider selectable per call, a result cap, and an optional direct answer alongside the results (deep_search).
An agent pass that searches multiple sources, analyses what it finds and compiles a report, with modelClass choosing how much model to spend on it (comprehensive_research).

Requirements

ENV_FILE — the path to the environment file the server loads its configuration from.

Setup effort

One command plus a key — claude mcp add deep-search -s user -e ENV_FILE=$HOME/.llm.env -- npx -y @just-every/mcp-deep-search, then supply credentials

See installation options

USE CASES

01

Answering a question that outran the model's knowledge

A single search call reaches live results across providers, with the provider and the number of results under your control and an answer returned alongside them when you want one.

deep_search

02

Handing off a technology or market scan you do not want to assemble yourself

Agents search several sources, weigh what they find and return a written report, with modelClass deciding how much model goes into the pass.

comprehensive_research

2 tools

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`comprehensive_research`

Perform in-depth research on complex topics using AI agents that automatically search multiple sources, analyze findings, and compile comprehensive reports. Ideal for thorough investigations, market research, technical analysis, or any topic requiring deep understanding from multiple perspectives.

BEFORE YOU INSTALL

What to know first

Tools you get

2 tools when we connected. Each search provider needs its own key; deep_search defaults to Brave, so without BRAVE_API_KEY the default call fails. Keys are read from the file ENV_FILE points to, which must be an absolute path.

Requires

npx on PATH
BRAVE_API_KEY in your environment

Optional

ANTHROPIC_API_KEY in your environment
OPENAI_API_KEY in your environment
GOOGLE_API_KEY in your environment
OPENROUTER_API_KEY in your environment
XAI_API_KEY in your environment

Where it runs

Both documented clients run the server on your machine.

CONTEXT COST

Light Standing cost

Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are

INSTALLATION

Connect your client

Server setup

Claude Code

TERMINAL

claude mcp add deep-search -s user -e ENV_FILE=$HOME/.llm.env -- npx -y @just-every/mcp-deep-search

MCP Clients

Any MCP client

ANY MCP CLIENT · JSON

{
  "mcpServers": {
    "deep-search": {
      "command": "npx",
      "args": [
        "-y",
        "@just-every/mcp-deep-search"
      ],
      "env": {
        "ENV_FILE": "<YOUR_ENV_FILE>"
      }
    }
  }
}

The configuration on this page does not set BRAVE_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, OPENROUTER_API_KEY and XAI_API_KEY; the project's instructions put them in a .env file. To supply them without depending on where the server looks for that file, use the block's "env" section.

Deep Search MCP