What is the key difference between Nexus and Wet MCP?

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

How do I install Nexus or Wet MCP 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 Nexus and Wet MCP free or paid?

Nexus operates under a BYOK (Pay Provider Direct) model (API Key required). Wet MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Nexus lists 1 tools with 2 views and 23 GitHub stars. Wet MCP lists 6 tools with 1 views and 16 GitHub stars.

Can I use both Nexus and Wet MCP 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

Nexus vs Wet MCP

In-depth architectural comparison of the Nexus and Wet MCP 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

Nexus

Search & Data Extraction · Local stdio

Quality: 61/100 (Good) | Auth: API Key required

Wet MCP

Search & Data Extraction · Local stdio

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

Verdict Summary: Choose Nexus if you need specialized Search & Data Extraction tools running via a local process. Choose Wet MCP 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 Nexus when:

You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: OPENROUTER_API_KEY.
Primary tools included: search.

Explore Nexus Details

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

Feature & Specification Comparison

Specification	Nexus adawalli Search & Data Extraction	Wet MCP n24q02m Search & Data Extraction
Summary	AI-powered web search server using Perplexity Sonar models with source citations. Zero-install setup via NPX.	Web search (embedded SearXNG), content extraction, and library docs indexing with hybrid search (FTS5 + semantic). Built-in Qwen3 embedding, no API keys required.
Category & Scope	Search & Data Extraction

Tools & Capabilities Breakdown

Nexus Tools (1)

The main search tool that provides AI-powered search capabilities.

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

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).

Nexus Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "adawalli-nexus": {
      "command": "bunx",
      "args": [
        "nexus-mcp"
      ],
      "env": {
        "OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE"
      }
    }
  }
}

Wet MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Nexus More alternatives to Wet MCP Search & Data Extraction category hub