How does Search Gateway simplify API integration?

It converts diverse external search APIs into a consistent local service, offering a provider-agnostic request/response model. This streamlines development and integration with systems like Codex.

What advanced features does it offer for search management?

Search Gateway includes automatic provider selection, health-aware rotation, retryable fallback, circuit breaking, and configurable caching to ensure robust and reliable search operations.

How can I configure Search Gateway?

Configuration can be managed through environment variables for API keys or a TOML file for detailed settings, including timeouts, cache behavior, circuit breaker thresholds, and provider order.

What is Search Gateway?

Search Gateway is a Rust-based tool that provides a unified interface to external search APIs, making them accessible via a local MCP server or a direct command-line interface (CLI).

What search providers does Search Gateway support?

It currently supports Tavily for answer-oriented queries and DuckDuckGo as a lightweight fallback. The tool intelligently routes requests and manages provider health.

Search Gateway

Name: Search Gateway
Author: AnNingUI

0•

Provides a unified search gateway, converting external search APIs into a local MCP service with CLI access.

Search Gateway is a Rust project designed to act as a unified interface for various search providers, specifically converting APIs like Tavily into a local MCP (Machine Comprehension Platform) service. It offers both a direct command-line interface (CLI) for immediate search, extraction, and crawling operations, and an MCP server for seamless integration with other systems. This dual approach ensures comprehensive MCP support while enabling lazy-loading through skills that invoke the CLI as needed, providing a robust and flexible solution for integrating external search capabilities with features like automatic provider selection, health-aware rotation, and circuit breaking.

主な機能

01Local `stdio` MCP server with a compact tool surface.

020 GitHub stars

03Default search routing preferring Tavily for answer-oriented queries, with DuckDuckGo as a lightweight fallback.

04CLI supporting `search`, `extract`, `crawl`, and `status` operations.

05Automatic provider selection, health-aware rotation, retryable fallback, and circuit breaking.

06Unified search gateway with provider-agnostic request and response models.

ユースケース

01Configuring a robust search proxy with provider fallbacks, caching, and circuit breaking.

02Integrating external search APIs like Tavily and DuckDuckGo into an MCP environment.

03Providing on-demand web search, extraction, and crawling capabilities via a local server or CLI.