DuckDuckGo MCP Server
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web using DuckDuckGo. Returns a list of search results with titles, URLs, and descriptions. |
| image_searchA | Search for images using DuckDuckGo. Returns a list of image results with URLs, titles, and sources. |
| download_imageA | Download an image from a URL to the local machine. Returns the local file path. |
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
Each tool has a distinct purpose: web_search for web results, image_search for image results, and download_image for saving images locally. No overlap.
All tools follow the same verb_noun snake_case pattern: download_image, image_search, web_search.
Three tools are well-scoped for a search server covering web search, image search, and image downloading. Not too few or too many.
Core search and download functionality is covered. Minor gaps exist (e.g., no video or news search), but the surface is sufficient for basic DuckDuckGo tasks.