Which AI clients can use the Parallel Search MCP server?

27 AI clients, including Cursor, VS Code, and Claude. Each connects to Parallel Search as a remote MCP server through Runlayer, which adds identity, policy, scanning, and audit to every call.

Which Parallel Search tools are available?

Parallel Search exposes 2 tools, including Web fetch, Web Search preview. Admins choose which ones each group can call.

How does Parallel Search authenticate?

Sign in the way Parallel Search requires. Runlayer holds the credentials so they stay out of the client’s configuration.

Integrations / MCP servers

Parallel Search

Search the web and fetch pages with Parallel's low-latency search built for agents.

Book a demo View documentation

Tools

2 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

Search 2 tools

Web fetch
Tool name: web_fetch
Purpose: Fetch and extract relevant content from specific web URLs.
Web Search preview
Tool name: web_search_preview
Purpose: Perform web searches and return results in an LLM-friendly format and with parameters tuned for LLMs.

Compatibility

Connect Parallel Search to the clients your teams already use

27 AI clients can connect to Parallel Search through Runlayer. Pick one for its setup steps and controls.

Why Runlayer

Why connect Parallel Search through Runlayer?

One approved path

Approve Parallel Search once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.