mcp-deepseek-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPSEEK_API_KEY | Yes | Your DeepSeek API key, obtained from platform.deepseek.com (e.g. sk-your-key-here) |
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 |
|---|---|
| deepseek_searchA | Web search powered by DeepSeek's search engine. Returns ranked results with two quality signals: rerank_score (0-3; >=1.5 means highly relevant) and authority (0-4; >=3 means highly authoritative source, -1 unknown). Query syntax: site: (limit to site), -site: (exclude site), -term (exclude word), "exact phrase", -"phrase" (exclude phrase), lang:zh,en (limit languages), after:YYYY or after:YYYY-MM-DD, before:YYYY-MM-DD. By default returns summaries only; set need_content=true to include full page text (larger response). |
| deepseek_fetchA | Fetch a single web page and return its main content converted to Markdown (truncated at 30000 chars). Use after deepseek_search to read a specific result URL in full. Plain http/https URLs only; result availability depends on the target site's access policy. |
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
The two tools have clearly distinct roles: deepseek_search performs ranked web search, while deepseek_fetch retrieves and converts a single page to Markdown. The description even states fetch should be used after search, eliminating ambiguity.
Both tools follow a consistent deepseek_<verb> pattern (search, fetch). The naming is predictable and easy to reason about.
Two tools is slightly below the typical 3-15 range, but the server has a narrow search-and-fetch purpose where each tool earns its place. No unnecessary tools are included.
The surface covers the full search/read workflow: query with advanced syntax and optional content, then fetch full page content for a specific URL. There are no obvious dead ends for a web search server.