MCP DuckDuckResearch

Created By
bkataru-workshopa year ago
mcp server with duckducksearch, web2md, and web2photo
Overview

what is MCP DuckDuckResearch?

MCP DuckDuckResearch is an MCP (Model Context Protocol) server that integrates DuckDuckGo search capabilities with web page content extraction and screenshot functionality, allowing users to programmatically access and manipulate web content.

how to use MCP DuckDuckResearch?

To use MCP DuckDuckResearch, clone the repository, install the dependencies, and configure the MCP server in your application settings. You can then utilize various tools to search the web, extract content, and take screenshots.

key features of MCP DuckDuckResearch?

  • 🔍 DuckDuckGo Search: Perform web searches using DuckDuckGo.
  • 📄 Content Extraction: Extract web page content as Markdown.
  • 📸 Screenshot Capture: Capture optimized screenshots of web pages.
  • Robust Error Handling: Built-in error handling for bot detection and content validation.
  • 🔒 Safe Search Options: Configurable safe search levels for content filtering.

use cases of MCP DuckDuckResearch?

  1. Automating web searches and content extraction for research.
  2. Generating Markdown documentation from web pages.
  3. Taking screenshots for visual documentation or reporting.

FAQ from MCP DuckDuckResearch?

  • Can MCP DuckDuckResearch handle all types of web pages?

Yes! It can extract content from most web pages, but some sites may have restrictions.

  • Is MCP DuckDuckResearch free to use?

Yes! The project is open-source and free to use.

  • What are the prerequisites for running MCP DuckDuckResearch?

You need Node.js (v18 or higher) and npm installed on your system.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bkataru-workshop
Star
0
Language
TypeScript
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