Proxy4agents Mcp
Give Claude Code or Cursor agents residential proxies with geo-targeting and sticky sessions so scrapers and browser workflows survive anti-bot blocks.
Overview
proxy4agents-mcp is a Build-phase MCP server that routes AI agent HTTP and browser traffic through residential proxies with geo-targeting, sticky sessions, and anti-bot-friendly egress.
What is this MCP server?
- Residential proxy MCP with geo-targeting and sticky sessions for agent-driven browsing
- stdio npm package bestproxy4agents-mcp (v1.7.0) for Claude Desktop and compatible MCP hosts
- Novada proxy user/pass plus Scraper API key and Browser WebSocket for search and render tools
- Optional BrightData and Smartproxy env vars for multi-provider failover
- Built for anti-bot bypass when automating public web research or extraction
- Server schema version 1.7.0
- npm package identifier bestproxy4agents-mcp with stdio transport
- Documented env vars: NOVADA_PROXY_USER, NOVADA_PROXY_PASS, NOVADA_API_KEY, NOVADA_BROWSER_WS, BRIGHTDATA_USER, BRIGHTDAT
Community signal: 4 GitHub stars.
What problem does it solve?
Agent-driven scraping and automation fail when cheap IPs get blocked and you do not want to maintain proxy rotation code in every project.
Who is it for?
Indie builders automating research, price checks, or login-light flows where residential IPs and session stickiness matter.
Skip if: Teams that only need static API calls with no web friction, or anyone unwilling to pay for residential proxy accounts and comply with site policies.
What do I get? / Deliverables
After you register the stdio server and proxy env vars, your agent can target countries, keep sticky sessions, and call Novada search/render tools without custom proxy plumbing.
- MCP-configured residential proxy tools callable from your coding agent
- Geo-targeted, session-stable egress for automated fetches and renders
- Optional multi-provider proxy env configuration in one server manifest
Recommended MCP Servers
Journey fit
Proxy wiring is integration work you do while building agents, crawlers, and data pipelines—not a launch or growth tactic on its own. MCP exposes Novada, BrightData, and Smartproxy credentials as tools your coding agent calls during backend and agent-tooling setup.
How it compares
MCP proxy integration for agents, not a standalone scraping framework or headless-browser skill.
Common Questions / FAQ
Who is proxy4agents-mcp for?
Solo and indie developers building AI agents in Claude Code, Cursor, or similar hosts who need residential proxies without writing rotation logic in every repo.
When should I use proxy4agents-mcp?
Use it during Build when integrating web automation, competitive research, or anti-bot-sensitive fetches that datacenter IPs cannot complete reliably.
How do I add proxy4agents-mcp to my agent?
Add the npm stdio server bestproxy4agents-mcp to your MCP config, set NOVADA_PROXY_USER and NOVADA_PROXY_PASS (and optional NOVADA_API_KEY, NOVADA_BROWSER_WS, BrightData, or Smartproxy vars), then restart the host.