$git clone https://github.com/Shelpuk-AI-Technology-Consulting/kindly-web-search-mcp-serverWeb search + robust content retrieval for AI coding tools.
| 1 | # Improve AI-generated code quality by 20% |
| 2 | |
| 3 | **Web search + robust content retrieval for AI coding tools.** |
| 4 | |
| 5 | Kindly Web Search is a part of the **[Shelpuk AI Technology Consulting](https://shelpuk.com) agentic suite** – a set of tools that together improve the code quality produced by AI coding agents by **15–20%**. [Read more on Claude Code generation quality improvement](https://shelpuk.com/en/blog/how-to-increase-claude-code-generation-quality-by-20-percent/). |
| 6 | |
| 7 | Works with **Claude Code**, **Codex**, **Antigravity**, **Cursor**, **Windsurf**, and any agent that supports skills or MCP servers. |
| 8 | |
| 9 | | Component | Role | |
| 10 | |--------------------------------------------------------------------------------------|---| |
| 11 | | [tdd](https://github.com/Shelpuk-AI-Technology-Consulting/agent-skill-tdd) | Enforces TDD, requirements discipline, and peer review for every coding task | |
| 12 | | [Serena](https://github.com/oraios/serena) | Semantic code navigation + persistent project memory | |
| 13 | | **Kindly Web Search** ← you are here | Up-to-date API and package documentation via web search | |
| 14 | | [Lad MCP Server](https://github.com/Shelpuk-AI-Technology-Consulting/lad_mcp_server) | Project-aware AI design and code review | |
| 15 | |
| 16 | If you like what we're building, please ⭐ **star this repo** – it's a huge motivation for us to keep going! |
| 17 | |
| 18 | ## How to use the suite |
| 19 | |
| 20 | **1. Install three MCP servers and one skill:** |
| 21 | |
| 22 | - [Serena](https://github.com/oraios/serena) |
| 23 | - [Kindly Web Search](https://github.com/Shelpuk-AI-Technology-Consulting/kindly-web-search-mcp-server) |
| 24 | - [Lad MCP Server](https://github.com/Shelpuk-AI-Technology-Consulting/lad_mcp_server) |
| 25 | - [tdd](https://github.com/Shelpuk-AI-Technology-Consulting/agent-skill-tdd) |
| 26 | |
| 27 | **2. Use the skill when requesting a feature:** |
| 28 | |
| 29 | Prompt your favorite AI coding agent (Claude Code, Codex, Cursor, etc.) as usual. Then just add `Follow $tdd` in the end. |
| 30 | |
| 31 | ``` |
| 32 | > Build [your feature description]. Follow $tdd. |
| 33 | ``` |
| 34 | |
| 35 | # Kindly Web Search MCP Server |
| 36 | |
| 37 |  |
| 38 | |
| 39 | ## Why do we need another web search MCP server? |
| 40 | |
| 41 | Picture this: You're debugging a cryptic error in Google Cloud Batch with GPU instances. Your AI coding assistant searches the web and finds the *perfect* StackOverflow thread. Great, right? Not quite. Here's what most web search MCP servers give your AI: |
| 42 | |
| 43 | ```json |
| 44 | { |
| 45 | "title": "GCP Cloud Batch fails with the GPU instance template", |
| 46 | "url": "https://stackoverflow.com/questions/76546453/...", |
| 47 | "snippet": "I am trying to run a GCP Cloud Batch job with K80 GPU. The job runs for ~30 min. and then fails..." |
| 48 | } |
| 49 | ``` |
| 50 | |
| 51 | The question is there, but **where are the answers?** Where are the solutions that other developers tried? The workarounds? The "this worked for me" comments? |
| 52 | |
| 53 | They're not there. Your AI now has to make a second call to scrape the page. Sometimes it does, sometimes it doesn't. And even when it does, most scrapers return either incomplete content or the entire webpage with navigation panels, ads, and other noise that wastes tokens and confuses the AI. |
| 54 | |
| 55 | ### The Real Problem |
| 56 | |
| 57 | At [Shelpuk AI Technology Consulting](https://shelpuk.com), we build custom AI products under a fixed-price model. Development efficiency isn't just nice to have - it's the foundation of our business. We've been using AI coding assistants since 2023 (GitHub Copilot, Cursor, Windsurf, Claude Code, Codex), and we noticed something frustrating: |
| 58 | |
| 59 | **When we developers face a complex bug, we don't just want to find a URL - we want to find the conversation.** We want to see what others tried, what worked, what didn't, and why. We want the GitHub Issue with all the comments. We want the StackOverflow thread with upvoted answers and follow-up discussions. We want the arXiv paper content, not just its abstract. |
| 60 | |
| 61 | Existing web search MCP servers are basically wrappers |