Skip to main content
Glama
BrandonStudio

SearXNG-MCP

by BrandonStudio
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

SearXNG-MCP

A Model Context Protocol (MCP) server that provides a bridge between AI assistants and SearXNG, a privacy-respecting metasearch engine.

Features

  • Search Tool: Perform web searches through SearXNG with full support for:

    • Multiple search categories (general, images, videos, news, music, files, etc.)

    • Specific engine selection

    • Language filtering

    • Pagination

    • Time range filtering

    • Safe search settings

  • Engine Discovery: List all available search engines supported by your SearXNG instance

  • Transport Support:

Related MCP server: OneSearch MCP Server

Prerequisites

You should enable JSON model in your SearXNG instance. Locate the search.formats configuration in your settings.yml and includes json:

search:
  formats:
    - html
    - json

Configuration

The server can be configured using environment variables:

Variable

Description

Default

SEARXNG_URL

URL of your SearXNG instance

http://localhost:8080

PORT

Port for HTTP transport

3000

TRANSPORT_MODE

Transport mode: http or stdio

http

Usage

HTTP Transport (Streamable HTTP)

# Start the server
TRANSPORT_MODE=http SEARXNG_URL=https://your-searxng-instance.com npm start

# The server will listen on http://localhost:3000/mcp

Stdio Transport

# Start with stdio transport
SEARXNG_URL=https://your-searxng-instance.com npm start

MCP Client Configuration

For Claude Desktop or other MCP-compatible clients, add to your configuration:

{
  "mcpServers": {
    "searxng": {
      "command": "npx",
      "args": [
        "-y",
        "@bs-mcps/searxng"
      ],
      "env": {
        "SEARXNG_URL": "https://your-searxng-instance.com",
      }
    }
  }
}

Cloudflare Worker Transport

You can deploy the MCP server as a Cloudflare Worker.

To deploy, you can fork this repository and then create a new Worker linked to your fork.

Or, you can simply click the button below to deploy directly to Cloudflare:
Deploy to Cloudflare

Required Environment Variables

Variable

Description

SEARXNG_URL

URL of your SearXNG instance

Available Tools

Tool

Description

search

Perform a web search using SearXNG

get_engines

Get all available search engines supported by the SearXNG instance

search

Perform a web search using SearXNG.

Parameters:

  • query (required): The search query

  • categories: Array of categories (e.g., ["general", "images"])

  • engines: Array of specific engines (e.g., ["google", "duckduckgo"])

  • language: Language code (e.g., "en")

  • pageno: Page number for pagination

  • time_range: Time filter ("day", "week", "month", "year")

  • safesearch: Safe search level (0, 1, 2)

get_engines

Get all available search engines supported by the SearXNG instance.

No parameters required.

Copyright Notice

Copyright 2025-2026 BrandonStudio

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Available Tools

2 tools
get_enginesGet EnginesA

Get all available search engines supported by the SearXNG instance

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description does not disclose behavioral traits beyond the implied read-only list operation. It does not explicitly state lack of side effects or authentication requirements, but for a simple list, minimal disclosure is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words. It is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description only says 'search engines' without specifying what attributes are returned (e.g., names, status). A bit more detail would improve completeness for an agent needing to process the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, so schema coverage is 100%. The description adds no parameter details, but none are needed. The baseline for zero parameters is high, and this is adequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies the verb 'get' and the resource 'all available search engines supported by the SearXNG instance', distinguishing it from the sibling tool 'search' which likely performs queries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While no explicit when-to-use or when-not-to-use is given, the purpose is distinct from the only sibling 'search', making it clear that this tool lists engines and the other searches. Some implicit guidance exists.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv0.4.0-dev.2
    • First observedget_engines
    • First observedsearch
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0
Disambiguation5/5

The two tools, get_engines and search, have completely distinct purposes. One retrieves available engines, the other performs searches, leaving no ambiguity.

Naming Consistency5/5

Both tool names follow a verb_noun pattern (get_engines, search) with clear, imperative verbs. The pattern is consistent even though search is a single verb.

Tool Count3/5

Two tools is on the lower end for a search engine server. While the core functionality (search and list engines) is covered, the count feels minimal but not unreasonable for a focused tool.

Completeness3/5

The tools cover basic search and engine listing, but lack features like filtering results, engine configuration, or advanced search parameters. The note about running twice suggests potential reliability issues, indicating minor gaps.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BrandonStudio/SearXNG-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server