DeepSeek Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPSEEK_API_KEY | Yes | Your DeepSeek API Key, created in the DeepSeek console (https://platform.deepseek.com/api_keys). It should only be injected via environment variables or client configuration. |
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_web_searchA | 使用 DeepSeek 自研搜索引擎搜索网页，返回结构化结果（标题、URL、日期、相关度、摘要）。查询支持语法：site: 限定站点、-关键词 排除、"精确短语"、lang: 语言、after:/before: 日期。计费：每 1000 次成功请求 5 元，失败不计费。 |
| deepseek_fetchA | 用 DeepSeek Fetch 抓取单个网页，以 Markdown 正文返回。适合读取某条搜索结果或指定文章的全文。 |
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 purposes: one searches the web and returns result lists, the other retrieves the full Markdown body of a single URL. There is no plausible scenario where an agent confuses discovery with retrieval, and the descriptions reinforce the boundary.
Both names use the same deepseek_ prefix and snake_case convention, which is consistent and readable. The minor asymmetry is that one is qualified (web_search) while the other is bare (fetch), but the action verbs remain clear and predictable.
Two tools is thin, sitting at the borderline of the 1-2 tool range that risks feeling under-built. However, for a search-and-retrieve service these are the two essential operations and neither is redundant, so it is defensible rather than deficient.
The search-plus-fetch pairing covers the standard research lifecycle end to end: find candidate pages, then read the full text of one. Nice-to-haves like batch fetching or paginated result continuation are absent, but agents can work around that with repeated calls.