proxy_locations — quanticdata mcp MCP Tool
proxy_locations
(proxy locations) is one of 26 tools on the
quanticdata mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call proxy_locations from your client
- Claude Code quanticdata mcp proxy_locations run in your project directory
- Claude Desktop quanticdata mcp proxy_locations ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor quanticdata mcp proxy_locations ~/.cursor/mcp.json
- VS Code quanticdata mcp proxy_locations .vscode/mcp.json
- Zed quanticdata mcp proxy_locations ~/.config/zed/settings.json
- Windsurf quanticdata mcp proxy_locations ~/.codeium/windsurf/mcp_config.json
- Cline quanticdata mcp proxy_locations ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI quanticdata mcp proxy_locations ~/.gemini/settings.json
- Grok quanticdata mcp proxy_locations .mcp.json (in your project root)
- ChatGPT quanticdata mcp proxy_locations Settings → Connectors → Advanced → Developer mode
- Claude.ai quanticdata mcp proxy_locations Settings → Connectors → Add custom connector
- LangChain quanticdata mcp proxy_locations pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http quanticdata-mcp https://api.quanticdata.io/mcpOther tools on this server
- scrape
- generate_parser
- save_parser_preset
- list_parser_presets
- parser_preset_stats
- heal_parser_preset
- seo_audit
- ai_visibility
- search
- search_and_read
- map
- crawl
- crawl_status
- batch
- batch_status
- search_bulk
- search_bulk_status
- create_dataset
- dataset_status
- list_proxies
- generate_proxies
- whitelist_ip
- list_collectors
- run_collector
- collector_run_status
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.