WebSearch-MCP
MCP ServerFree** - Self-hosted Websearch API
Capabilities11 decomposed
mcp-compliant web search tool exposure
Medium confidenceImplements the Model Context Protocol (MCP) server specification to expose a standardized web_search tool that AI assistants can invoke via stdio transport. The server translates tool calls from MCP-compatible clients (Claude Desktop, Cursor, Cline) into internal search requests and marshals results back through the MCP protocol layer, enabling seamless integration without custom client-side code.
Implements MCP server using the official MCP SDK with stdio-based bidirectional communication, enabling zero-configuration integration with Claude Desktop and other MCP clients through standardized tool schema registration rather than custom API bindings
Provides native MCP integration without requiring custom client plugins or API wrappers, unlike REST-based search APIs that require manual HTTP orchestration in agent code
real-time web search with anti-bot bypass
Medium confidenceDelegates search execution to a containerized WebSearch Crawler API that integrates with FlareSolverr to bypass Cloudflare and other anti-bot protections, enabling searches on protected domains. The crawler handles the low-level HTTP mechanics, JavaScript rendering, and bot detection evasion, returning structured JSON results that the MCP server formats for client consumption.
Decouples search execution into a dedicated Docker-based crawler service that integrates FlareSolverr for browser-based anti-bot evasion, rather than using simple HTTP clients or public search APIs, enabling searches on protected domains while maintaining MCP protocol separation
Bypasses Cloudflare and similar protections through browser automation (FlareSolverr), unlike REST search APIs (Google Custom Search, Bing) that cannot access protected sites, and unlike simple HTTP crawlers that get blocked immediately
search result caching and deduplication (implicit)
Medium confidenceWhile not explicitly documented, the architecture suggests potential for implementing result caching at the Crawler API level to avoid redundant searches for identical queries within a time window. The structured result format and centralized crawler enable future caching implementations without client-side changes, though current implementation likely lacks built-in caching or deduplication of results.
Architecture supports potential caching implementation at the Crawler API level without client-side changes, though current implementation status is unclear from documentation
Potential for server-side caching unlike REST APIs that require client-side caching logic, though current implementation status is undocumented
parameterized search filtering and refinement
Medium confidenceAccepts multiple optional filter parameters (domain restrictions, language, region, excluded terms) that are passed through the MCP tool schema to the Crawler API, enabling fine-grained result filtering without requiring multiple sequential searches. Filters are applied server-side during result processing, reducing irrelevant results and improving search precision for domain-specific or localized queries.
Exposes filter parameters through the MCP tool schema (domain, language, region, exclude_terms) that are evaluated server-side by the Crawler API, enabling declarative result filtering without requiring the client to implement post-processing logic
Provides server-side filtering integrated into the search request, unlike REST search APIs that return unfiltered results requiring client-side post-processing, and unlike simple HTTP crawlers that have no filtering capability
structured search result formatting and marshaling
Medium confidenceTransforms raw HTML search results from the Crawler API into a standardized JSON structure with title, snippet, URL, and metadata fields, then marshals this data through the MCP protocol to the client. The formatting layer ensures consistent result structure across different search sources and handles edge cases like missing fields or malformed HTML, providing clients with predictable, parseable output.
Implements server-side result formatting that normalizes raw HTML search results into a consistent JSON schema before transmission through MCP, ensuring clients receive predictable structured data rather than raw HTML or search engine-specific formats
Provides normalized result structure out-of-the-box, unlike raw search APIs that return engine-specific formats requiring client-side parsing, and unlike simple HTTP crawlers that return unstructured HTML
docker-containerized self-hosted deployment
Medium confidencePackages the WebSearch Crawler API as a Docker container that can be deployed on-premises or in private infrastructure, eliminating dependency on third-party search engine APIs or cloud services. The container encapsulates the crawler logic, FlareSolverr integration, and HTTP server, enabling single-command deployment via Docker Compose or Kubernetes orchestration while maintaining full control over data and infrastructure.
Provides Docker containerization of the entire Crawler API with integrated FlareSolverr support, enabling single-container deployment of a complete self-hosted search infrastructure without external API dependencies, rather than requiring manual setup or relying on cloud search services
Offers complete self-hosted deployment with Docker, unlike REST search APIs (Google, Bing) that require cloud accounts and API keys, and unlike manual HTTP crawler setups that require extensive configuration and dependency management
mcp server npm package distribution
Medium confidenceDistributes the WebSearch-MCP server as an npm package (websearch-mcp) that developers can install via npm/yarn and configure in their MCP client setup files. The package includes pre-built TypeScript/JavaScript code, type definitions, and configuration templates, enabling rapid integration into Node.js-based MCP clients without requiring source compilation or manual setup.
Distributes the MCP server as a standard npm package with pre-built TypeScript code and type definitions, enabling one-command installation and configuration in Node.js projects, rather than requiring Docker-only deployment or manual source compilation
Provides lightweight npm-based installation for developers who prefer package managers over Docker, unlike Docker-only distributions that require container runtime, and unlike source-based distributions that require compilation
client-agnostic mcp protocol abstraction
Medium confidenceImplements the MCP protocol layer as an abstraction that decouples the web search implementation from specific AI client details, enabling the same MCP server to work with Claude Desktop, Cursor, Cline, and any future MCP-compatible client without code changes. The server communicates via stdio transport using the standardized MCP message format, allowing clients to invoke the web_search tool through their native interfaces.
Implements MCP protocol as a client-agnostic abstraction layer that enables the same server to work with any MCP-compatible client through standardized stdio-based message passing, rather than implementing client-specific integrations or REST APIs
Provides true client-agnostic integration through MCP protocol, unlike REST APIs that require client-specific HTTP orchestration, and unlike vendor-specific integrations (OpenAI plugins, Anthropic tools) that lock into single platforms
configurable crawler api endpoint connectivity
Medium confidenceAllows the MCP server to connect to a WebSearch Crawler API instance via configurable endpoint URL (local Docker container, remote server, or cloud deployment), enabling flexible deployment topologies. The server accepts the crawler endpoint as a configuration parameter, enabling users to point to different crawler instances without code changes, supporting both local development and distributed production deployments.
Decouples MCP server from Crawler API through configurable endpoint connectivity, enabling flexible deployment topologies (local Docker, remote server, cloud) without code changes, rather than hardcoding the crawler location or requiring service discovery
Provides explicit endpoint configuration for deployment flexibility, unlike monolithic deployments that couple server and crawler, and unlike automatic service discovery that requires additional infrastructure (Kubernetes, Consul)
request-response flow orchestration through mcp
Medium confidenceImplements the complete request-response flow where the MCP server receives a tool invocation from the client, translates it into a Crawler API request, awaits the response, formats the results, and returns them through the MCP protocol. The orchestration layer handles error propagation, timeout management, and response marshaling, ensuring reliable end-to-end search execution from client invocation to result delivery.
Implements end-to-end request-response orchestration through the MCP protocol, translating client tool invocations into Crawler API requests and marshaling responses back through MCP, with integrated error handling and response formatting
Provides complete orchestration through MCP protocol, unlike REST APIs that require client-side orchestration logic, and unlike simple HTTP wrappers that lack error handling and timeout management
integration with flaresolverr for cloudflare bypass
Medium confidenceThe Crawler API integrates with FlareSolverr, a browser automation service that solves Cloudflare challenges and other anti-bot protections by rendering JavaScript and managing cookies. When the crawler encounters a protected site, it delegates the request to FlareSolverr, which returns the rendered HTML after bypassing protections, enabling searches on Cloudflare-protected domains that would otherwise be blocked.
Integrates FlareSolverr browser automation service into the Crawler API to solve Cloudflare challenges and render JavaScript-heavy sites, enabling searches on protected domains that simple HTTP crawlers cannot access
Provides Cloudflare bypass through browser automation (FlareSolverr), unlike simple HTTP crawlers that get blocked immediately, and unlike public search APIs that cannot access protected sites
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with WebSearch-MCP, ranked by overlap. Discovered automatically through the match graph.
Brave Search
** - Web and local search using Brave's Search API. Has been replaced by the [official server](https://github.com/brave/brave-search-mcp-server).
Web Search MCP
** - A server that provides local, full web search, summaries and page extration for use with Local LLMs.
Bright Data
** - Discover, extract, and interact with the web - one interface powering automated access across the public internet.
Search1API
** - One API for Search, Crawling, and Sitemaps
firecrawl-mcp-server
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
Brave Search MCP Server
Search the web using Brave Search API through MCP.
Best For
- ✓Teams building AI applications with Claude Desktop, Cursor IDE, or Cline that need real-time web access
- ✓Developers integrating web search into MCP-compatible workflows without custom protocol implementation
- ✓Organizations standardizing on MCP for tool orchestration across multiple AI clients
- ✓Developers needing to search protected websites from AI agents without manual intervention
- ✓Teams running self-hosted search infrastructure to avoid rate limits and IP bans from public search APIs
- ✓Organizations requiring on-premises web search without relying on third-party search engine APIs
- ✓Applications with high search volume and repeated queries (e.g., FAQ bots, knowledge base search)
- ✓Teams running high-traffic AI agents where search latency is critical
Known Limitations
- ⚠Requires MCP-compatible client — cannot be used with non-MCP AI assistants or APIs
- ⚠Stdio transport adds latency for each search request — not suitable for high-frequency polling scenarios
- ⚠No built-in caching or result deduplication across multiple identical search requests
- ⚠FlareSolverr integration adds 2-5 second latency per search due to browser automation overhead
- ⚠Crawler API must be running as separate Docker container — adds operational complexity vs. serverless alternatives
- ⚠No built-in rate limiting or request queuing — high-volume searches may overwhelm the crawler instance
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
** - Self-hosted Websearch API
Categories
Alternatives to WebSearch-MCP
Are you the builder of WebSearch-MCP?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →