Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Omnisearch MCP Server

MCP server that unifies web search, AI answer, GitHub search, and web extraction providers including Tavily, Brave, Kagi, Exa, Linkup, Firecrawl, and GitHub behind four consolidated tools.

by Scott Spence·added 2026-06-06·
Claude CodeClaude Desktop
HarnessClaude CodeClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • Omnisearch MCP Server can query multiple third-party search, AI answer, GitHub search, extraction, scraping, crawling, summarization, and content-processing providers.
  • Firecrawl crawl, scrape, map, extract, and action modes can interact with websites and may trigger robots.txt, TOS, rate-limit, or authentication concerns.
  • GitHub search depends on the configured token scope and can reveal private code, repositories, users, or organization metadata when a broad token is used.
  • Large result mode can write response content to files; review where those files are stored before using it with private or regulated data.
  • Require confirmation before crawling sites, extracting private URLs, using authenticated providers on sensitive targets, or running broad GitHub searches against private organizations.

Privacy notes

  • Provider API keys, GitHub tokens, search queries, URLs, extracted page content, crawled site maps, scraped text, summaries, AI answers, GitHub search results, and large-result files can be exposed to the MCP client.
  • Search and extraction providers may log queries, URLs, source content, account identifiers, usage metadata, and generated responses according to their own policies.
  • Web extraction can capture personal data, paywalled content, internal URLs, or proprietary documents if supplied by the user or available to an authenticated provider.
  • GitHub search output may include repository names, code snippets, file paths, commit metadata, and organization details.
  • Keep provider credentials in local MCP configuration only, and avoid sharing transcripts that contain private queries, URLs, source text, or tokens.

Prerequisites

  • Node.js 22 or newer for the published npm package.
  • At least one provider API key for Tavily, Kagi, Brave Search, GitHub, Exa, Linkup, or Firecrawl.
  • Optional `FIRECRAWL_BASE_URL` when using a self-hosted Firecrawl instance.
  • Optional `OMNISEARCH_LARGE_RESULT_MODE` choice for file or inline handling of large results.
  • Review of which providers, quotas, search indexes, URLs, GitHub scopes, and extraction/crawling modes Claude may use.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
15 minutes
Difficulty
intermediate
Tool listing metadata
Disclosure
Community-maintained MIT MCP server that wraps multiple external search, extraction, AI-answer, and GitHub providers. Users must follow each provider's API, quota, billing, retention, and website-use policies.
Full copyable content
{
  "mcpServers": {
    "omnisearch": {
      "command": "npx",
      "args": ["mcp-omnisearch"],
      "env": {
        "TAVILY_API_KEY": "your-tavily-key",
        "KAGI_API_KEY": "your-kagi-key",
        "BRAVE_API_KEY": "your-brave-key",
        "GITHUB_API_KEY": "your-github-token",
        "EXA_API_KEY": "your-exa-key",
        "LINKUP_API_KEY": "your-linkup-key",
        "FIRECRAWL_API_KEY": "your-firecrawl-key"
      }
    }
  }
}

About this resource

Content

Omnisearch MCP Server connects Claude and other MCP clients to multiple search, AI-answer, GitHub search, and web-extraction providers through four consolidated tools: web_search, ai_search, github_search, and web_extract.

Use it when Claude needs one MCP interface for provider-backed web search, sourced AI answers, GitHub search, URL extraction, crawling, scraping, summaries, similar-content discovery, or content retrieval.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, npm metadata, license, package metadata, server manifest, provider selection guide, large-results guide, server entrypoint, and tool registry for current setup and behavior details.

Features

  • Search the web through Tavily, Brave Search, Kagi, Exa, or Kagi Enrichment.
  • Get sourced AI answers through Kagi FastGPT, Exa Answer, or Linkup.
  • Search GitHub code, repositories, and users.
  • Extract, scrape, crawl, map, summarize, or find similar content through Tavily, Kagi, Firecrawl, or Exa.
  • Skip unavailable providers when API keys are not configured.
  • Use provider-selection documentation to choose a provider by task, key, mode, and capability.
  • Route large results either inline or through file mode.

Installation

Configure at least one provider API key, then launch the server:

{
  "mcpServers": {
    "omnisearch": {
      "command": "npx",
      "args": ["mcp-omnisearch"],
      "env": {
        "TAVILY_API_KEY": "your-tavily-key",
        "KAGI_API_KEY": "your-kagi-key",
        "BRAVE_API_KEY": "your-brave-key",
        "GITHUB_API_KEY": "your-github-token",
        "EXA_API_KEY": "your-exa-key",
        "LINKUP_API_KEY": "your-linkup-key",
        "FIRECRAWL_API_KEY": "your-firecrawl-key"
      }
    }
  }
}

Only include the provider keys you actually intend Claude to use. Use a least-privilege GitHub token when enabling GitHub search.

Use Cases

  • Search current web results through a preferred provider.
  • Ask for a sourced AI answer and compare providers.
  • Search public or approved private GitHub code for examples.
  • Extract a long article, documentation page, or site map.
  • Crawl an approved documentation site and summarize relevant pages.
  • Switch providers when one service is unavailable, rate-limited, or poorly suited to the task.

Safety and Privacy

Omnisearch MCP Server is a broker over multiple external providers. Scope API keys carefully, confirm before crawling or scraping, and respect website terms, robots policies, provider quotas, billing, and retention behavior.

Treat provider keys, GitHub tokens, queries, URLs, extracted content, crawled pages, GitHub results, AI answers, summaries, and large-result files as sensitive. Avoid sending private URLs, proprietary source text, or broad GitHub tokens through providers that should not receive them.

#search#web-extraction#github-search#crawling#multi-provider

Source citations

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.