google_search_scraper — oxylabs mcp MCP Tool
google_search_scraper
(google search scraper) is one of 10 tools on the
oxylabs mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call google_search_scraper from your client
- Claude Code oxylabs mcp google_search_scraper run in your project directory
- Claude Desktop oxylabs mcp google_search_scraper ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor oxylabs mcp google_search_scraper ~/.cursor/mcp.json
- VS Code oxylabs mcp google_search_scraper .vscode/mcp.json
- Zed oxylabs mcp google_search_scraper ~/.config/zed/settings.json
- Windsurf oxylabs mcp google_search_scraper ~/.codeium/windsurf/mcp_config.json
- Cline oxylabs mcp google_search_scraper ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI oxylabs mcp google_search_scraper ~/.gemini/settings.json
- Grok oxylabs mcp google_search_scraper .mcp.json (in your project root)
- ChatGPT oxylabs mcp google_search_scraper Settings → Connectors → Advanced → Developer mode
- Claude.ai oxylabs mcp google_search_scraper Settings → Connectors → Add custom connector
- LangChain oxylabs mcp google_search_scraper pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http oxylabs-mcp https://mcp.oxylabs.io/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.