DeepSeek Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPSEEK_API_KEY | Yes | DeepSeek 开放平台 API 密钥（以 sk- 开头）。 | |
| DEEPSEEK_BASE_URL | No | 自定义 API 网关地址（用于企业私有代理或内网转发）。 | https://api.deepseek.com |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deepseek_searchA | Search the web using DeepSeek's official search engine. Returns real-time, high-quality search results with relevance scores (rerank_score) and dense summaries tailored for LLMs. Supports advanced syntax such as 'site:', '-site:', and quotes. |
| deepseek_fetchB | Fetch and extract the readable Markdown text of a specific webpage using DeepSeek's official crawler. Ideal for deep-dive reading on search results or analyzing documentation from a specific URL. |
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
deepseek_search and deepseek_fetch have clearly distinct purposes: one queries the search engine, the other retrieves and converts a specific URL to Markdown. An agent can trivially tell which to call based on whether it has a query or a known URL.
Both tools use the same deepseek_ prefix followed by a concise action verb (search, fetch). The pattern is predictable and readable, with no mixing of conventions.
Two tools is on the lean side, but for a web-retrieval server this is exactly the minimal complete pair (find then read). Nothing feels missing or padded, though a multi-URL or batch fetch would be a natural addition.
Search plus fetch covers the full retrieval lifecycle: discovering sources and then reading them in depth. There are no obvious dead ends for the stated purpose of web search and content extraction.