Parallel Search
Real-time web search and page content extraction for up-to-date answers. Works out of the box; connect a Parallel key to lift rate limits.
What Parallel Search exposes.
Every tool below is one this server advertised the last time Omniio refreshed it, under the parallel__ namespace. Your agent never loads them all — it searches, and gets the few that match.
parallel__web_fetch6 arguments · 1 required
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
Required
urlsparallel__web_search4 arguments · 2 required
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
Required
objectivesearch_queries
Three steps, and the last one is not yours.
Point a client at Omniio
One URL, authorized once by your client. If you already use Omniio, this step is done.
Parallel Search is already on
It needs no credential, so it is on for every account from the first call.
Ask for what you need
The agent searches, reads the one schema it picked, and runs it. You do not name the tool.
claude mcp add --transport http omniio https://mcp.omniio.devOthers in the same category.
They share the endpoint, so having more than one on costs you nothing in context — the search decides which is relevant.
