kindly-web-search-mcp-server MCP — ユースケース, インストール & ライブデモ

なぜ使うのか

主な機能

web_search returns page_content as Markdown, not just title/snippet
get_content does platform-aware full fetches (SO threads, GitHub Issues, arXiv)
Supports Serper (primary), Tavily (fallback), or self-hosted SearXNG
Optional GITHUB_TOKEN enables structured GitHub Issue extraction
Works from Claude Code, Codex, Cursor, Copilot, Gemini, Antigravity

ライブデモ

実際の動作

kindly-web-search.replay ▶ 準備完了

0/0

インストール

クライアントを選択

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "kindly-web-search": {
      "command": "uvx",
      "args": [
        "kindly-web-search-mcp-server"
      ],
      "_inferred": true
    }
  }
}

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

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "kindly-web-search": {
      "command": "uvx",
      "args": [
        "kindly-web-search-mcp-server"
      ],
      "_inferred": true
    }
  }
}

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

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "kindly-web-search": {
      "command": "uvx",
      "args": [
        "kindly-web-search-mcp-server"
      ],
      "_inferred": true
    }
  }
}

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

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "kindly-web-search": {
      "command": "uvx",
      "args": [
        "kindly-web-search-mcp-server"
      ],
      "_inferred": true
    }
  }
}

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

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "kindly-web-search",
      "command": "uvx",
      "args": [
        "kindly-web-search-mcp-server"
      ]
    }
  ]
}

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

~/.config/zed/settings.json

{
  "context_servers": {
    "kindly-web-search": {
      "command": {
        "path": "uvx",
        "args": [
          "kindly-web-search-mcp-server"
        ]
      }
    }
  }
}

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

claude mcp add kindly-web-search -- uvx kindly-web-search-mcp-server

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

ユースケース

実用的な使い方： kindly-web-search-mcp-server

Debug a library error by reading the whole StackOverflow thread

👤 Developers hit with a cryptic error ⏱ ~10 min beginner

使うタイミング： The top SO answer is often not right; the conversation below has the real fix.

前提条件

SERPER_API_KEY — serper.dev — 2500 free queries/mo

フロー

Search the exact error

Search for: 'fatal error: 'openssl/opensslv.h' file not found' arm64 mac — return the top 3 SO URLs.✓ コピーしました

→ SO URLs with snippets
Fetch the full thread of the most relevant

get_content on the top SO URL — give me the whole thread including every comment.✓ コピーしました

→ Full Q+A+comments in Markdown
Pick the fix the thread's consensus supports

Which answer (including ones below the accepted one) does the thread's comments actually validate? Show me the exact commands.✓ コピーしました

→ Specific command sequence

結果： The real fix, not just the accepted answer — with evidence from comments.

注意点

SO pages can be huge; full content can be 10k+ tokens — Ask for an executive summary first, then drill in

組み合わせ： filesystem

Read a long GitHub Issue with full context

👤 Engineers evaluating whether to upgrade a dependency ⏱ ~10 min beginner

使うタイミング： The issue has 80 comments and you need the signal from the noise.

前提条件

GITHUB_TOKEN (optional but recommended) — A classic/fine-grained token; empty scope set fine for public repos

フロー

Pull structured issue data

get_content on https://github.com/vercel/next.js/issues/12345 — return structured metadata plus body and all comments.✓ コピーしました

→ Structured extract, not raw HTML
Distill signal

Summarize: is this fixed, open, workaround-only? Who from the maintainer team has commented, and what was their last position?✓ コピーしました

→ Status + maintainer stance

結果： A grounded go/no-go decision on a library upgrade.

組み合わせ： github

Summarize an arXiv paper with full text access

👤 Researchers, curious devs ⏱ ~10 min beginner

使うタイミング： You don't want a snippet; you want to quote section 3.2.

フロー

Fetch the paper

get_content https://arxiv.org/abs/2410.XXXXX — full text.✓ コピーしました

→ Markdown of the paper
Targeted summary

Summarize the methodology (section 3) in 5 bullets and quote the key claim from the results table.✓ コピーしました

→ Summary with verbatim quote

結果： Paper understanding without leaving chat.

組み合わせ

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

kindly-web-search + github

Kindly reads the issue discussion; github MCP creates a tracking issue in your own repo

Read the discussion on open-upstream/project#432 via kindly, then open a shadowing issue in our team's repo summarizing it.✓ コピーしました

kindly-web-search + filesystem

Save researched answers as Markdown notes

Research 'best practices for Postgres connection pooling with pgbouncer', save the full SO thread + two docs links under ./notes/pgbouncer.md.✓ コピーしました

ツール

このMCPが提供する機能

ツール	入力	呼び出すタイミング	コスト
web_search	query: str, num_results?: int (default 3)	Any web search where you'd have followed with a fetch anyway	1 search provider call + N fetches
get_content	url: str	Deep dive on a specific URL	1 fetch (plus provider ops for platform parsing)

コストと制限

運用コスト

APIクォータ: Serper: 2500/mo free. Tavily: 1000/mo free. SearXNG self-hosted: unlimited.
呼び出しあたりのトークン: web_search with full content: 2-6k per call. get_content: 1-10k depending on page.
金額: Free with provider free tiers; self-host SearXNG for zero cost
ヒント: For iterative research, lower num_results to 2 — kindly returns full content per result, so 3 can be expensive.

セキュリティ

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

認証情報の保管： Env vars: SERPER_API_KEY or TAVILY_API_KEY or SEARXNG_BASE_URL

データ送信先： Queries to chosen search provider + fetches to result URLs

絶対に付与しない： GitHub token with repo write — public-read is enough for content extraction

Returned content includes whatever the live page serves — verify before trusting for security-critical decisions.
Requires a Chromium browser on the host for full-content rendering.

トラブルシューティング

よくあるエラーと対処法

No provider configured

Set at least one of SERPER_API_KEY, TAVILY_API_KEY, or SEARXNG_BASE_URL.

確認： env | grep -E 'SERPER|TAVILY|SEARXNG'

Chromium not found

Install Chrome, Edge, Brave, or chromium. Set PUPPETEER_EXECUTABLE_PATH if auto-detect fails.

確認： which google-chrome || which chromium

Python version error

Requires Python 3.13+. Upgrade via pyenv or uv.

確認： python3 --version

代替案

kindly-web-search-mcp-server 他との比較

代替案	代わりに使う場面	トレードオフ
omnisearch	You want many providers including AI-search in one MCP	Less platform-aware; snippets-first
brave-search	You only want search, not full-content retrieval	Snippets only
fetch MCP	You don't need search, just URL fetching	No search

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

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