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

kindly-web-search-mcp-server

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

설치

클라이언트 선택

사용 사례

실전 활용법: kindly-web-search-mcp-server

Debug a library error by reading the whole StackOverflow thread

사전 조건

흐름

함정

Read a long GitHub Issue with full context

사전 조건

흐름

Summarize an arXiv paper with full text access

흐름

조합

다른 MCP와 조합해 10배 효율

도구

이 MCP가 노출하는 것

비용 및 제한

운영 비용

보안

권한, 시크릿, 파급범위

문제 해결

자주 발생하는 오류와 해결

대안

kindly-web-search-mcp-server 다른 것과 비교

더 보기

리소스