What is the key difference between Wet MCP and OmniSeek?

Wet MCP belongs to the Search & Data Extraction category with local stdio execution, while OmniSeek belongs to the Search & Data Extraction category with cloud HTTP/SSE execution.

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

Wet MCP operates under a Free / Open Source model (No auth required). OmniSeek 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 18 GitHub stars. OmniSeek lists 18 tools with 0 views and 74 GitHub stars.

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

In-depth architectural comparison of the Wet MCP and OmniSeek 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: 59/100 (Good) | Auth: No auth required

OmniSeek

Search & Data Extraction · Remote HTTP/SSE

Quality: 55/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 OmniSeek if your workspace requires Search & Data Extraction integration with remote web transport. 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).
Primary tools included: search, extract, media.

Explore Wet MCP Details

Choose OmniSeek when:

You need dedicated capabilities in the Search & Data Extraction domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: omniseek_search, omniseek_read, omniseek_view.

Explore OmniSeek Details

Feature & Specification Comparison

Specification	Wet MCP n24q02m Search & Data Extraction	OmniSeek 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.	Your agent seeks what search can't find. A self-hosted perception MCP server.
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": [
        "wet-mcp"
      ]
    }
  }
}

OmniSeek Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "omniseek": {
      "url": "http://127.0.0.1:8765/mcp"
    }
  }
}

Frequently Asked Questions

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