LabscoMCP early access ↗
MCP SERVER · OFFICIAL PROJECT

Parallel Web Search

Two tools — search and fetch — usable with no key, plus a separate authenticated endpoint for deep research.

by Parallel ↗Web Search Engines✓ Official

LABSCO SUMMARY

Both tools take an objective, not just a query — which is what makes the excerpts worth reading.

Passing what you are trying to find out, alongside the search terms, lets the server select excerpts against the goal rather than against keyword overlap. That is the difference between a snippet that happens to contain the word and one that answers the question. Splitting fast search from authenticated deep research is the other sensible division: the cheap path stays open and anonymous.

What it is

Parallel publishes two endpoints. The search one lists two tools without credentials; a separate Task endpoint handles deep research and enrichment and always needs credentials.

What you get

  • web_search — low-latency search returning LLM-friendly results with excerpts, guided by a stated objective
  • web_fetch — extract content from specific URLs, documented as a follow-up for when search excerpts are not enough
  • On the Task endpoint: createDeepResearch, createTaskGroup, getStatus, getResultMarkdown

Requirements

Nothing for search; an API key as a Bearer token raises the rate limits. To sign in with OAuth instead, use the separate address https://search.parallel.ai/mcp-oauth, which refuses anonymous requests. The Task endpoint needs an API key or OAuth. One-click install links exist for Cursor, VS Code, LM Studio and Goose.

Setup effort

Paste a URL — add the endpoint to your client