DeepSeek Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPSEEK_API_KEY | Yes | 必填，DeepSeek 开放平台 API Key | |
| DEEPSEEK_ENABLE_WEB_FETCH | No | 设为 "true" 时启用 deepseek_web_fetch，默认关闭 | false |
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_searchC | Search the web for a query and return a ranked list of structured results. |
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 1 tool
With a single tool there is no possibility of misselection or overlap; its purpose is unambiguous. The name and description align cleanly, leaving nothing to confuse.
The lone tool uses a clear snake_case verb_noun style (deepseek_search) that matches its server identity. No mixed conventions exist since there is only one name.
A one-tool surface is borderline thin even for a search server; typical search MCPs expose pagination, filtering, or multiple content types. It works but leaves little room for user control.
Core web search is covered, but there are no options for result count, pagination, freshness, or filtering, which are common expectations. The surface is functional yet notably shallow for a search domain.