DuckDuckGo Search MCP Server
Provides tools to query DuckDuckGo's Instant Answer API for search results, summaries, and related topics.
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., "@DuckDuckGo Search MCP Serversearch for recent climate change articles"
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.
MCP DuckDuckGo Search
A Model Context Protocol (MCP) server querying DuckDuckGo Instant Answer API.
Installation
Installing via Smithery
To install DuckDuckGo Search for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @shaheen2013/duckduckgo-search-mcp-server --client claudeManual Installation
# Clone the repository
git clone https://github.com/shaheen2013/duckduckgo-search-mcp-server.git
cd duckduckgo-search-mcp-server
# Install dependencies
npm install
# Build the project
npm run buildDocker
You can test this MCP server using Docker. To do this first run:
docker build -t duckduckgo-search-mcp-server .
docker run -p 8080:8080 duckduckgo-search-mcp-serverYou can then test the server running within Docker via the inspector e.g.
pnpm run inspector http://localhost:8080Related MCP server: DuckDuckGo Search MCP Server
Usage
Running the Server
You can use the MCP Inspector to test the server:
npm run inspectorAccess the MCP Inspector and then test the tool e.g.

Development
Project Structure
src/index.ts- Main server implementation
Available Scripts
npm run build- Build the TypeScript codenpm run watch- Watch for changes and rebuildnpm run inspector- Run the MCP Inspector against the server
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Acknowledgments
Available Tools
1 toolduckduckgo_searchC
Search DuckDuckGo Instant Answer API for a query string
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states what the tool does, but omits critical traits like rate limits, error handling, authentication requirements, or result format. This is insufficient for safe invocation.
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 a single sentence, which is concise, but it may be too brief, omitting valuable context. Every word is used, but the structure is minimal and lacks standard elements like parameter clarification. It achieves conciseness at the expense of completeness.
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?
Given the tool's simplicity (one parameter, no output schema, no annotations), the description still fails to provide a complete picture. It does not explain what the search returns, how to interpret results, or any limitations. The agent lacks essential context to use the tool effectively.
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?
With 0% schema description coverage, the description must add meaning beyond the schema. It only mentions 'for a query string', which is generic. The single parameter 'query' lacks any explanation of format, constraints, or examples. The description does not compensate for the schema's lack of detail.
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's purpose: searching the DuckDuckGo Instant Answer API with a query string. The verb 'search' and resource 'DuckDuckGo Instant Answer API' are specific and unambiguous. With no sibling tools to distinguish, the description is sufficient.
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 provides no guidance on when to use this tool, scenarios where it is appropriate, or any conditions. There is no mention of alternatives or context, leaving the agent without direction.
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
v0.1.0- First observed
duckduckgo_search
TDQS
Only one tool exists, so there is no possibility of confusion between tools.
The single tool name follows a clear verb_noun pattern (search_duckduckgo), which is consistent and descriptive.
A single tool for a search server feels minimal but still functional for its stated purpose; it is at the lower end of acceptable scope.
The server only offers a single search operation (Instant Answer API), lacking common search features like web search, image search, or filtering, which are typical 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
DuckDuckGo: The DuckDuckGo Search API is a tool that allows developers and businesses to integrate.
LLM-ready web search + instant answers + URL-to-clean-text fetch for agents and RAG.
DuckDuckGo search as JSON. Ranked results, ads in their own array, 37 regions.
Search Stack Exchange questions, fetch Q&A threads as markdown, look up tag FAQs and user profiles.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables web search capabilities using DuckDuckGo's free API without requiring authentication or API keys.-
- AlicenseNot gradedqualityCmaintenanceEnables web search and content fetching via DuckDuckGo without requiring an API key.2073MIT
- FlicenseBqualityDmaintenanceEnables querying the DuckDuckGo Instant Answer API through the Model Context Protocol, allowing users to perform searches and retrieve instant answers.19-
- AlicenseNot gradedqualityDmaintenanceEnables web searching using Google search results with no API keys required.431MIT
Appeared in Searches
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/Muhammad-Sarfaraz/duckduckgo-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server