_tool> duckduckmcp visit_page { "url": "https://example.com", "takeScreenshot": false } ``` #### 3. take_screenshot Take a screenshot of the currently loaded page: ```typescript duckduckmcp take_screenshot {} ``` ### Example Workflow in Roo Code Here's a complete example of searching for information and visiting a result: 1. First, search for information: ```typescript duckduckmcp search_duckduckgo { "query": "TypeScript best practices", "options": { "numResults": 10, "safeSearch": "MODERATE" } } ``` 2. Then, visit one of the results: ```typescript duckduckmcp visit_page { "url": "https://example.com/typescript-practices", "takeScreenshot": true } ``` The server will automatically handle: - Browser initialization and cleanup - Content extraction and conversion to Markdown - Screenshot capture and optimization - Error handling and retries ## Development ### Prerequisites - Node.js (v18 or higher) - npm - A system capable of running Chrome/Chromium (for Playwright) ### Setup Development Environment ```bash # Install dependencies npm install # Start in development mode npm run dev # Run tests npm test # Run tests with coverage npm run test:coverage # Format code npm run format # Lint code npm run lint ``` ### Project Structure ``` mcp-duckduckresearch/ ├── src/ │ ├── browser.ts # Browser management and content extraction │ ├── search.ts # DuckDuckGo search implementation │ ├── types.ts # Type definitions and schemas │ ├── utils.ts # Utility functions │ └── index.ts # Main server implementation ├── tests/ │ ├── unit/ # Unit tests │ └── integration/ # Integration tests └── package.json # Project configuration ``` ## Testing The project uses Vitest for testing. Tests are organized into: - **Unit Tests**: Testing individual components and functions - **Integration Tests**: Testing the complete workflow - **Test Coverage**: Aiming for >80% coverage Run tests with: ```bash # Run all tests npm test # Run with coverage npm run test:coverage ``` ## Contributing 1. Fork the repository 2. Create your feature branch (`git checkout -b feature/amazing-feature`) 3. Commit your changes (`git commit -m 'Add some amazing feature'`) 4. Push to the branch (`git push origin feature/amazing-feature`) 5. Open a Pull Request ## License This project is licensed under the MIT License - see the LICENSE file for details. ## Credits - [duck-duck-scrape](https://github.com/duckduckgo/duck-duck-scrape) - DuckDuckGo search implementation - [Playwright](https://playwright.dev/) - Browser automation and screenshots - [Model Context Protocol](https://github.com/modelcontextprotocol/spec) - MCP specification and SDK2a:T650,## 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 dete

#duckduckresearch

MCP DuckDuckResearch