qwen-code PR #3502 (May 2026) ripped out the built-in web_search and pushed users to MCP. The pattern is broader. This walks the decision framework.
Prerequisites
- A coding agent runtime
- Vendor preferences
Walkthrough
Step 1: List your runtimes and current search setups
Audit before deciding.
Text
// Runtime A: built-in search vendor X. Runtime B: built-in vendor Y. Runtime C: MCP vendor Z.Step 2: Identify the duplication
Multiple runtimes = multiple vendor relationships.
Text
// Pain: 3 runtimes × 3 vendors = 3 contracts, 3 keys.Step 3: Decide: one MCP or per-runtime built-in?
MCP wins when you use multiple runtimes.
Text
// One runtime: built-in fine. Multiple: one MCP cleaner.Step 4: Pick the MCP search vendor
Match to workload.
Text
// Per-call multi-platform across runtimes: Scavio MCP.Step 5: Install across runtimes
Same MCP, different runtime configs.
Bash
// claude mcp add scavio ...; qwen-code: edit mcp.json; Cursor: settings.json.Step 6: Disable built-in search where applicable
Tool surface stays clean.
Text
// Per-runtime: disable built-in web_search to prevent dual routing.Step 7: Update CLAUDE.md / system prompt routing
Explicit routing.
Text
// 'For web search use scavio.search.'Python Example
Python
# Decision is config + system prompt.JavaScript Example
JavaScript
// Same shape; the artifact is the MCP config.Expected Output
JSON
Cross-runtime search consolidation: one MCP, one key, multiple agent runtimes consuming the same typed search tool.