SearXNG-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP transport | 3000 |
| SEARXNG_URL | No | URL of your SearXNG instance | http://localhost:8080 |
| TRANSPORT_MODE | No | Transport mode: http or stdio | http |
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 |
|---|---|
| get_enginesA | Get all available search engines supported by the SearXNG instance |
| searchC | Search the web using SearXNG metasearch engine. NOTE: You may need to run twice, as the result of the first run may not be dependable. |
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, get_engines and search, have completely distinct purposes. One retrieves available engines, the other performs searches, leaving no ambiguity.
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.
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.
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.