DeepSeek Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | HTTP mode only | 127.0.0.1 |
| MCP_PORT | No | HTTP mode only | 3000 |
| MCP_AUTH_TOKEN | No | HTTP mode; unset = no auth, localhost only | |
| DEEPSEEK_API_KEY | Yes | Required for tool calls. Get a key at https://platform.deepseek.com/api_keys | |
| DEEPSEEK_BASE_URL | No | For testing against a mock | https://api.deepseek.com |
| MAX_CONTENT_CHARS | No | fetch truncation limit | 40000 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the web and return ranked results (title, url, snippet, summary, date, authority). Supports site:, -site:, lang:, after:, before: and quoted exact phrases in |
| fetchA | Fetch one web page and return its title plus Markdown body. Use after |
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 2 tools
Search and fetch target clearly different operations: search returns ranked results, while fetch retrieves a single page's full content. The descriptions reinforce the intended use sequence (search then fetch), leaving no meaningful ambiguity.
Both tool names are simple lowercase verbs (search, fetch), following a consistent single-verb convention. There is no mixing of styles or noun phrasing.
Two tools is slightly below the typical 3–15 range, but each is well-scoped and earns its place for a focused web search and retrieval server. The surface is minimal yet sufficient for the core workflow.
The server is read-only, and its domain lifecycle is search then fetch; both operations are present with useful filtering parameters. No obvious gaps exist for basic web search and page retrieval.