Definition
MCP as default web search is the 2026 pattern (most visibly adopted by qwen-code in PR #3502) of CLI coding agents removing built-in web_search tools and replacing them with Model Context Protocol server expectations, pushing the search-vendor decision out of the agent runtime and onto the user's MCP configuration.
In Depth
An r/Qwen_AI post in May 2026 documented the change in qwen-code: the built-in web_search tool was ripped out in favor of MCP-based search, frustrating users who wanted batteries-included. 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 search is convenient but vendors lock the agent runtime into one search vendor's commercial terms; MCP search puts the choice on the user but adds a config step. For users adopting the pattern, the practical recipe is one MCP per role: scavio.search for typed multi-platform Google + Reddit + YouTube + Amazon + Walmart; a deep research delegation MCP (Comet Skill, Perplexity MCP) when the workflow needs multi-step research; and a code search MCP (Semble) when the repo is large.
Example Usage
Qwen-code user upset about the removed web_search tool installs Scavio MCP via the agent's mcp.json. One config line later they have typed Google + Reddit + YouTube + Amazon + Walmart search inside qwen-code, plus the same MCP works in Claude Code and Cursor.
Platforms
MCP as Default Web Search is relevant across the following platforms, all accessible through Scavio's unified API:
Related Terms
MCP Tool Naming Convention
MCP tool naming convention is the discipline of naming Model Context Protocol tools clearly and orthogonally (e.g., scav...
Comet Skill / CDP Browser Delegation
The Comet Skill / CDP browser delegation pattern is a way to give a coding agent (Claude Code, Codex) deep research capa...