@kyaulabs/deepseek-websearch
Enables real-time web search via DeepSeek's server-side tool without requiring additional search API keys.
README
@kyaulabs/deepseek-websearch
An OpenCode-native MCP server that gives your agents real-time web search via DeepSeek's server-side web_search_20250305 tool. One tool call handles search, page fetch, decryption, and answer synthesis — no third-party search API required.
Based on lyumeng/websearch-deepseek (MIT). See Attribution.
How It Works
DeepSeek's Anthropic-compatible endpoint implements a built-in web_search_20250305 tool type. When your OpenCode agent calls the web_search tool, this MCP server forwards the query to DeepSeek, which performs the entire search pipeline server-side:
Agent calls web_search("latest Rust version")
│
▼
MCP Server ──POST──▶ api.deepseek.com/anthropic/v1/messages
tools: [{ type: "web_search_20250305" }]
│
▼ (all server-side)
1. Search the web
2. Fetch relevant pages
3. Decrypt page content
4. Synthesize a detailed answer
│
▼
MCP Server ◀──response── { text answer + source URLs }
│
▼
Agent receives Markdown answer with cited sources
No SerpAPI. No Tavily. No Brave Search key. DeepSeek does the searching itself.
Quick Start
1. Get a DeepSeek API Key
Sign up at platform.deepseek.com and create an API key.
2. Add to Your OpenCode Config
Add the server to your project's opencode.json (or ~/.config/opencode/opencode.json for global):
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"deepseek-websearch": {
"type": "local",
"command": ["npx", "@kyaulabs/deepseek-websearch"],
"enabled": true,
"environment": {
"DEEPSEEK_API_KEY": "{env:DEEPSEEK_API_KEY}"
}
}
}
}
The {env:DEEPSEEK_API_KEY} syntax reads from your environment — set it in .envrc (direnv) or your shell profile:
export DEEPSEEK_API_KEY=sk-xxxxxxxxxxxxxxxx
3. Ask Your Agent
Restart OpenCode. Your agent now has a web_search tool available. Ask anything that needs current information:
- "What's new in React 19?"
- "Search for the latest Node.js LTS release schedule"
- "Find the current DeepSeek API pricing"
The agent will automatically invoke web_search when it needs real-time data beyond its training cutoff.
Configuration
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
DEEPSEEK_API_KEY |
Yes | — | DeepSeek API key |
WEBSEARCH_API_KEY |
No | — | Fallback key variable name |
WEBSEARCH_MODEL |
No | deepseek-v4-flash |
deepseek-v4-flash (fast) or deepseek-v4-pro (powerful) |
WEBSEARCH_THINKING |
No | enabled |
enabled or disabled |
WEBSEARCH_MAX_TOKENS |
No | 32768 |
Max response tokens |
WEBSEARCH_BASE_URL |
No | https://api.deepseek.com/anthropic |
API base URL (for proxies) |
JSON Config File
Prefer a config file over env vars? Create ~/.deepseek-websearch.json:
{
"apiKey": "sk-xxxxxxxxxxxxxxxx",
"model": "deepseek-v4-pro",
"thinking": "disabled",
"maxTokens": 16384
}
Resolution order (each layer overrides the previous): defaults → JSON file → environment variables.
Model Selection
| Model | Speed | Cost | Use When |
|---|---|---|---|
deepseek-v4-flash |
Fast | Low | Daily searches (default) |
deepseek-v4-pro |
Slower | Higher | Deep research, complex queries |
Cost
Each search consumes ~8,000–15,000 DeepSeek API tokens (search + thinking + answer generation). Check DeepSeek pricing for current rates.
Features
- Zero runtime dependencies beyond the official
@modelcontextprotocol/sdk - Official MCP SDK — proper capability negotiation, error envelopes, no hand-rolled JSON-RPC
- TypeScript strict mode with 90%+ test coverage (Vitest)
- Structured errors — rate-limit detection (429), network errors, API errors, cancellation
- Configurable — env vars, JSON config file, or per-call programmatic overrides
- AbortSignal support — searches are cancellable
- Clean module separation — import
searchWeb()directly from your own code if you don't need the MCP layer
Development
npm install # install dependencies
npm test # run unit test suite (56 tests)
npm run test:integration # run live API tests (requires DEEPSEEK_API_KEY)
npm run build # compile TypeScript → dist/
npm run check # type-check without emitting
Using the Core Library Directly
The search logic is framework-agnostic. You can import it without the MCP server:
import { searchWeb } from "@kyaulabs/deepseek-websearch/search";
const result = await searchWeb("latest TypeScript features");
console.log(result.textAnswer); // AI-generated answer
console.log(result.results); // SearchResult[] with title, url, pageAge
Attribution
This project is based on lyumeng/websearch-deepseek by @lyumeng, originally released under the MIT License.
The original project established the approach of using DeepSeek's Anthropic-compatible endpoint with the web_search_20250305 tool type for server-side web search via MCP. This version is an independent engineering rewrite with the following improvements:
- Official
@modelcontextprotocol/sdkreplaces hand-rolled JSON-RPC - TypeScript strict mode with comprehensive Vitest test suite (90%+ coverage)
- Structured error handling with actionable codes (rate-limit detection, invalid config)
- Env vars + optional JSON config file with merge cascade
- Bug fix: system prompt placed as top-level
systemparameter (correct Anthropic Messages API format)
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。