SearXNG Control Plane MCP Server
This server provides MCP tools to manage and monitor a SearXNG search instance, including configuration inspection, search engine toggling, health checking, and container restart.
Inspect Settings (
inspect_settings): Read and parsesettings.ymlto view current configuration and list enabled/disabled engines.Enable/Disable Engines (
enable_engine,disable_engine): Turn specific search engines on or off.Set Engine Status (
set_engine_status): Explicitly set an engine's state to enabled or disabled in one call.Test API Health (
test_search_api_health): Send a test query to the search API and check response status, latency, and payload.Restart Container (
restart_searxng_container): Restart the SearXNG Docker container to apply changes or recover.
Manages SearXNG instances by inspecting configuration settings, toggling search engines, testing search API health, and restarting the SearXNG container.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SearXNG Control Plane MCP Server check the health of the search API"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SearXNG Control Plane MCP Server
An Model Context Protocol (MCP) server for managing SearXNG instances, configuration settings, search engine states, API health checking, and container lifecycle.
This repository is part of the TheNovaNodes Antigravity Agent Ecosystem. It provides standard MCP tools to interface securely and reliably with SearXNG, empowering ecosystem agents to inspect settings, toggle search engines dynamically, and monitor service health.
Features
Inspect Settings: Read and parse SearXNG configuration settings (
settings.yml), listing active/disabled engines and configuration parameters.Enable/Disable Search Engines: Toggle individual search engines on or off directly within
settings.yml.Health Testing: Test search API health by sending query requests and verifying HTTP response codes, latency, and JSON result payloads.
Container Control: Restart the SearXNG Docker container (
searxng-app) via subprocess.
Related MCP server: SearXNG MCP Server
Configuration
Environment variables can be used to override default settings:
Variable | Default Value | Description |
|
| Path to SearXNG |
|
| Base URL of SearXNG instance |
|
| Name of the Docker container running SearXNG |
Installation & Setup
pip install -e .Available MCP Tools
inspect_settings: Inspect current SearXNG configuration settings and list enabled/disabled search engines.enable_engine: Enable a specific search engine insettings.yml.disable_engine: Disable a specific search engine insettings.yml.set_engine_status: Set explicit enabled/disabled state for a search engine insettings.yml.test_search_api_health: Perform a health check query against the SearXNG search endpoint.restart_searxng_container: Restart the SearXNG Docker container via subprocess.
Ecosystem Context
As a part of the TheNovaNodes ecosystem, this project adheres to high-quality standards and ensures robustness for integrations with other Antigravity agents.
License
MIT
Available Tools
6 toolsdisable_engineB
Disable a specific search engine in SearXNG settings.yml.
Args: engine_name: Name of the engine to disable (e.g. 'duckduckgo'). settings_path: Optional path to settings.yml.
Inputs: engine_name (required), settings_path. Returns: result
enable_engineB
Enable a specific search engine in SearXNG settings.yml.
Args: engine_name: Name of the engine to enable (e.g. 'duckduckgo'). settings_path: Optional path to settings.yml.
Inputs: engine_name (required), settings_path. Returns: result
inspect_settingsA
Inspect SearXNG configuration settings and active/disabled engines from settings.yml.
Args: settings_path: Optional path to settings.yml. Defaults to SEARXNG_SETTINGS_PATH.
Inputs: settings_path. Returns: result
restart_searxng_containerA
Restart the SearXNG Docker container via subprocess.
Args: container_name: Name of the docker container (defaults to SEARXNG_CONTAINER_NAME).
Inputs: container_name. Returns: result
set_engine_statusA
Enable or disable a search engine in settings.yml.
Args: engine_name: Name of the engine (e.g. 'google cse', 'duckduckgo', 'bing'). enabled: True to enable the engine, False to disable it. settings_path: Optional path to settings.yml. Defaults to SEARXNG_SETTINGS_PATH.
Inputs: enabled (required), engine_name (required), settings_path. Returns: result
test_search_api_healthA
Test SearXNG Search API health by issuing a test query and measuring latency.
Args: url: Base URL or search endpoint of SearXNG instance (defaults to SEARXNG_URL). query: Test search query string (defaults to 'healthcheck').
Inputs: url, query. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
The three engine control tools (set_engine_status, enable_engine, disable_engine) heavily overlap, with set_engine_status effectively combining the other two. This creates ambiguity about which tool to use for enabling/disabling an engine. The remaining tools are distinct but the redundancy lowers the overall clarity.
All tool names follow a consistent verb_noun pattern with snake_case (inspect_settings, set_engine_status, enable_engine, disable_engine, test_search_api_health, restart_searxng_container). The only inconsistency is that set_engine_status and enable/disable_engine represent overlapping actions, but the naming convention itself is uniform.
With six tools, the server is well-scoped for a control plane managing a SearXNG instance. Each tool covers a distinct area (settings inspection, engine status modification, health testing, container restart) without unnecessary bloat, making the count appropriate.
The surface covers core operations like inspecting settings, toggling engines, testing health, and restarting. However, it lacks lifecycle operations such as starting, stopping, or getting the container status, and there's no direct 'apply config' action. These gaps are notable for a control plane but not fatal.
Related MCP Connectors
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Search a directory of 800+ open-source MCP servers: find, compare and get install configs.
An MCP server for the STRG.com s3-compatible object storage network for all management operations. Full documentation access, ask questions, create buckets, configure scoped access keys, CORS rules, lifecycle policies and perform any S3 operation.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server for connecting agentic systems to search systems via searXNG.1132MIT
- AlicenseAqualityDmaintenanceAn MCP server that allows searching through public SearXNG instances by parsing HTML content into JSON results, enabling metasearch capabilities without requiring JSON API access.173 npm57MIT
- AlicenseAqualityCmaintenanceSelf-contained SearXNG MCP server in Docker. Aggregates 200+ search engines across 30+ categories with multi-page fanout, autocomplete, and engine discovery. Dual transport (HTTP + stdio), API key auth, and built-in Web UI reverse proxy.311MIT
- AlicenseAqualityDmaintenanceAn MCP server that integrates the SearXNG API for web search and URL content extraction with advanced features like pagination, caching, and proxy support.417,815 npm2MIT