# @just-every/mcp-deep-search [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/just-every/mcp-deep-search  
**GitHub Stars:** 9  
**npm Downloads (last month):** 1430  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/just-every-mcp-deep-search

## Description
MCP server for deep web search using @just-every/search

## Tools
Capabilities this server exposes over MCP:

- **deep_search** — Perform web searches using a specific provider.
- **comprehensive_research** — Perform comprehensive research using AI agents that intelligently select and query multiple search engines.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-deep-search": {
    "command": "npx",
    "args": ["-y","@just-every/mcp-deep-search"],
    "env": {
      "ENV_FILE": "",
      "BRAVE_API_KEY": "",
      "ANTHROPIC_API_KEY": "",
      "OPENAI_API_KEY": "",
      "GOOGLE_API_KEY": "",
      "OPENROUTER_API_KEY": "",
      "XAI_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `ENV_FILE`, `BRAVE_API_KEY`, `ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, `GOOGLE_API_KEY`, `OPENROUTER_API_KEY`, `XAI_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What @just-every/mcp-deep-search does

@just-every/mcp-deep-search exposes web search and research capabilities through the Model Context Protocol. It uses `@just-every/search` to query multiple search providers, including Brave, Google, Bing, DuckDuckGo, Perplexity variants, Anthropic, OpenAI, and xAI-backed search options.

The server offers two MCP tools. `deep_search` performs a query against a selected provider and can return a configurable number of results, with an optional AI-generated answer when the provider supports one. `comprehensive_research` delegates provider selection and multi-engine querying to AI agents for a broader research workflow.

## How it works

The server runs as an MCP process launched with `npx -y @just-every/mcp-deep-search`. MCP clients pass requests to the available tools, while provider credentials are loaded through the `ENV_FILE` environment variable. The environment file must be supplied using an absolute path, such as `/Users/name/.llm.env` or `/home/name/project/.env`.

Provider selection is explicit for `deep_search`; Brave is the default. The tool accepts a query, a result limit, and an `includeAnswer` option. `comprehensive_research` accepts a research topic and an optional model class, defaulting to `reasoning_mini`.

A command-line interface is also available for direct searches. It supports a query, a provider selection, and a result-count option.

## Setup and configuration

Create an environment file from the project’s example or use an existing `.env` file. Configure credentials for the providers you plan to use:

- `BRAVE_API_KEY` for Brave
- `ANTHROPIC_API_KEY` for Anthropic
- `OPENAI_API_KEY` for OpenAI
- `GOOGLE_API_KEY` for Google
- `OPENROUTER_API_KEY` for the `sonar` and `sonar-pro` providers
- `XAI_API_KEY` for xAI

A generic MCP configuration uses `npx` as the command and passes `ENV_FILE` under the client’s environment settings. Claude Code can add the server with `claude mcp add`, using `-e ENV_FILE=/absolute/path/to/.env` before the command separator.

## Tools and capabilities

- `deep_search`: searches a chosen provider with `query`, `provider`, `maxResults`, and `includeAnswer` parameters.
- `comprehensive_research`: runs AI-directed research across multiple search engines with `query` and `modelClass` parameters.
- Provider options include Brave, Anthropic, OpenAI, Google, `sonar`, `sonar-pro`, and xAI.
- CLI searches can specify a provider with `-p` and a result count with `-n`.
- The server includes automatic restart handling for crashes, unhandled exceptions, and rejected promises, with exponential backoff and a maximum of 10 attempts within one minute.

## Limitations and notes

Each provider requires its corresponding credential, so available searches depend on the API keys configured in the environment file. `ENV_FILE` should use an absolute path; relative paths and unexpanded home-directory shortcuts can prevent the server from loading configuration in some client contexts.

For troubleshooting, run a search manually with `ENV_FILE=/absolute/path/to/.env npx @just-every/mcp-deep-search search "test"`. The development command `npm run serve:dev` runs without the automatic restart wrapper, which can help expose startup or configuration errors.

_Full upstream README: https://allmcps.com/mcp/just-every-mcp-deep-search/readme_