Proxyclaw
Give your agent rotating residential proxies so scrapers, browser automations, and integration tests can reach geo-blocked or bot-protected sites.
Overview
ProxyClaw is a MCP server for the Build phase that provides residential proxy tools with 175M+ IPs in 195+ countries for agent-driven web access.
What is this MCP server?
- Residential proxy MCP server with 175M+ IPs across 195+ countries
- Anti-bot bypass oriented tooling via ProxyClaw / iploop.io API
- stdio npm package proxyclaw-mcp-server v1.0.4
- Requires IPLOOP_API_KEY secret for authenticated proxy sessions
- 175M+ residential IPs
- npm package version 1.0.4
Community signal: 1 GitHub stars.
What problem does it solve?
Integration and scraping jobs fail on CAPTCHAs, IP bans, and regional blocks when agents call sites from a single datacenter IP.
Who is it for?
Builders automating third-party web APIs or UIs that throttle non-residential IPs during Build.
Skip if: Teams who only need static API keys with no geo rotation or who cannot use paid proxy services.
What do I get? / Deliverables
After registration, your agent can request proxied egress through ProxyClaw using your IPLOOP API key.
- Agent-callable proxy tools backed by IPLOOP
- Configurable residential egress for integration and automation scripts
Recommended MCP Servers
Journey fit
Proxy access is wired while building data pipelines, scrapers, and external integrations—not primarily a launch SEO task. ProxyClaw is an external service integration (IPLOOP API) exposed as MCP tools for fetch and automation workflows.
How it compares
Residential proxy MCP integration, not a headless browser or compliance audit skill.
Common Questions / FAQ
Who is ProxyClaw for?
Solo builders and agents doing web scraping, monitoring, or multi-region integration tests that need residential IPs.
When should I use ProxyClaw?
Use it in Build integrations when direct HTTP from your dev machine or cloud IP is blocked or geo-restricted.
How do I add ProxyClaw to my agent?
Install proxyclaw-mcp-server from npm, set IPLOOP_API_KEY in the MCP server environment, and register the stdio server in your MCP client.