MyWebSearch - multi-engine web search MCP server, CLI and local daemon. No API keys required.
My-websearch is an MCP integration. MyWebSearch - multi-engine web search MCP server, CLI and local daemon. No API keys required.
The published npm package is my-websearch, version 1.0.24. Its declared MCP transport is stdio.
The package declares EXA_API_KEY: Optional Exa API key (https://dashboard.exa.ai/api-keys) — only needed for the exa search engine.
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 1.0.24 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| EXA_API_KEY | Optional Exa API key (https://dashboard.exa.ai/api-keys) — only needed for the exa search engine | Check documentation |
Retrieve public web pages as readable Markdown with the reference Fetch MCP server, including pagination for longer responses.
Use Firecrawl MCP to retrieve website content and extract information for research through Firecrawl’s API-backed web tools.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Automates browsers and APIs, enabling Large Language Models (LLMs) to interact with web pages for tasks like screenshot capture and JavaScript
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.