Searxng Mul Mcp

Created By
jae-jae9 months ago
A Model Context Protocol (MCP) server for SearXNG search engine with multi-query parallel search support
Overview

What is SearXNG Mul MCP?

SearXNG Mul MCP is a Model Context Protocol (MCP) server designed for integrating with the SearXNG metasearch engine, enabling multi-query parallel searches using both standard input/output and HTTP transport protocols.

How to use SearXNG Mul MCP?

To use SearXNG Mul MCP, you can run it via NPM in either stdio or HTTP mode by setting the required environment variables, including the SearXNG server URL.

Key features of SearXNG Mul MCP?

  • Multi-Query Parallel Search for improved efficiency
  • Dual Transport Support (stdio and HTTP)
  • Direct integration with SearXNG REST API
  • Basic Authentication support for SearXNG servers
  • Docker Deployment for easy containerization
  • Flexible environment configuration management

Use cases of SearXNG Mul MCP?

  1. Executing multiple search queries simultaneously to enhance search efficiency.
  2. Integrating with web-based applications that require search functionalities.
  3. Deploying a private SearXNG instance with secure access.

FAQ from SearXNG Mul MCP?

  • What is the default transport mode?

The default transport mode is stdio, which uses standard input/output for communication.

  • Can I deploy it using Docker?

Yes! SearXNG Mul MCP can be deployed using Docker with a provided docker-compose configuration.

  • What are the prerequisites for development?

You need Node.js 18 or higher, npm or yarn, and TypeScript to develop SearXNG Mul MCP.

Server Config

{
  "mcpServers": {
    "searxng-mul-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "searxng-mul-mcp"
      ],
      "env": {
        "SEARXNG_URL": "https://your.searxng.com",
        "USERNAME": "your_username",
        "PASSWORD": "your_password"
      }
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
jae-jae
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago