Claude Parallel Search connectorWhat Claude can look up on the web through Parallel.
The Claude Parallel Search connector exposes 2 tools, both of them read tools. 2 search or read web pages, 0 write, 0 are undocumented. Below: what Claude brings back, why no account is involved, and where anonymous access tops out.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when you need fresh information
Parallel Search doesn't plug into any account of yours: it gives Claude web search and the ability to read specific pages while it answers. Parallel pitches it as usable with no API key, built to return excerpts rich enough to answer from without a follow-up, so less of the conversation gets eaten by raw pages.
Check a breaking fact. When a question turns on current information, web_search runs a general web search and returns excerpts that are often enough to settle it without opening the page.
Read the exact page. When excerpts fall short, or you paste a link yourself, web_fetch pulls the page as clean text, up to 20 URLs per request, so Claude can quote the wording exactly instead of working from a truncated excerpt.
Run a quick market scan. Parallel lists live fact-checking during a conversation, research on recent or fast-moving topics and competitive intelligence among the common uses.
What Claude doesn't do with this connector: it writes nothing, posts nothing and opens no account. It won't rerun a search on its own either, since nothing runs in the background between two of your messages. For a search that fires on a schedule you need an automation tool, a different job; the Integrations hub covers that side.
Four words, then you connect
The bare minimum to follow the rest of this page.
- Connector
- The link you add once in Claude to open an outside service to it; here, a search engine rather than one of your accounts.
- Tool
- A named action the connector makes available. Claude decides by itself whether it needs one, and the directory lists them by name.
- Approval
- The confirmation Claude asks for before an action that changes something in an account, right when it matters in the chat.
- MCP
- The open standard that links connectors to Claude; it's what lets the assistant call an outside service at all.
Add Parallel Search to Claude in three steps
- 01
Find Parallel Search
In Claude's settings, open Customize, then Connectors, and spot Parallel Search in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization first.
- 02
Add it
Click Connect on its row. The directory sheet says no sign-in is required, so there's no Parallel login to enter. If adding it goes wrong, hit Disconnect and try again.
- 03
Check what shows up
No sign-in screen is expected for this connector. If a service ever does show you an authorization screen, read it before accepting: that screen, not Claude, sets how far access goes.
The 2 tools, grouped by what they do
Parallel Search gives Claude 2 tools: 2 that read your account, 0 that change something in it.
Two web-reading tools, nothing else. Names stay in English, the way Claude shows them.
- 2 read
What Claude reads (2)
2 toolsTwo tools that search the web and read pages without posting anything.
web_search
Runs a general web search and returns results with excerpts written for an assistant to read. Parallel designs those excerpts to be complete enough that opening the page often isn't needed.
web_fetch
Fetches the content of specific pages from their URLs and hands it back as readable text. Parallel reserves it for cases where search excerpts aren't enough.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before every action it takes on an account for you. The request shows up in the chat, at the moment it matters.
There's no account here: the connector searches and reads web pages, and Parallel presents both tools as read-only. No source describes a confirmation specific to either one. On a Team or Enterprise workspace, Owners decide whether a member may let some actions through without a fresh prompt, and they can limit what the connector may do for the whole organization, with no way around it from a personal account.
Which plans it's available on
None of the 819 sheets in the official directory shows plan availability. Per connector, that information isn't published anywhere.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables them for the organization before members connect. For the current state, the Parallel Search sheet in the official directory is the reference.
Where this connector stops
A connector isn't an automation. Claude calls these tools while it answers you, so no search reruns on a schedule.
By default the sheet only exposes read tools. That's an observed floor, not a guarantee: an admin can open actions that appear on no public sheet. The connector is documented by its publisher alone, with no Anthropic page; the rest of the family sits on the Claude connectors hub. The directory badge isn't an audit: Anthropic doesn't choose the tools exposed or vouch for how they behave, so only add what comes from a publisher you trust.
Need help connecting Parallel Search to Claude?
A person reads every message.