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. If unset on macOS, the server reads it from the Keychain service `deepseek-api-key`. | |
| DEEPSEEK_DAILY_LIMIT | No | Daily billable-call limit (default 500). | 500 |
| DEEPSEEK_MONTHLY_LIMIT | No | Monthly billable-call limit (default 5000). | 5000 |
| DEEPSEEK_SEARCH_STATE_DIR | No | Directory where usage-count state is stored. | ~/.local/state/deepseek-search-mcp |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deepseek_searchA | Search the web with DeepSeek's own search engine. 用 DeepSeek 自研搜索引擎搜索网页。按次计费(每次 0.005 元,与 count 无关)。 |
| deepseek_fetchA | Fetch one web page as Markdown via DeepSeek. 用 DeepSeek 抓取单个网页,返回 Markdown 正文。按次计费(每次 0.005 元),同一网址 15 分钟内翻页不重复计费。 |
| deepseek_usageA | 查看本机 DeepSeek 搜索/抓取的计费调用次数、估算花费和防误扣上限。 |
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 3 tools
The three tools cover clearly distinct purposes: cost/quota inspection (deepseek_usage), web search (deepseek_search), and single-page retrieval (deepseek_fetch). An agent can unambiguously select the right tool for each task.
All tools share the deepseek_ prefix, giving a predictable namespace. The suffixes mix verbs (search, fetch) with a noun (usage), a minor deviation, but overall it reads consistently.
Three tools is well-scoped for a search/retrieval server, and each earns its place: one to search, one to fetch, one to monitor billing. No redundant or filler tools.
The surface fully covers the search lifecycle: discovery via search, content retrieval via fetch with pagination hints, and cost control via usage. No obvious gaps for the stated purpose.