
MySearch-Proxy
by skernelx·★ 120·Score 47
Unified search MCP server that proxies requests to Tavily, Firecrawl, Exa and Social with a central management layer.
Overview
MySearch-Proxy is a comprehensive search stack for AI assistants that consolidates multiple search providers into a single interface. It provides MCP tools for search, URL extraction, research workflows, and health monitoring. The server features a proxy layer for team deployment and token management, with support for both direct provider connections and a proxy-first architecture. The implementation includes advanced routing strategies, caching, and fallback mechanisms to ensure reliable search results across different query types.
Try asking AI
After installing, here are 5 things you can ask your AI assistant:
When to choose this
Choose MySearch-Proxy when you need a unified search interface for multiple AI assistants or want centralized management of search provider credentials and quotas.
When NOT to choose this
Avoid this if you need direct control over individual provider APIs without abstraction, or if you're not comfortable with the proxy-based architecture requiring additional infrastructure.
Tools this server exposes
4 tools extracted from the READMEsearchUnified search across Tavily, Firecrawl, Exa, and Social/X
extract_urlExtract content from a webpage URL
researchPerform comprehensive research with search and content extraction
mysearch_healthCheck health status of search providers
Comparable tools
Installation
Installation
Option 1: Direct MCP Installation
cd /path/to/MySearch-Proxy
python3 -m venv venv
source venv/bin/activate
# Configure environment variables
echo 'MYSEARCH_PROXY_BASE_URL=https://your-mysearch-proxy.example.com' >> .env
echo 'MYSEARCH_PROXY_API_KEY=mysp-...' >> .env
./install.shOption 2: Deploy Proxy First
mkdir -p mysearch-proxy-data
docker run -d \
--name mysearch-proxy \
--restart unless-stopped \
-p 9874:9874 \
-e ADMIN_PASSWORD=change-me \
-v $(pwd)/mysearch-proxy-data:/app/data \
skernelx/mysearch-proxy:latestClaude Desktop Configuration
Add to claude_desktop_config.json:
{
"mcpServers": {
"mysearch": {
"command": "python",
"args": ["-m", "mysearch.mcp_server"],
"env": {
"MYSEARCH_PROXY_BASE_URL": "https://your-mysearch-proxy.example.com",
"MYSEARCH_PROXY_API_KEY": "mysp-..."
}
}
}
}FAQ
- What search providers are supported?
- Currently supports Tavily, Firecrawl, Exa, and Social/X with options for domain filtering and result prioritization.
- How does routing work between providers?
- Uses intelligent routing: web/news queries go to Tavily, docs/github/pdf queries go to Firecrawl, with fallback mechanisms to Exa when needed.
Compare MySearch-Proxy with
Last updated · Auto-generated from public README + GitHub signals.