@kyaulabs/deepseek-websearch
This MCP server gives AI agents real-time web search capabilities powered by DeepSeek's native search tool — no third-party search API (e.g., SerpAPI, Tavily) required.
Core capability: Perform web searches via a single web_search tool call, with DeepSeek handling the entire pipeline server-side — searching, fetching pages, and synthesizing a detailed, Markdown-formatted answer with cited source URLs.
Use cases:
Look up recent events, current data, or time-sensitive information beyond the model's training cutoff
Fact-checking and documentation/changelog lookups
Price checks, release schedules, and technical references
Additional features:
Model selection: Choose between
deepseek-v4-flash(fast, low-cost) ordeepseek-v4-pro(more powerful, for complex queries)Cancellable searches: Supports
AbortSignalfor in-flight cancellationStandalone use: Import the core
searchWeb()function directly into your own code without the MCP server layerConfiguration: Set API key, model, and other parameters via environment variables or a JSON config file
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@kyaulabs/deepseek-websearchWhat's the latest news about the James Webb Space Telescope?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@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 sourcesNo SerpAPI. No Tavily. No Brave Search key. DeepSeek does the searching itself.
Related MCP server: websearch-deepseek
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-xxxxxxxxxxxxxxxx3. 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 |
| Yes | — | DeepSeek API key |
| No | — | Fallback key variable name |
| No |
|
|
| No |
|
|
| No |
| Max response tokens |
| No |
| 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 |
| Fast | Low | Daily searches (default) |
| 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/sdkOfficial 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 emittingUsing 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, pageAgeAttribution
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-RPCTypeScript 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)
Available Tools
1 toolweb_searchA
Search the web for current, real-time, or factual information. Use when you need information beyond training data — recent events, current data, documentation lookups, or fact-checking. Returns a detailed AI-generated answer based on full page content, plus source URLs. Powered by DeepSeek's native web search.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The search query. Be specific and include relevant keywords. | |
| explanation | No | One sentence explaining why this search is needed. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It states the return type (AI-generated answer plus source URLs) and mentions it is powered by DeepSeek. However, it does not disclose potential latency, rate limits, or that searches may fail. It is adequate but not exhaustive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise with four sentences. It is front-loaded with purpose, followed by usage guidance, then return information. Every sentence adds value without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers purpose, usage, and return type. Given the tool's simplicity and full schema coverage, it is largely complete. However, it lacks details on possible response structure or error handling, but for a search tool this is acceptable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with both 'query' and 'explanation' parameters described in the schema. The tool description adds no additional parameter-level details beyond the schema's own descriptions. Baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches the web for current, real-time, or factual information. It lists specific use cases (recent events, current data, documentation lookups, fact-checking) and distinguishes itself from using training data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Use when you need information beyond training data' and provides clear scenarios for when to use, such as recent events, current data, documentation lookups, and fact-checking. It effectively guides the agent on appropriate use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.1- First observed
web_search
TDQS
Only one tool exists, so there is no possibility of confusion or overlapping purposes.
The single tool uses a clear snake_case verb_noun pattern ('web_search'), which is consistent and predictable.
One tool is slightly below the typical 3-15 range, but it is reasonably scoped for a focused web search server.
The tool covers the core search functionality thoroughly, returning both detailed AI-generated answers and source URLs, with no obvious gaps.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Enable AI assistants to perform web searches using Perplexity's Sonar Pro.
Real-time web search, reasoning, and research through Perplexity's API
Agent-native search engine with live web research optimized for AI agents.
The best web search for your AI Agent
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables real-time web search via DeepSeek's search-enhanced dialogue, providing search results as answers through MCP tools.1MIT
- AlicenseAqualityCmaintenanceA general MCP server providing web search capabilities using DeepSeek's native online search API.16128MIT
- FlicenseNot gradedqualityDmaintenanceEnables web search for large language models using Zhipu AI's Web Search API, supporting multiple search engines and advanced filtering options.-
- AlicenseNot gradedqualityCmaintenanceEnables web search via Azure OpenAI Responses API with the web_search_preview tool, returning results with citations.13MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kyaulabs/deepseek-websearch-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server