MCP MixSearch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Server host address | localhost |
| MCP_ONLY | No | Run in MCP-only mode (true) or include REST API (false) | |
| MCP_PORT | No | Server port number | 3000 |
| LOG_LEVEL | No | Logging level | INFO |
| BRAVE_API_KEY | No | Your Brave API key for web search | |
| MCP_TRANSPORT | No | Transport mode: 'stdio' or 'http' | stdio |
| MCP_AUTH_ENABLED | No | Enable authentication | true |
| MCP_CORS_ORIGINS | No | Comma-separated list of allowed CORS origins | http://localhost:3000,http://localhost:5173 |
| MAX_CONTENT_LENGTH | No | Maximum content length for extraction | 500000 |
| MAX_CONCURRENT_REQUESTS | No | Maximum number of concurrent requests | 5 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| full_web_searchA | Get comprehensive web search results with full page content extraction. Use this when you need detailed content from web sources for comprehensive research and analysis. This searches the web and extracts the full content from each result page. Use this for comprehensive research or detailed information from web sources. Args: query: Search query string (1-200 characters) limit: Number of results to return with full content (1-10, default 5) include_content: Whether to extract full page content (default true) max_content_length: Maximum characters per result content (0 = no limit) top_n: Alternative name for limit (for compatibility) recency_days: Days to look back for recent content (time filtering) source: Content type filter ("news", "images", "videos", etc.) language: Language filter (e.g., "en", "es", "fr", "de") country: Geographic filter (e.g., "US", "GB", "FR", "DE") Returns: Formatted text containing search results with full extracted content Parameter Usage Guidelinesquery (required)
limit (optional, default 5)
include_content (optional, default true)
max_content_length (optional, default unlimited)
top_n (optional, compatibility parameter)
recency_days (optional, time filtering)
source (optional, content type filtering)
language (optional, language filtering)
country (optional, geographic filtering)
Usage ExamplesBasic search with default settings:Quick overview (smaller limit):Recent news search with time filtering:Geographic and language filtering:Comprehensive research with all parameters:Content type specific search:Source identification only:When to Use This
Related Functionality
|
| get_web_search_summariesA | Get lightweight web search results with only result summaries. Use this when you need a quick overview of available sources without full content. This gets search result titles, URLs, and descriptions for quick research or when you only need an overview of available information. Use this when you want to quickly understand what information is available on a topic before diving deeper with full content extraction. Args: query: Search query string (1-200 characters) limit: Number of search result summaries to return (1-10, default 5) top_n: Alternative name for limit (for compatibility) recency_days: Days to look back for recent content (time filtering) source: Content type filter ("news", "images", "videos", etc.) language: Language filter (e.g., "en", "es", "fr", "de") country: Geographic filter (e.g., "US", "GB", "FR", "DE") Returns: Formatted text containing search result summaries (title, URL, description) Parameter Usage Guidelinesquery (required)
limit (optional, default 5)
Usage ExamplesBasic topic exploration:Quick source discovery:Recent news exploration:Geographic research:Content type discovery:Complete parameter example:When to Choose This ToolPrimary Decision Criteria:
Decision Matrix: When to Use Each ToolUse |
| get_single_web_page_contentA | Extract and return the full content from a single web page URL. Use this when you have a specific URL and need the full text content for analysis or reference. Args: url: The URL of the web page to extract content from max_content_length: Maximum characters for the extracted content (0 = no limit) Returns: Formatted text containing the extracted page content with word count Parameter Usage Guidelinesurl (required)
max_content_length (optional, default unlimited)
Usage ExamplesBasic content extraction:Extract with content limit:Extract documentation:Extract complete article:Complete parameter example:When to Choose This Tool
Error Handling
Alternative Tools
|
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 3 tools
The three tools have clearly distinct purposes with no overlap: full_web_search for comprehensive search with content extraction, get_web_search_summaries for lightweight result overviews, and get_single_web_page_content for extracting content from specific URLs. The descriptions explicitly differentiate their use cases, and the decision matrix helps agents choose appropriately.
All tool names follow a consistent snake_case pattern with clear verb_noun structure: full_web_search, get_web_search_summaries, and get_single_web_page_content. The naming is predictable and readable, with 'get' and 'full' prefixes appropriately indicating scope differences.
Three tools is well-scoped for a web search and content extraction server. Each tool earns its place by covering distinct workflow stages: discovery (summaries), comprehensive search (full), and targeted extraction (single page). This minimal set effectively covers the domain without bloat.
The tool set provides complete coverage for web search and content extraction workflows. It supports discovery (summaries), in-depth research (full search with extraction), and follow-up on specific URLs (single page). The descriptions explicitly outline complementary use cases, leaving no obvious gaps for agents.