What is the key difference between Wet MCP and MCP Local Rag?

Wet MCP belongs to the Search & Data Extraction category with local stdio execution, while MCP Local Rag belongs to the Search & Data Extraction category with local stdio execution.

How do I install Wet MCP or MCP Local Rag in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Wet MCP and MCP Local Rag free or paid?

Wet MCP operates under a Free / Open Source model (No auth required). MCP Local Rag operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Wet MCP lists 6 tools with 1 views and 16 GitHub stars. MCP Local Rag lists 6 tools with 2 views and 133 GitHub stars.

Can I use both Wet MCP and MCP Local Rag together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Wet MCP vs MCP Local Rag

In-depth architectural comparison of the Wet MCP and MCP Local Rag MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Wet MCP

Search & Data Extraction · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

MCP Local Rag

Search & Data Extraction · Local stdio

Quality: 53/100 (Good) | Auth: No auth required

Verdict Summary: Choose Wet MCP if you need specialized Search & Data Extraction tools running via a local process. Choose MCP Local Rag if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Wet MCP when:

You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: WET_MCP_CONFIG.
Primary tools included: search, extract, media.

Explore Wet MCP Details

Choose MCP Local Rag when:

You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Multi-engine search across 9+ backends, Multi-topic deep research, Semantic similarity ranking.

Explore MCP Local Rag Details

Feature & Specification Comparison

Specification	Wet MCP n24q02m Search & Data Extraction	MCP Local Rag nkapila6 Search & Data Extraction
Summary	Web search (embedded SearXNG), content extraction, and library docs indexing with hybrid search (FTS5 + semantic). Built-in Qwen3 embedding, no API keys required.	"primitive" RAG-like web search model context protocol (MCP) server that runs locally. No APIs needed.
Category & Scope	Search & Data Extraction

Tools & Capabilities Breakdown

Wet MCP Tools (6)

Web (SearXNG metasearch), news, images, academic research (Scholar / arXiv / PubMed / CrossRef / Semantic Scholar / BASE), library docs (HyDE + FTS5), find similar pages. Includes `docs_resolve` (library name -> ranked id), `docs_query` (version-aware + topic + 5000-token cap), `docs_lock_project`…

extract

URL -> smart chunks dict (`clean_text` + `markdown` + `structured_data` + `code_blocks` + `metadata`) via web-core 5-strategy chain. Batch processing (up to 50 URLs), deep crawling, site mapping, local file conversion (PDF/DOCX/XLSX/PPTX/EPUB), structured extraction (JSON Schema)

media

list` (discover URLs from gallery pages), `download` (SSRF-safe). `analyze` was removed in v2.0.0 -- use `imagine-mcp.understand` instead

config

status`, `set`, `cache_clear`, `docs_reindex`, `warmup`, `setup_sync`, `setup_status`, `setup_skip`, `setup_reset`, `setup_complete

help

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Wet MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "n24q02m-wet-mcp": {
      "command": "uvx",
      "args": [
        "invocation"
      ],
      "env": {
        "WET_MCP_CONFIG": "YOUR_WET_MCP_CONFIG_HERE"
      }
    }
  }
}

MCP Local Rag Configuration

mcpServers (Claude Desktop / Cursor)

{
  "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

Wet MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, MCP Local Rag belongs to Search & Data Extraction using local stdio subprocess. Select Wet MCP when you need capabilities focused on search & data extraction and MCP Local Rag when you require tools for search & data extraction.

More alternatives to Wet MCP More alternatives to MCP Local Rag Search & Data Extraction category hub