[Feature]: Add a keyless Parallel Search MCP setup example #3453

Activity

1. roomote-community commented on Oct 10, 2026

   

   roomote-communitybot

   on Oct 10, 2026 – with roomote-community

   Contributor

   More actions

   I've analyzed this issue and recommend a small, docs-only implementation. The existing importer (apps/web/src/lib/custom-mcp-json-import.ts) accepts a URL-only mcpServers entry, and CustomMcpServers.tsx already provides Remote (HTTP) and Authentication → None. Parallel's current documentation describes anonymous access at /mcp and the web_search and web_fetch tools. No additional reporter clarification is needed to draft the example.

   Proposed implementation plan

   1. Add a “Keyless web search example: Parallel” section to apps/docs/integrations/custom-mcp-servers.mdx, near the existing import/setup guidance. Explain both entry points: shared under Integrations, or private under Personal Settings → Personal MCP servers. Show Import from JSON, confirm the remote URL and Authentication → None, choose the intended visibility, and save. Use this single-server snippet:

      {
        "mcpServers": {
          "parallel-search": {
            "url": "https://search.parallel.ai/mcp"
          }
        }
      }

   2. Include a short search → fetch walkthrough. For example, ask the agent to use Parallel to find current official documentation for a library, then fetch a returned documentation URL and summarize it with a citation. Name web_search and web_fetch; if showing tool inputs, use the provider's current schemas (objective and search_queries for search; urls for fetch). Explain how to confirm discovery in Manage tools, and use a newly started task when checking sandbox availability.
   3. State the limits and prerequisites accurately. Anonymous use needs no account, API key, or auth headers and is intended for exploration/light use at lower rate limits. Parallel's default fast search mode is a provider setting, distinct from Roomote's Fast mode. Link to provider docs rather than inventing a fixed quota. Self-hosted deployments need outbound HTTPS access from the Roomote control plane to search.parallel.ai. Link to the existing Exa guide as another keyless option.
   4. Validate before publishing. Import the exact snippet, confirm URL/no-auth prefill, discover both tools, and execute one search followed by fetching a returned public URL through Roomote's existing proxy. Verify private/shared visibility and existing per-tool controls behave as documented. Run mise exec -- pnpm --filter @roomote/docs check and inspect the rendered guide. Existing importer tests cover the configuration shape; additional application tests are only warranted if this check exposes a compatibility defect. Coordinate the edit with open docs PR [Docs] Explain custom MCP tool-list recovery #3451, which touches the same guide for tool-list recovery.

   Acceptance criteria: a reader can copy the snippet, discover both tools, and complete the search/fetch example without credentials. The proposed change uses existing custom MCP support and preserves the catalog and tool-permission behavior; it requires no new service, environment variable, or migration.

   This documents an opt-in provider choice without requiring a built-in integration. Live search/fetch through Roomote has not been exercised in this triage; it remains an explicit validation step. Maintainers can assess the docs-only proposal and reply with feedback; tag @roomote for follow-up.