How do I use Synthetic Search MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Synthetic Search MCP Server search for the latest TypeScript 5.4 features" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Synthetic Search MCP Server

by joephaser

Overview Schema Source Related Servers Score Discussions Admin

JavaScript

Remote

🔍 Synthetic Search MCP Server

Web search capabilities for your MCP-enabled applications with zero-data-retention privacy.

Installation • Usage • Configuration • API Reference

✨ Features

🔒 Privacy First

Zero-data-retention search ensures your queries remain private and secure.

⚡ Fast & Accurate

Get relevant web search results in milliseconds with high-quality ranking.

🔧 Easy Integration

Simple MCP tool interface that works seamlessly with OpenCode and other MCP clients.

📦 Zero Dependencies

Lightweight implementation with minimal external dependencies for reliability.

Related MCP server: DeepSearch MCP

🚀 Installation

Prerequisites

Node.js 20 or higher
A Synthetic API key (Get one here)

Quick Start

# Clone the repository
git clone https://github.com/joephaser/synthetic-search-mcp.git
cd synthetic-search-mcp

# Install dependencies
npm install

# Build the project
npm run build

🎯 Usage

1. Configure Your API Key

# Option 1: Environment variable
export SYNTHETIC_API_KEY="your-api-key-here"

# Option 2: Using .env file
cp .env.example .env
# Edit .env and add your API key

2. Run the Server

# Production mode
npm start

# Development mode with hot reload
npm dev

3. Test It

export SYNTHETIC_API_KEY="your-api-key"
npm test

⚙️ Configuration

Claude Code CLI Integration

Add this MCP server to your Claude Code configuration using the claude mcp add command:

# Add the MCP server with your API key
claude mcp add --transport stdio --env SYNTHETIC_API_KEY=your-api-key-here synthetic-search -- node /path/to/synthetic-search-mcp/dist/index.js

Or manually edit ~/.claude.json and add:

{
  "mcpServers": {
    "synthetic-search": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/synthetic-search-mcp/dist/index.js"],
      "env": {
        "SYNTHETIC_API_KEY": "your-api-key-here"
      }
    }
  }
}

Note: Replace /path/to/synthetic-search-mcp with the actual path to your installation and your-api-key-here with your Synthetic API key.

OpenCode Integration

Add this MCP server to your OpenCode configuration at ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "synthetic-search": {
      "type": "local",
      "command": ["node", "/path/to/synthetic-search-mcp/dist/index.js"],
      "environment": {
        "SYNTHETIC_API_KEY": "your-api-key-here"
      },
      "enabled": true
    }
  }
}

Note: Replace /path/to/synthetic-search-mcp with the actual path to your installation and your-api-key-here with your Synthetic API key.

📚 API Reference

Tool: `synthetic_search`

Search the web using Synthetic's privacy-focused search API.

Parameters

Parameter	Type	Required	Description
`query`	`string`	✅ Yes	The search query to execute

Example Request

{
  "query": "latest TypeScript features 2024"
}

Response Format

{
  "results": [
    {
      "title": "What's New in TypeScript 5.4",
      "url": "https://example.com/article",
      "date": "2024-03-15",
      "snippet": "TypeScript 5.4 introduces several exciting features..."
    }
  ]
}

Result Fields

Title - The page title
URL - Direct link to the source
Date - Publication date (when available)
Snippet - Relevant excerpt from the content

🛠️ Development

# Run in development mode
npm run dev

# Build for production
npm run build

# Run linting
npm run lint

# Run tests
npm test

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

Made with ❤️ for the MCP community

Report Bug • Request Feature

Available Tools

1 tool

synthetic_searchA

Search the web using Synthetic's zero-data-retention search API. Returns relevant web results including URL, title, snippet text, and publication date.

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	The search query to execute

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden and discloses key behavioral traits: it specifies the API type ('zero-data-retention search API') and return format ('URL, title, snippet text, and publication date'). However, it doesn't mention rate limits, authentication needs, or error handling, leaving some gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, with two sentences that efficiently convey purpose and output without wasted words. Every sentence adds value, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is fairly complete, covering purpose, API context, and return values. However, it could improve by addressing behavioral aspects like rate limits or error cases, slightly reducing completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the 'query' parameter. The description adds no additional meaning beyond what the schema provides, such as query formatting or examples, resulting in a baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Search the web') and resource ('using Synthetic's zero-data-retention search API'), with no siblings to differentiate from. It precisely communicates what the tool does without being vague or tautological.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for web searches but provides no explicit guidance on when to use this tool versus alternatives (e.g., other search methods or APIs). With no siblings, it doesn't need sibling differentiation, but lacks context on exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

1 tool updatev1.0.0Feb 13, 2026
- First observedsynthetic_search

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0

Scored 2026-04-17 22:55 across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

The single tool name follows a consistent snake_case pattern, and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and appropriate for its function.

Tool Count2/5

A single tool is generally too few for a server's purpose, as it limits functionality and suggests an incomplete or overly narrow scope. For a search server, one tool might suffice for basic searches, but it lacks operations like filtering, pagination, or advanced queries that would enhance utility.

Completeness3/5

The tool provides a core search function, but there are notable gaps such as no options for refining searches (e.g., by date, domain, or language) or handling search metadata. It covers the basic operation but lacks features that would make the surface more robust and versatile for agents.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

pixserp A
com.pixserp
Live AI-native web search with citations. One tool for every MCP client. Flat per-request pricing.
Search Browser Automation
12
qsearch A
io.github.theYahia
Multi-engine search for AI agents. Trust scoring, local corpus, MCP-native. Self-hostable, BYOK.
Search RAG Systems
22
MESSORA A
dev.messora
Scrape, crawl and search the web for AI agents via MCP.
Web Scraping Browser Automation Search
51
seltz-ai-seltz-mcpOAuth
ai.seltz
Provides AI assistants with access to Seltz's powerful Web Search capabilities.
Search Browser Automation Web Scraping
2

Related MCP Servers

Google Search MCP Server
Web Scraping Browser Automation Search
Claw256
A
license
Not graded
quality
Not graded
maintenance
Provides Google search capabilities, web content extraction, and screenshot functionality with advanced bot detection avoidance through the MCP protocol.
Updated 2 years ago (2025-02-05 05:53 UTC)
22
6
-
DeepSearch MCP
Search Browser Automation RAG Systems
yuemingruoan
A
license
B
quality
C
maintenance
Enables web search and site-specific search capabilities through the Deepsearch model. Provides unified access to broad web retrieval and targeted site search functionality within the MCP ecosystem.
Updated 10 months ago (2025-11-08 02:12 UTC)
2
8
5
Apache 2.0
Parallel Search MCP
Browser Automation RAG Systems Search
parallel-web
A
license
Not graded
quality
B
maintenance
Free web search and page fetching for AI agents. No account or API key required. Connect to https://search.parallel.ai/mcp over Streamable HTTP. Tools: web_search and web_fetch. Free-tier rate limits apply.
Updated 11 hours ago (2026-09-08 22:15 UTC)
15
MIT
Deep Search MCP Server
Search Browser Automation Web Scraping
LikhonSheikh404
F
license
Not graded
quality
D
maintenance
Provides comprehensive search capabilities including web search, content extraction, news search, academic search, and AI-powered multi-source research. Enables natural language access to web content and research through a production-ready MCP server.
Updated 9 months ago (2025-12-05 06:02 UTC)
-

Appeared in Searches

A server for general search queries

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/joephaser/synthetic-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

🔍 Synthetic Search MCP Server

✨ Features

🔒 Privacy First

⚡ Fast & Accurate

🔧 Easy Integration

📦 Zero Dependencies

🚀 Installation

Prerequisites

Quick Start

🎯 Usage

1. Configure Your API Key

2. Run the Server

3. Test It

⚙️ Configuration

Claude Code CLI Integration

OpenCode Integration

📚 API Reference

Tool: synthetic_search

Parameters

Example Request

Response Format

Result Fields

🛠️ Development

📄 License

Available Tools

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Google Search MCP Server

DeepSearch MCP

Parallel Search MCP

Deep Search MCP Server

Appeared in Searches

Latest Blog Posts

MCP directory API

Tool: `synthetic_search`