syn-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SYN_SEARCH_DEBUG | No | Set to 1 to log to stderr | |
| SYNTHETIC_API_KEY | Yes | Synthetic API key (starts with syn_) | |
| SYN_SEARCH_MAX_BYTES | No | Truncation byte limit | 51200 |
| SYN_SEARCH_MAX_LINES | No | Truncation line limit | 2000 |
| SYN_SEARCH_SUMMARIZER_MODEL | No | Chat model used for ai-summary | syn:small:text |
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 |
|---|---|
| synthetic_searchA | Search the web via Synthetic's Search API. Returns top results with titles, URLs, and text snippets. Use detail_level='ai-summary' (recommended for real questions) to get AI-summarized results with an optional summary_prompt to focus on what matters. Use 'full' for complete text. Output truncated to 2000 lines or 50.0KB; full output saved to a temp file when exceeded. |
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
Only one tool exists, so there is no possibility of selecting the wrong tool for a task. The single tool's purpose is clearly defined as web search.
The single tool name 'synthetic_search' follows a clean verb_noun pattern. With only one tool, there is no conflicting naming convention to introduce confusion.
A server with just one tool feels thin, even for a narrowly scoped search service. However, the tool is substantive and handles multiple detail levels, so it is a borderline case rather than an egregious under-provision.
The tool covers the core search lifecycle well—retrieving results, summaries, and full text. It lacks explicit pagination or advanced filtering options, but the built-in truncation and temp-file output mitigate common gaps.