by spences10
Omnisearch unifies search by selecting top providers like Tavily, Brave, and Perplexity for flexible, enhanced content r
Provides unified search across multiple providers (Tavily, Brave, Perplexity, Kagi, Exa, GitHub) through a single interface with advanced search operators and content processing.
Omnisearch is a community-built MCP server published by spences10 that provides AI assistants with tools and capabilities via the Model Context Protocol. Omnisearch unifies search by selecting top providers like Tavily, Brave, and Perplexity for flexible, enhanced content r It is categorized under search web.
You can install Omnisearch in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Omnisearch is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
Share your MCP server with the developer community
Omnisearch reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We evaluated Omnisearch against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: Omnisearch is the kind of server we cite when onboarding engineers to host + tool permissions.
We wired Omnisearch into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Omnisearch reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Omnisearch has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Omnisearch reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend Omnisearch for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Omnisearch is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend Omnisearch for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 69
A Model Context Protocol (MCP) server that provides unified access to multiple search providers and AI tools. This server combines the capabilities of Tavily, Perplexity, Kagi, Jina AI, Brave, Exa AI, and Firecrawl to offer comprehensive search, AI responses, content processing, and enhancement features through a single interface.
<a href="https://glama.ai/mcp/servers/gz5wgmptd8"> <img width="380" height="200" src="https://glama.ai/mcp/servers/gz5wgmptd8/badge" alt="Glama badge" /> </a>
site:, -site:, filetype:/ext:, intitle:,
inurl:, inbody:, inpage:, lang:, loc:, before:,
after:, +term, -term, and exact phrases ("phrase").site:, -site:, filetype:/ext:, intitle:, inurl:,
inbody:, inpage:, lang:, loc:, before:, after:, +term,
-term, and exact phrases ("phrase").filename:, path:, repo:,
user:, language:, in:file)MCP Omnisearch provides powerful search capabilities through operators and parameters:
Brave & Kagi Operators (use in query string):
site:example.com, -site:example.comfiletype:pdf or ext:pdfintitle:term, inurl:term, inbody:term,
inpage:termlang:en (ISO 639-1 codes)loc:us (ISO 3166-1 codes)before:2024, after:2024-01-01"exact phrase"+required, -excludedTavily (API parameters only):
include_domains, exclude_domains// Brave/Kagi: Advanced operators in query
{
"query": "filetype:pdf lang:en site:microsoft.com +typescript -javascript",
"provider": "brave"
}
// Brave/Kagi: Search gists
{
"query": "site:gist.github.com claude code settings",
"provider": "brave"
}
// Tavily: API parameters for domain filtering
{
"query": "typescript guide",
"provider": "tavily",
"include_domains": ["microsoft.com"]
}
filename:remote.ts - Search for specific filespath:src/lib - Search within specific directoriesrepo:user/repo - Search within specific repositoriesuser:username - Search within a user's repositorieslanguage:typescript - Filter by programming languagein:file "export function" - Search for text within filesMCP Omnisearch is designed to work with the API keys you have available. You don't need to have keys for all providers - the server will automatically detect which API keys are available and only enable those providers.
For example:
This flexibility makes it easy to get started with just one or two providers and add more as needed.
This server requires configuration through your MCP client. Here are examples for different environments:
Add this to your Cline MCP settings:
{
"mcpServers": {
"mcp-omnisearch": {
"command": "node",
"args": ["/path/to/mcp-omnisearch/dist/index.js"],
"env": {
"TAVILY_API_KEY": "your-tavily-key",
"PERPLEXITY_API_KEY": "your-perplexity-key",
"KAGI_API_KEY": "your-kagi-key",
"JINA_AI_API_KEY": "your-jina-key",
"BRAVE_API_KEY": "your-brave-key",
"GITHUB_API_KEY": "your-github-key",
"EXA_API_KEY": "your-exa-key",
"FIRECRAWL_API_KEY": "your-firecrawl-key",
"FIRECRAWL_BASE_URL": "http://localhost:3002"
},
"disabled": false,
"autoApprove": []
}
}
}
For WSL environments, add this to your Claude Desktop configuration:
{
"mcpServers": {
"mcp-omnisearch": {
"command": "wsl.exe",
"args": [
"bash",
"-c",
"TAVILY_API_KEY=key1 PERPLEXITY_API_KEY=key2 KAGI_API_KEY=key3 JINA_AI_API_KEY=key4 BRAVE_API_KEY=key5 GITHUB_API_KEY=key6 EXA_API_KEY=key7 FIRECRAWL_API_KEY=key8 FIRECRAWL_BASE_URL=http://localhost:3002 node /path/to/mcp-omnisearch/dist/index.js"
]
}
}
}
The server uses API keys for each provider. You don't need keys for all providers - only the providers corresponding to your available API keys will be activated:
TAVILY_API_KEY: For Tavily SearchPERPLEXITY_API_KEY: For Perplexity AIKAGI_API_KEY: For Kagi services (FastGPT, Summarizer, Enrichment)JINA_AI_API_KEY: For Jina AI services (Reader, Grounding)BRAVE_API_KEY: For Brave SearchGITHUB_API_KEY: For GitHub search services (Code, Repository, User
search)EXA_API_KEY: For Exa AI services (Search, Answer, Contents,
Similar)FIRECRAWL_API_KEY: For Firecrawl services (Scrape, Crawl, Map,
Extract, Actions)FIRECRAWL_BASE_URL: For self-hosted Firecrawl instances (optional,
defaults to Firecrawl cloud service)You can start with just one or two API keys and add more later as needed. The server will log which providers are available on startup.
To use GitHub search features, you'll need a GitHub personal access token with public repository access only for security:
Go to GitHub Settings: Navigate to GitHub Settings > Developer settings > Personal access tokens
Create a new token: Click "Generate new token" → "Generate new token (classic)"
Configure token settings:
Name: MCP Omnisearch - Public Search
Expiration: Choose your preferred expiration (90 days recommended)
Scopes: Leave all checkboxes UNCHECKED
⚠️ Important: Do not select any scopes. An empty scope token can only access public repositories and user profiles, which is exactly what we want for search functionality.
Generate and copy: Click "Generate token" and copy the token immediately
Add to environment: Set GITHUB_API_KEY=your_token_here
Security Notes:
If you're running a self-hosted instance of Firecrawl, you can
configure MCP Omnisearch to use it by setting the FIRECRAWL_BASE_URL
environment variable. This allows you to maintain complete control
over your data processing pipeline.
Self-hosted Firecrawl setup:
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ Use when
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid when
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.