agentic mode, which returns more concise results than the default one-shot mode.
The Search MCP comprises two tools:
- web_search - Search the web for information and retrieve relevant results
- web_fetch - Extract and retrieve content from specific URLs
Use Cases
The Search MCP is suited for any application where real-world information is needed as part of an AI agent’s reasoning loop. Common use cases include:- Real-time fact checking and verification during conversations
- Gathering current information to answer user questions
- Researching topics that require recent or live data
- Retrieving content from specific URLs to analyze or summarize
- Competitive intelligence and market research
Installation
The Search MCP can be installed in any MCP client. The server URL is:https://search-mcp.parallel.ai/mcp
The Search MCP can also be used programmatically by providing your Parallel API key in the Authorization header as a Bearer token.
Cursor
Add to~/.cursor/mcp.json or .cursor/mcp.json (project-specific):
VS Code
Add tosettings.json in VS Code:
Claude Desktop / Claude.ai
Go to Settings → Connectors → Add Custom Connector, and fill in:Claude Code
Run this command in your terminal:Windsurf
Add to~/.codeium/windsurf/mcp_config.json:
Cline
Go to MCP Servers → Remote Servers → Edit Configuration:Gemini CLI
Add to~/.gemini/settings.json:
ChatGPT
WARNING: Please note that Developer Mode must be enabled, and this feature may not be available to everyone. Additionally, MCPs in ChatGPT are experimental and may not work reliably. First, go to Settings → Connectors → Advanced Settings, and turn on Developer Mode. Then, in connector settings, click Create and fill in:OpenAI Codex CLI
Add to~/.codex/config.toml:
Amp
Run this command in your terminal:Kiro
Add to.kiro/settings/mcp.json (workspace) or ~/.kiro/settings/mcp.json (global):
Google Antigravity
In the Antigravity Agent pane, click the menu (⋮) → MCP Servers → Manage MCP Servers → View raw config, then add:Best practices
Filtering by date or domain
To filter search results by date or domain, include these constraints directly in your search query or objective rather than expecting separate parameters. For example:- “Latest AI research papers from 2025”
- “News about climate change from nytimes.com”
- “Product announcements from apple.com in the last month”
We have experimented with adding dedicated date and domain parameters to the Search MCP tools, but found they harm quality overall—LLMs tend to overuse them, which overconstrains search results.
Troubleshooting
Common Installation Issues
Cline: 'Authorization Error redirect_uri must be https'
Cline: 'Authorization Error redirect_uri must be https'
Gemini CLI: Where to provide API key
Gemini CLI: Where to provide API key
Gemini CLI uses HTTP MCPs and authenticates via OAuth. If OAuth isn’t working, you can provide your API key directly.Solution: Use environment variables or the Add this to
mcp-remote proxy:~/.gemini/settings.json and replace YOUR-PARALLEL-API-KEY with your key from platform.parallel.ai.VS Code: Incorrect configuration format
VS Code: Incorrect configuration format
VS Code requires a specific configuration format. Common mistakes include using the wrong property names.Incorrect (Cursor format):Correct (VS Code format):Note: VS Code uses
mcp.servers (not mcpServers) and requires the type: "http" field.Windsurf: Configuration location and format
Windsurf: Configuration location and format
Windsurf uses a different configuration format than Cursor.Correct Windsurf configuration:Note: Windsurf uses
serverUrl instead of url. Add this to your Windsurf MCP configuration file.Connection timeout or 'server unavailable' errors
Connection timeout or 'server unavailable' errors
Tools not appearing in the IDE
Tools not appearing in the IDE
If the MCP installs but tools don’t show up:
- Restart your IDE completely (not just reload)
- Check configuration syntax: Ensure valid JSON with no trailing commas
- Verify the server URL: Must be exactly
https://search-mcp.parallel.ai/mcp - Check IDE logs: Look for MCP-related errors in your IDE’s output/debug panel