/ ディレクトリ / プレイグラウンド / mcp-searxng
● コミュニティ ihor-sokoliuk ⚡ 即起動

mcp-searxng

作者 ihor-sokoliuk · ihor-sokoliuk/mcp-searxng

Private, self-hosted web search for your AI — no API key, no rate-limit drama, no search provider tracking your queries.

mcp-searxng connects to any SearXNG instance (your own or a public one) and exposes two tools: web search with pagination/time/lang/safesearch, and URL-to-markdown extraction. Best when you already run SearXNG or want zero-tracking search without paying per query.

なぜ使うのか

主な機能

ライブデモ

実際の動作

searxng.replay ▶ 準備完了
0/0

インストール

クライアントを選択

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "searxng": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-searxng"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config を開く。保存後、アプリを再起動。

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "searxng": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-searxng"
      ],
      "_inferred": true
    }
  }
}

Cursor は Claude Desktop と同じ mcpServers スキーマを使用。プロジェクト設定はグローバルより優先。

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "searxng": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-searxng"
      ],
      "_inferred": true
    }
  }
}

Cline サイドバーの MCP Servers アイコンをクリックし、"Edit Configuration" を選択。

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "searxng": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-searxng"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop と同じ形式。Windsurf を再起動して反映。

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "searxng",
      "command": "npx",
      "args": [
        "-y",
        "mcp-searxng"
      ]
    }
  ]
}

Continue はマップではなくサーバーオブジェクトの配列を使用。

~/.config/zed/settings.json
{
  "context_servers": {
    "searxng": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-searxng"
        ]
      }
    }
  }
}

context_servers に追加。保存時に Zed がホットリロード。

claude mcp add searxng -- npx -y mcp-searxng

ワンライナー。claude mcp list で確認、claude mcp remove で削除。

ユースケース

実用的な使い方: mcp-searxng

Fact-check a claim against multiple sources

👤 Writers, analysts ⏱ ~10 min beginner

使うタイミング: You need to confirm something across a few independent sources.

フロー
  1. Search
    Search the exact claim phrase. Return top 10 from different domains.✓ コピーしました
    → Diverse result list
  2. Cross-read
    web_url_read on the 3 most authoritative — quote the sections that speak to the claim.✓ コピーしました
    → Quoted excerpts
  3. Verdict
    Claim: supported, contested, or false? Cite specifically.✓ コピーしました
    → Verdict with citations

結果: A cited fact-check.

Build a zero-API-key research assistant for your team

👤 Teams that won't/can't buy search API keys ⏱ ~40 min intermediate

使うタイミング: Everyone wants AI search but no one wants to manage Tavily keys per person.

フロー
  1. Run SearXNG behind your intranet
    Set up SearXNG container on the team server, point mcp-searxng at it.✓ コピーしました
    → All team AI clients search via shared instance
  2. Test from multiple clients
    Run the same query from Claude Desktop and Cursor — both should hit the same SearXNG.✓ コピーしました
    → Consistent results

結果: Team-wide AI search with one instance, no per-user billing.

組み合わせ

他のMCPと組み合わせて10倍の力を

searxng + filesystem

Research and save notes

Search 'SBOM best practices', web_url_read the top 3, save a distilled memo to ./notes/sbom.md.✓ コピーしました

Stack both — kindly for platform-aware full fetches, searxng for private general search

Use searxng for the initial search; if any result is SO/GitHub, fall back to kindly for richer content.✓ コピーしました

ツール

このMCPが提供する機能

ツール入力呼び出すタイミングコスト
searxng_web_search query: str, pageno?: int, time_range?: day|week|month|year, language?: str, safesearch?: 0|1|2 Any web search free (your SearXNG)
web_url_read url: str, start_heading?: int, end_heading?: int, start_paragraph?: int, end_paragraph?: int Clean extraction of an article free

コストと制限

運用コスト

APIクォータ
Unlimited (your SearXNG instance)
呼び出しあたりのトークン
Search: 500-1500 tokens. Read: 1-10k depending on page.
金額
Free
ヒント
Narrow queries with time_range and language — cuts both tokens and SearXNG load.

セキュリティ

権限、シークレット、影響範囲

認証情報の保管: No keys needed; just SEARXNG_URL
データ送信先: Your SearXNG instance (which in turn queries upstream engines)

トラブルシューティング

よくあるエラーと対処法

Connection refused

SearXNG not running or SEARXNG_URL wrong. curl the URL directly first.

確認: curl $SEARXNG_URL
Empty results for any query

SearXNG blocked by upstream engines or misconfigured. Check /search directly in browser.

確認: Open $SEARXNG_URL/search?q=test
web_url_read returns mostly nav junk

Some sites are JS-heavy; narrow with heading/paragraph ranges, or use a different extractor.

代替案

mcp-searxng 他との比較

代替案代わりに使う場面トレードオフ
omnisearchYou want multi-provider + AI searchRequires provider API keys
kindly-web-searchYou want platform-aware full contentStill needs Serper/Tavily key unless paired with SearXNG
brave-searchYou're OK with one commercial providerPaid above the free tier

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る