duckduckgo-search

This MCP server exposes a DuckDuckGo Instant Answer API integration as a Model Context Protocol (MCP) service. It queries DuckDuckGo's Instant Answer API to fetch concise information and present it in a structured format suitable for use by clients that support MCP. You can test and interact with the server using the MCP Inspector tool included in the project. Once the server is running, you can send requests through the MCP Inspector to evaluate how the DuckDuckGo data is retrieved and wired into your model-context workflow. The server is designed to be run in a Node.js environment and is compatible with Docker for easy deployment.

Prerequisites:

• Node.js and npm installed on your system
• Git installed
• Docker (optional, for container testing)

Install via Smithery (automatic):

npx -y @smithery/cli install @shaheen2013/duckduckgo-search-mcp-server --client claude

Manual 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 build

Docker (build and run locally):

docker build -t duckduckgo-search-mcp-server .
docker run -p 8080:8080 duckduckgo-search-mcp-server

Test using the MCP Inspector (optional):

pnpm run inspector http://localhost:8080

Notes:

• The server builds to a dist/index.js entrypoint which is referenced in the MCP config as the Node command with dist/index.js.
• Default port is 8080; adjust PORT in the mcp_config if you choose a different port.
• The MCP Inspector can be used to validate requests and responses against the DuckDuckGo Instant Answer data.
• The npm package name to reference this server (for Smithery) is likely "@shaheen2013/duckduckgo-search-mcp-server"; use the corresponding package name when installing via Smithery or npm.
• If you deploy via Docker, you can map ports as needed (e.g., -p 8080:8080) to expose the MCP endpoint.