Open WebSearch
Multi-engine MCP server, CLI, and local daemon for agent web search and content retrieval — skill-guided workflows, no API keys.
At a glance.
A compact read before the deeper capability notes and official setup links.
Core features.
Feature cards focus on what the tool helps users do, not generated setup commands.
open-websearch provides an MCP server, CLI, and local daemon, and can also be paired with skill-guided agent workflows for live web search and content retrieval without API keys.
Web search using multi-engine results
Configurable number of results per search
Customizable default search engine
Best when you want to connect open-websearch to Claude Desktop, Cherry Studio, Cursor, or another MCP client.
Best when you want a reusable long-lived local HTTP service exposing status, GET /health, and POST /search / POST /fetch-.
Start it explicitly with open-websearch serve and check it with open-websearch status.
A skill does not replace MCP, CLI, or the local daemon; it typically works together with the CLI and/or local daemon to help an agent discover, activate, and use the smallest working path.
Agent / Skill / MCP / Workflow fit.
This panel keeps technical format separate from the user-facing AI category.
Official setup path.
Generated install snippets are intentionally not mirrored here because they drift. The page links to source-owned setup docs instead.
Evidence and adoption notes.
These notes help a user decide whether to investigate the official project further.
Source repository last pushed at 2026-05-08T05:34:14Z.
Generated from source metadata; confirm operational details in the official project before adopting it.
Review the upstream license, maintenance activity, and issue history before using it in production.