DeepSeek × Exa Search Combine MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXA_API_KEY | No | Exa API key (https://dashboard.exa.ai/api-keys). One of EXA_API_KEY or DEEPSEEK_API_KEY must be set; the server refuses to start with neither. | |
| EXA_BASE_URL | No | Override for proxies/gateways. | https://api.exa.ai |
| MERGE_DEDUPE | No | Set to `false` to disable cross-provider URL merging. | true |
| DEEPSEEK_API_KEY | No | DeepSeek API key (https://platform.deepseek.com/api_keys). One of EXA_API_KEY or DEEPSEEK_API_KEY must be set; the server refuses to start with neither. | |
| DEEPSEEK_BASE_URL | No | Override for proxies/gateways. | https://api.deepseek.com |
| FETCH_PROVIDER_ORDER | No | Fallback order for `fetch`. | exa,deepseek |
| SEARCH_HTTP_TIMEOUT_MS | No | Per-request deadline in milliseconds. | 60000 |
| DEFAULT_SEARCH_PROVIDER | No | Provider used when a tool call omits `provider`: `both` | `exa` | `deepseek`. | both |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the web through DeepSeek and Exa at once and get back a single deduplicated list. By default every configured provider is queried in parallel and pages found by both are merged into one entry (labelled with all sources). Pass provider="exa" or "deepseek" to use just one. If only one API key is configured, the default automatically narrows to that provider. |
| fetchA | Fetch full page content for one or more URLs. Providers are tried in the configured fallback order (Exa first by default, then DeepSeek) and the first one that returns real content wins per URL. Pass provider="exa" or "deepseek" to pin a single backend. |
| statusA | Report which backends this server can reach, the default search behaviour and the fetch fallback order. Makes no network calls and costs nothing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: search performs multi-provider web search, fetch retrieves page content for URLs, and status reports backend availability without network calls. There is no meaningful overlap that would cause misselection.
The names are short, lowercase, and consistently action-oriented or state-oriented: search, fetch, status. The pattern is predictable and easy for an agent to map to intent.
Three tools are well scoped for a focused search-and-fetch server. Each tool earns its place, and there are no redundant or filler tools.
The core lifecycle is covered: search the web, fetch full content, and inspect backend status. Minor gaps exist around provider configuration or richer result management, but the essential surface is complete for the stated purpose.