kindly-web-search-mcp-server MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

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

Live-Demo

In der Praxis

kindly-web-search.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/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
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

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

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

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

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

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: kindly-web-search-mcp-server

Debug a library error by reading the whole StackOverflow thread

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

Wann einsetzen: The top SO answer is often not right; the conversation below has the real fix.

Voraussetzungen

SERPER_API_KEY — serper.dev — 2500 free queries/mo

Ablauf

Search the exact error

Search for: 'fatal error: 'openssl/opensslv.h' file not found' arm64 mac — return the top 3 SO URLs.✓ Kopiert

→ 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.✓ Kopiert

→ 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.✓ Kopiert

→ Specific command sequence

Ergebnis: The real fix, not just the accepted answer — with evidence from comments.

Fallstricke

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

Kombinieren mit: filesystem

Read a long GitHub Issue with full context

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

Wann einsetzen: The issue has 80 comments and you need the signal from the noise.

Voraussetzungen

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

Ablauf

Pull structured issue data

get_content on https://github.com/vercel/next.js/issues/12345 — return structured metadata plus body and all comments.✓ Kopiert

→ 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?✓ Kopiert

→ Status + maintainer stance

Ergebnis: A grounded go/no-go decision on a library upgrade.

Kombinieren mit: github

Summarize an arXiv paper with full text access

👤 Researchers, curious devs ⏱ ~10 min beginner

Wann einsetzen: You don't want a snippet; you want to quote section 3.2.

Ablauf

Fetch the paper

get_content https://arxiv.org/abs/2410.XXXXX — full text.✓ Kopiert

→ Markdown of the paper
Targeted summary

Summarize the methodology (section 3) in 5 bullets and quote the key claim from the results table.✓ Kopiert

→ Summary with verbatim quote

Ergebnis: Paper understanding without leaving chat.

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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.✓ Kopiert

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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
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)

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: Serper: 2500/mo free. Tavily: 1000/mo free. SearXNG self-hosted: unlimited.
Tokens pro Aufruf: web_search with full content: 2-6k per call. get_content: 1-10k depending on page.
Kosten in €: Free with provider free tiers; self-host SearXNG for zero cost
Tipp: For iterative research, lower num_results to 2 — kindly returns full content per result, so 3 can be expensive.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: Env vars: SERPER_API_KEY or TAVILY_API_KEY or SEARXNG_BASE_URL

Datenabfluss: Queries to chosen search provider + fetches to result URLs

Niemals gewähren: 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.

Fehlerbehebung

Häufige Fehler und Lösungen

No provider configured

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

Prüfen: env | grep -E 'SERPER|TAVILY|SEARXNG'

Chromium not found

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

Prüfen: which google-chrome || which chromium

Python version error

Requires Python 3.13+. Upgrade via pyenv or uv.

Prüfen: python3 --version

Alternativen

kindly-web-search-mcp-server vs. andere

Alternative	Wann stattdessen	Kompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen