SearXNG MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARXNG_URL | No | The URL of the SearXNG instance. Defaults to http://192.168.1.44:55001 | http://192.168.1.44:55001 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web using SearXNG. Returns up to 10 relevant results with titles, URLs, snippets, and metadata. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'web_search' follows a clear verb_noun pattern.
A single tool for a web search server feels thin and limited in scope. While it covers the core search functionality, it lacks additional features like filtering, advanced queries, or result management that might be expected in a more complete search interface.
The server provides only basic search functionality without any supporting operations. There are significant gaps, such as no ability to refine searches, handle pagination, or access search history, making the surface incomplete for robust web search tasks.