multsearch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NO_PROXY | No | Comma-separated hosts to bypass proxy (e.g., localhost,127.0.0.1,ark.cn-beijing.volces.com) | |
| HTTP_PROXY | No | HTTP proxy for accessing Tavily/Firecrawl/Gemini (e.g., http://127.0.0.1:7890) | |
| MULT_DEBUG | No | Enable detailed debug logging | false |
| MULT_MODEL | No | LLM model name, can be switched via switch_model tool | glm-5.2 |
| HTTPS_PROXY | No | HTTPS proxy for accessing Tavily/Firecrawl/Gemini | |
| GEMINI_MODEL | No | Gemini model name | gemini-2.5-flash |
| MULT_API_KEY | Yes | Required API key for the LLM provider | |
| MULT_API_URL | No | OpenAI-compatible endpoint (e.g., https://ark.cn-beijing.volces.com/api/plan/v3) | |
| MULT_LOG_DIR | No | Directory for log output | ~/.config/multsearch/logs |
| MULT_PROVIDER | No | Provider: custom or ark (preset by setup wizard) | custom |
| GEMINI_API_KEY | No | Optional Gemini API key for gemini_search (second search path) | |
| MULT_LOG_LEVEL | No | Log level: DEBUG, INFO, WARNING, ERROR | INFO |
| TAVILY_API_KEY | No | Optional Tavily API key for web_search and web_fetch/web_map | |
| MULT_MAX_TOKENS | No | Maximum tokens for LLM responses (e.g., 8192 for reasoning models) | |
| FIRECRAWL_API_KEY | No | Optional Firecrawl API key for web_search and web_fetch fallback |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | |
| get_sourcesB | |
| gemini_searchA | |
| web_fetchA | |
| web_mapA | |
| get_config_infoA | |
| switch_modelA | |
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 7 tools
Each tool has a distinct purpose: configuration, search (two providers), source retrieval, URL fetch, site mapping, and model switching. The two search tools (web_search and gemini_search) overlap in function but descriptions clearly position gemini_search as a cross-validation path, so an agent can disambiguate. Overall boundaries are clear.
Naming mixes verb-first and object-first conventions: get_config_info/get_sources/switch_model are verb_noun, while web_search/web_fetch/web_map/gemini_search are object_verb (or proper-noun_verb). This inconsistency is noticeable but all names are readable and lower_snake_case, so it is not chaotic.
Seven tools is well within the ideal 3–15 range. Each tool covers a distinct capability (config, search, sources, fetch, map, model switch) and none seem redundant or filler.
The surface covers the full workflow: search via two providers, retrieve sources via session_id, fetch single URLs, map website structures, and manage configuration/model. There are no obvious dead ends; the only minor gap might be a way to clear cache, but that is not essential to the core search/fetch/map domain.