mcp-searxng
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARXNG_URL | Yes | The URL of your SearXNG instance. | |
| MCP_HTTP_PORT | No | Port to enable HTTP transport mode. | |
| SEARXNG_HEADERS_BASE64 | No | Base64 encoded JSON object of custom headers to send with search requests. | |
| URL_READER_HEADERS_BASE64 | No | Base64 encoded JSON object of custom headers to send with URL read requests. |
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 | {} |
| logging | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searxng_web_searchA | Performs a web search using the SearXNG API, ideal for general queries, news, articles, and online content. Use this for broad information gathering, recent events, or when you need diverse web sources. |
| web_url_readA | Read the content from an URL. Use this for further information retrieving to understand the content of each URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Server Configuration | Current server configuration and environment variables |
| Usage Guide | How to use the MCP SearXNG server effectively |
TDQS
Scored across 2 tools
Each tool serves a distinct role: one performs web searches and the other reads specific URLs. There is no overlap in functionality, making them easy to distinguish.
The naming pattern is inconsistent: one tool uses the 'searxng_' prefix while the other does not, and the action-object order differs (web_search vs url_read). This mixed convention could confuse an agent.
With only 2 tools, the server feels minimal and is below the typical well-scoped range of 3-15. However, the two tools do cover a basic search-and-read workflow.
The pair covers the core search and content retrieval workflow, which is sufficient for basic information gathering. Minor gaps exist, such as no advanced search options, but these are not critical for a simple search server.