searxng-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARXNG_URL | Yes | Base URL of your SearXNG instance, e.g. http://localhost:8888. | |
| SEARXNG_TIMEOUT_MS | No | Request timeout in milliseconds. | 10000 |
| SEARXNG_MAX_RESULTS | No | Default maximum number of results, clamped to 1-50. | 20 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searxng_web_searchB | Search the web through a SearXNG instance. Returns ranked results, instant answers, and query suggestions. |
| searxng_suggestC | Get search query autocomplete suggestions from the SearXNG instance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one performs web searches, the other provides autocomplete suggestions. There is no overlap or ambiguity.
Both names follow a consistent pattern: searxng_<action> (searxng_web_search and searxng_suggest). The naming is predictable and readable.
With only 2 tools, the surface is thin for a search server. While each tool earns its place, the lack of additional features like pagination or site-specific search makes it borderline.
The tools cover basic search and suggestions but miss common operations like advanced search parameters, result filtering, or pagination. This is a notable gap for a search-oriented server.