DuckDuckGo MCP Server

Created By
rsimda year ago
DuckDuckGo MCP Server for Claude Desktop and Cursor
Overview

What is DuckDuckGo MCP Server?

DuckDuckGo MCP Server is a Model Context Protocol (MCP) server that provides search functionality using DuckDuckGo for applications like Claude Desktop and Cursor IDE.

How to use DuckDuckGo MCP Server?

To use the DuckDuckGo MCP Server, install the required dependencies and run the server using either the uv package manager or pip. You can then execute searches using the provided command.

Key features of DuckDuckGo MCP Server?

  • Web page search functionality via DuckDuckGo
  • Retrieval of search results with summaries and detailed information
  • Asynchronous processing for fast search results
  • Fallback functionality for enhanced stability

Use cases of DuckDuckGo MCP Server?

  1. Integrating DuckDuckGo search capabilities into desktop applications.
  2. Enhancing coding environments with AI-assisted search features.
  3. Providing a reliable search service for various MCP-compatible applications.

FAQ from DuckDuckGo MCP Server?

  • Is the DuckDuckGo MCP Server free to use?

Yes! The DuckDuckGo API is free to use.

  • What are the prerequisites for running the server?

You need Python 3.11 or later and the uv package manager or pip for installation.

  • Can I run the server in a Docker environment?

Yes! The server can be run in a Docker environment supporting both Python 3.13 and the required package managers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rsimd
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago