DuckDuckGo Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web-searchA | Search the web. Use mode="web" for standard DuckDuckGo results (titles, URLs, snippets). Use mode="ai" for AI-generated answers — pick backend="iask" (default) or backend="monica". |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The two modes are clearly described within the single tool.
With a single tool named 'web-search', the naming is self-consistent and follows a clear verb-noun pattern.
A search server with only one tool feels too thin for the domain. Typically, separate tools for different search types (web, images, news, etc.) would be expected.
The single tool covers web and AI search but misses common search categories like images, news, and video, leaving notable gaps for typical search use cases.