The QuantumProxies MCP Server is used to connect QuantumProxies' residential proxy capabilities to AI agents, giving Claude, Cursor, and other MCP clients real-time web access capability.
-
Main uses It is aimed at AI agent scenarios that need web data: through residential proxies and real browser TLS fingerprints, it scrapes, searches, maps, and crawls pages, so that pages that would otherwise block ordinary bots can also return clean content. At the same time, it hands the various raw proxy endpoints in the active plan (residential, mobile, datacenter, ISP, IPv6) to the agent, which can be connected directly to any HTTP client.
-
Main capabilities
-
Scrape: scrape pages into Markdown.
-
SERP search: perform searches.
-
Site map and crawl.
-
Proxy generation: residential, mobile, datacenter, ISP, IPv6 proxies, with country/city/ASN targeting, rotating or sticky sessions, HTTP or SOCKS5.
-
Built-in ready-made collectors. The official description mentions 25 tools; later it also mentions 28 tool definitions totaling about 14,000 tokens.
-
How to use Running locally requires no installation; npx fetches quantumproxies-mcp on demand (requires Node.js 18+). Claude Code uses a single command; Claude Desktop, Cursor, or any MCP client can write to claude_desktop_config.json, .cursor/mcp.json, or .mcp.json. The same server can also run as a hosted Streamable HTTP remote endpoint, for clients that prefer a URL. OAuth connections are supported: the endpoint supports the MCP authorization specification (OAuth 2.1). In supported clients, add the hosted URL as a remote server, and the client will open the QuantumProxies.io login page. After logging in or creating a free account, click allow access, and the connection is complete; a key named MCP · <client> will appear on the dashboard API keys page, and deleting it disconnects the client. Under the hood this involves authorization server metadata, protected resource metadata, dynamic client registration (RFC 7591) and Client ID Metadata Documents, required PKCE (S256), 1-hour access tokens and rotating refresh tokens, and token binding to the endpoint (RFC 8707). Usage is billed against the balance. Clients that do not want to use OAuth can use a bearer token: the key is placed in the Authorization header per request (or X-Api-Key), and the server does not store it. Requests with neither a token nor a key receive a 401 and a WWW-Authenticate header pointing to the metadata, thereby prompting OAuth-capable clients to initiate login. Self-hosting the endpoint is the second binary in the same package; after setting QUANTUMPROXIES_API_KEY, it can serve that account to callers who do not send credentials. It can also be run from source (development mode), and then point the client to the local build.
-
Applicable scenarios and limitations Suitable for AI agent workflows that need web scraping, search, site mapping and crawling, and that need to generate and manage multiple proxy endpoints. Local models (Ollama, LM Studio, Qwen, Open WebUI): 28 tool definitions total about 14,000 tokens; Ollama's default 4K context cannot fit them, and a 32K context loses nearly half its space before scraping the first page. Fewer tools can be loaded: under stdio set QUANTUMPROXIES_TOOLS=web; for the hosted endpoint URL add ?tools=web and send the API key in the Bearer header, for example https://api.quantumproxies.io/mcp?tools=web；名称可组合，如 ?tools=lite,collectors. Privacy and data: the server runs locally and only communicates with the public QuantumProxies API (https://app.quantumproxies.io/api/v1）通信，使用你自己的 qp_live_ key; each call carries the parameters you or the agent pass in (target URL or query, and any extraction hints), does not read or transmit any other content on the local machine, and has no filesystem, shell, or clipboard access. Account data and request logs (target URL or query, timestamp, response status, bytes transferred, API key used) are used for billing, abuse prevention, and support; scraped page content is not retained except as needed to return results. You do not sell personal data and share it only with service processors and upstream proxy networks (connection metadata only); account data is retained for the life of the account, request logs are retained on a rolling window, and deletion can be requested at any time. The API key is stored by Claude Desktop in the operating system keychain and passed to the server as an environment variable; it is not written into the package and is not sent anywhere except the QuantumProxies API, and can be https://app.quantumproxies.io/api-keys revoked or rotated. Example prompts include: scrape the pricing page of example.com and give the plans and prices; search Google Shopping in the United States for "nintendo switch oled" and list the 5 cheapest; map docs.example.com and then crawl only /guides/ pages and summarize; list proxy plans and generate 5 sticky US residential proxy socks5 URLs; get a German rotating mobile proxy and whitelist server IP 203.0.113.7. Contact email: support@quantumproxies.io. Full privacy policy:https://quantumproxies.io/privacy。
Details such as parameters and pricing, and the specific tool list, are not yet fully provided in the materials.
