search-rotation MCP server

One MCP server for web search and page extraction across multiple providers.

Built by Robin Bially.

Rotate across available quotas, automatically fail over when a provider is unavailable, and return consistent results to your AI assistant. A local dashboard lets you manage API keys, reorder engines, check quotas, and inspect request history.

Actual dashboard UI, shown in English with illustrative demo data. Calls and provider budgets are displayed separately; activity bars offer time-window and per-engine details.

Quick start

npm

npx -y search-rotation --http --open

Requires Node.js 20.3+. For MCP over stdio, configure your client to run npx -y search-rotation with no arguments. The server is also listed in the official MCP Registry as io.github.robin-bially/search-rotation.

Homebrew

brew install robin-bially/tap/search-rotation
search-rotation --http --open

Homebrew installs the required Node.js runtime. For MCP over stdio, configure your client to run search-rotation with no arguments. See the Homebrew tap for upgrades and details.

Pinned release from GitHub

npx -y --allow-git=all github:robin-bially/search-rotation-mcp#v0.4.11

Use this when you want a fixed version instead of the current npm release.

Add your provider keys in the dashboard, then connect your assistant using the MCP client setup guide for Codex, Claude, Cursor, or OpenCode.

What you get

• Search and fetch: independent rotation for web search and Markdown page extraction.
• Automatic failover: quota-aware ordering, rate-limit cooldowns, and request timeouts.
• Local dashboard: API keys, drag-and-drop engine order, per-engine calls and errors, separate quota balances, and interactive request history.
• Local or remote: MCP over stdio or authenticated Streamable HTTP.

Providers: Tavily · Firecrawl · Parallel · Exa · Google PSE · Jina Reader · DuckDuckGo HTML. Keyless access and quota accounting vary by provider.

MCP tools

websearch · fetchurl · enginestatus · opendashboard

The dashboard's MCP Tools tab explains each tool, its parameters, and copyable example calls.

Actual dashboard UI, shown in English.

Search time filters

web_search accepts the following arguments:

Use either timeRange or explicit dates. One-sided bounds and equal start/end dates are allowed; invalid calendar dates, reversed bounds, and mixing relative and explicit filters are rejected before any provider request.

Shortened. The full README is on GitHub.