qwen-code Lost web_search Built-in: The Fix (2026)

An r/Qwen_AI post: qwen-code's built-in web_search tool was ripped out in PR #3502 (May 2026) in favor of MCP-based search. The OP's verdict: "What a pain in the ass. This cli gets less usable with every new version." Here's the one-config-line fix.

Why qwen-code did this

The pattern is broader than qwen-code. Claude Code, Codex, opencode, and several others now treat web search as something the user wires via MCP rather than something the agent ships built-in. The honest tradeoff: built-in is convenient but locks the agent runtime into one search vendor's commercial terms; MCP-based puts the choice on the user but adds a config step.

The one-config-line fix

Edit qwen-code's mcp.json (or equivalent config file) and add Scavio MCP. One config line restores web search and adds Reddit + YouTube + Amazon + Walmart bonus surface.

{
  "mcpServers": {
    "scavio": {
      "url": "https://mcp.scavio.dev/mcp",
      "headers": { "x-api-key": "YOUR_SCAVIO_KEY" }
    }
  }
}

Free tier covers it

Scavio's free tier (500 credits/mo recurring, no card) handles moderate qwen-code usage. The Project tier ($30/mo for 7K credits) handles heavier daily usage. Most qwen-code users land in the free tier comfortably for the first few weeks.

What you get

Restart qwen-code. The tool surface picks up the new MCP. Six clearly- named tools appear: scavio.search, scavio.reddit_search, scavio.youtube_search, scavio.amazon_search, scavio.walmart_search, scavio.extract. The agent routes correctly without prompt engineering.

Test queries

'Search the web for latest LLM benchmarks 2026.'
'Search Reddit r/LocalLLaMA for Qwen3 35B reviews.'
'Search YouTube for ffmpeg.wasm video clipping tutorials.'
'Find the best Amazon-rated 65W USB-C charger.'
'Extract the readable content from https://example.com/article'

Cross-runtime bonus

The same Scavio MCP works in Claude Code, Cursor, VS Code, Windsurf, and opencode. One key, one config style across runtimes. If you use more than one agent runtime, you only manage one search vendor relationship instead of one per runtime.

# Claude Code
claude mcp add scavio https://mcp.scavio.dev/mcp \
  --header 'x-api-key: $SCAVIO_API_KEY'

# Cursor: settings.json mcpServers entry (same shape as qwen-code config)
# VS Code Continue extension: similar
# Windsurf: similar

The MCP-as-default pattern

qwen-code's PR #3502 is one data point in a broader pattern. CLI coding agents are removing built-in tools and pushing the search-vendor decision out of the agent runtime onto the user. For users adopting the pattern, the practical recipe is: one MCP per role. Scavio for typed multi-platform search. A code search MCP (Semble) for in-repo. A deep research delegation MCP (Comet Skill) when you have Perplexity Pro.

What if you only want Google search

Brave Search MCP, community Tavily/Exa wrappers, or a custom single-vendor MCP all work. Scavio's edge is multi-platform under one key plus first-party hosted MCP at mcp.scavio.dev. If you only need Google and you care about index independence, Brave Search MCP is a fine pick.

Honest case for built-in tools

Convenience. If you only use one agent runtime and the built-in vendor works for you, the MCP path adds setup overhead you don't need. The pattern only earns its keep when you use multiple runtimes or want vendor independence.

What to do this week

If you're on qwen-code and missing web search: edit mcp.json, add the Scavio block, restart, test. Total elapsed time: under 5 minutes.

Verified-online May 2026 against the qwen-code commit aeeb2976 and the Scavio MCP spec.