Use case
The MCP Tool Provider guide shows Streamable HTTP with a local server and a bearer token. A working hosted example would make it easier to try remote MCP tools without running another server or getting a search API key.
I work at Parallel and would like to add a short Python and TypeScript example using our free Search MCP.
Solution/User Experience
Add a “Hosted web search” section to docs/src/content/docs/agents/mcp-tool-provider.mdx, using the existing MCPToolProvider and streamable-http transport with https://search.parallel.ai/mcp. The example would expose web_search and web_fetch without a Parallel account or API key. Anonymous access is rate limited, and any agent still needs its usual model-provider setup.
This would be a docs example users choose to run. It wouldn't change routing, defaults, dependencies, or existing examples. The section would explain that tool-call queries, URLs, and supplied context are sent to Parallel, show cleanup, and link to the service's setup and limits.
I'd validate the snippets through Agent Squad's actual provider, checking tool discovery, a useful search result, and disconnecting before submitting the linked PR. Would this be a useful addition to the guide?
Alternative solutions
Users can supply their own remote server today. The guide's placeholder is flexible, but it doesn't give readers a hosted endpoint they can try straight away. This proposal doesn't replace the existing search examples or add a new search abstraction.
Use case
The MCP Tool Provider guide shows Streamable HTTP with a local server and a bearer token. A working hosted example would make it easier to try remote MCP tools without running another server or getting a search API key.
I work at Parallel and would like to add a short Python and TypeScript example using our free Search MCP.
Solution/User Experience
Add a “Hosted web search” section to
docs/src/content/docs/agents/mcp-tool-provider.mdx, using the existingMCPToolProviderandstreamable-httptransport withhttps://search.parallel.ai/mcp. The example would exposeweb_searchandweb_fetchwithout a Parallel account or API key. Anonymous access is rate limited, and any agent still needs its usual model-provider setup.This would be a docs example users choose to run. It wouldn't change routing, defaults, dependencies, or existing examples. The section would explain that tool-call queries, URLs, and supplied context are sent to Parallel, show cleanup, and link to the service's setup and limits.
I'd validate the snippets through Agent Squad's actual provider, checking tool discovery, a useful search result, and disconnecting before submitting the linked PR. Would this be a useful addition to the guide?
Alternative solutions
Users can supply their own remote server today. The guide's placeholder is flexible, but it doesn't give readers a hosted endpoint they can try straight away. This proposal doesn't replace the existing search examples or add a new search abstraction.