Kagimcp vs MCP Local Rag
A side-by-side look at the Kagimcp and MCP Local Rag MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kagimcp for search & data extraction work as a local process; choose MCP Local Rag for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kagimcp when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
KAGI_API_KEY. - You want tools like
kagi_search_fetch, kagi_extract.
Choose MCP Local Rag when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
rag_search_ddgs, rag_search_google, deep_research.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 80/100 · Excellent | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | KAGI_API_KEY | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 546 | 134 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 2 | 5 |
| Full listing | View Kagimcp | View MCP Local Rag |
Tools & capabilities
Kagimcp tools 2
kagi_search_fetchFetch web results for a query using the Kagi Search API. Use for general search and when the user explicitly tells you to 'fetch' results/information. Results are numbered so that a user may refer to a result by a specific number.kagi_extractExtract the content of a web page as markdown using the Kagi Extract API. Use this to read the full content of a page when needed.
MCP Local Rag tools 5
rag_search_ddgsSearch the web for a given query using DuckDuckGo. Returns context to the LLM with RAG-like similarity scoring to prioritize the most relevant results. This tool fetches web search results, scores them by semantic similarity to the query using text embeddings, and returns the top-ranked content as markdown text.rag_search_googleSearch on Google for a given query using ddgs. Give back context to the LLM with a RAG-like similarity sort.deep_researchPerform deep research across multiple search terms using specified search backends. This tool aggregates results from multiple searches across chosen engines, scores them by relevance, and returns the most relevant content with duplicates removed. Perfect for comprehensive research on a topic. Available backends: bing, brave, duckduckgo, google, grokipedia, mojeek, yandex, yahoo, wikipedia USAGE GUIDANCE FOR LLM: 1. Ask the user which backend(s) they prefer, OR 2. Choose appropriate backend(s) based on context: - ["duckduckgo"] - Privacy-focused, general search - ["google"] - Comprehensive results, best for technical queries - ["duckduckgo", "google"] - Maximum coverage (default) - ["wikipedia"] - Factual/encyclopedia content - ["bing", "google"] - Balanced commercial engines - Multiple backends for broader research coverage 3. For specific use cases, consider: - deep_research_google() - shortcut for Google-only - deep_research_ddgs() - shortcut for DuckDuckGo-onlydeep_research_googlePerform deep research across multiple search terms using ONLY Google. Aggregates results from multiple Google searches, scores them by relevance, and returns the most relevant content with duplicates removed.deep_research_ddgsPerform deep research across multiple search terms using ONLY DuckDuckGo. Aggregates results from multiple DuckDuckGo searches, scores them by relevance, and returns the most relevant content with duplicates removed.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kagimcp
{
"mcpServers": {
"kagisearch-kagimcp": {
"command": "uvx",
"args": [
"kagimcp"
],
"env": {
"KAGI_API_KEY": "YOUR_KAGI_API_KEY_HERE"
}
}
}
}
MCP Local Rag
{
"mcpServers": {
"nkapila6-mcp-local-rag": {
"command": "uvx",
"args": [
"--python=3.10",
"--from",
"git+https://github.com/nkapila6/mcp-local-rag",
"mcp-local-rag"
]
}
}
}
Frequently asked questions
Kagimcp is categorized under Search & Data Extraction and uses a local stdio subprocess. MCP Local Rag belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Kagimcp for search & data extraction work and MCP Local Rag for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Kagimcp is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. MCP Local Rag is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kagisearch-kagimcp and nkapila6-mcp-local-rag as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kagimcp has a quality signal of 80/100 (Excellent) with 3 views, 0 installs and 546 GitHub stars. MCP Local Rag has 63/100 (Good) with 3 views, 0 installs and 134 GitHub stars.