Parallel Search

What the Parallel Search connector does

The Parallel Search MCP server gives an AI agent live web search and page extraction. It exposes two read-only tools built on Parallel's Search and Extract APIs, and answers anonymously with no API key. Use it when your client has no built-in browsing, or when you want search you can point at chosen domains and modes.

Parallel Search tools (2)

• web_searchRead-only

  Purpose: Perform web searches and return LLM-friendly results, including excerpts that are usually sufficient to answer directly without a follow-up fetch. Ideal Use Cases: - Answering questions that require fresh or current information - Research, comparison, documentation, and troubleshooting questions - Broad tasks where multiple `search_queries` can be issued in a single call

• web_fetchRead-only

  Purpose: Fetch and extract relevant content from specific web URLs. Use only when web_search excerpts are insufficient for the task at hand. Ideal Use Cases: - The user asked about a specific URL or page - You need exact wording or quotes that excerpts may have truncated - You need full-page analysis (long article, document, or page structure) - web_search excerpts are conflicting or clearly insufficient to answer

Read from the server on 2026-09-08, including each tool's own safety annotations.

Limits

• It reads the web; it writes nothing. Both tools are annotated read-only and non-destructive by the server. There is no write path on this surface at all.
• Everything it returns is untrusted third-party content. Both tools declare openWorldHint: true — the server's own statement that results come from an open-ended external source. Any text on a fetched page can reach your model, including text shaped like instructions. Treat results as data, never as directives, and keep the connector away from agents holding credentials or write access. Parallel's MCP page carries no security or prompt-injection section.
• Anonymous use is deliberately constrained. Parallel describes the free tier as having lower rate limits, running in fast mode with server-managed settings, and silently ignoring every connection-level override. A misconfigured anonymous client does not error — it just gets defaults.
• The "token-efficient search" claim is Parallel's, not our measurement. It is Parallel's own description in Anthropic's directory listing and its documentation. What we can point at is the mechanism behind it: a documented cap of roughly 25,000 characters of excerpts per tool call, and an excerpt-first default on web_fetch. We ran no token benchmark.
• Rate limits are published for the APIs, not for anonymous MCP. Parallel documents 600 requests per minute each for its Search and Extract endpoints. It publishes no anonymous MCP figure, and we did not probe for one — finding a rate limit means deliberately exceeding it.
• turbo mode is narrower than the others. Parallel states that turbo currently supports English and Japanese queries only, and that domain and path filters are unsupported in it.
• Commercial terms are reported by reference only. Parallel publishes per-mode Search pricing and a per-URL Extract rate on its pricing page. Pricing changes without notice and we make no claim about what any tier costs — read it from Parallel.
• Results depend on Parallel's retrieval, not the whole web. Absence from a result set is not evidence a page does not exist.
• We did not exercise either tool. Our check was a read-only handshake. Every behavioural claim above comes from the server's own tool descriptions and schemas or from Parallel's documentation.

Frequently asked questions

Sources

• Parallel Docs, "Search MCP" (retrieved 2026-09-08, HTTP 200, served as clean Markdown by appending .md to the page URL). This is the exact documentation value in Anthropic's directory entry. Source for both endpoints, the free-tier posture, the 25,000-character excerpt cap, the per-call parameter tables, the connection-level override mechanism and validation behaviour, the per-client setup instructions and the troubleshooting section. · retrieved 2026-09-08
• Parallel Docs, "Search Modes" (retrieved 2026-09-08, HTTP 200). The four modes with their stated latencies, the advanced default for the API, and turbo's English/Japanese language limitation. · retrieved 2026-09-08
• Parallel Docs, "API Rate Limits" (retrieved 2026-09-08, HTTP 200). The 600-per-minute quotas for Search and Extract, and the instruction to contact support for higher limits. · retrieved 2026-09-08
• Parallel Docs, "Parallel API Pricing" (retrieved 2026-09-08, HTTP 200). Consulted; cited by reference only, with no figure restated as our own claim. · retrieved 2026-09-08
• Parallel documentation machine index (retrieved 2026-09-08, HTTP 200). Used to resolve real page slugs rather than guessing them. · retrieved 2026-09-08
• Live tools/list handshake against https://search.parallel.ai/mcp — two tools with full descriptions, input schemas, output schemas and all three safety annotations, answered anonymously with no credential and no authentication challenge (2026-09-08). Schema committed at docs/marketing/data/tool-schemas/parallel-search.tools.json. · retrieved 2026-09-08
• Anthropic Connectors Directory entry — . Tier, category, endpoint, transport, author and both listed tool names, read from our committed directory snapshot dated 2026-09-08. The directory's auth_posture of no_auth agrees with what we observed. · retrieved 2026-09-08
• Parallel support — <support@parallel.ai> · Privacy