Other · Local MCP server
Proxy4agents MCP
Residential proxy MCP for AI agents — geo-targeting, sticky sessions, anti-bot bypass.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.NovadaLabs/proxy4agents-mcp- Version
- 1.7.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-04-10
- Updated
- 2026-04-10
- Publisher
- NovadaLabs (GitHub) · 2 servers with pages here
- Repository
- github.com/NovadaLabs/proxy4agent
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | bestproxy4agents-mcp | 1.7.0 | stdio |
How to connect Proxy4agents MCP
Proxy4agents MCP runs locally from a Node.js package published to the npm registry: bestproxy4agents-mcp version 1.7.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y bestproxy4agents-mcp@1.7.0. It reads these environment variables: NOVADA_PROXY_USER (secret), NOVADA_PROXY_PASS (secret), NOVADA_API_KEY (secret), NOVADA_BROWSER_WS (secret), BRIGHTDATA_USER (secret), BRIGHTDATA_PASS (secret), SMARTPROXY_USER (secret), SMARTPROXY_PASS (secret), OXYLABS_USER (secret), OXYLABS_PASS (secret) and PROXY_URL (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"proxy4agents-mcp": {
"command": "npx",
"args": [
"-y",
"bestproxy4agents-mcp@1.7.0"
],
"env": {
"NOVADA_PROXY_USER": "<secret>",
"NOVADA_PROXY_PASS": "<secret>",
"NOVADA_API_KEY": "<secret>",
"NOVADA_BROWSER_WS": "<secret>",
"BRIGHTDATA_USER": "<secret>",
"BRIGHTDATA_PASS": "<secret>",
"SMARTPROXY_USER": "<secret>",
"SMARTPROXY_PASS": "<secret>",
"OXYLABS_USER": "<secret>",
"OXYLABS_PASS": "<secret>",
"PROXY_URL": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from NovadaLabs (GitHub)
| Server | Runs |
|---|---|
| Novada MCPSearch, extract, crawl, map, research, scrape 16 platforms, browser automation, proxy — one API key. | Remote & Local · HTTP, stdio |
More other servers
| Server | Runs |
|---|---|
| Proximens Oracle1000+ Generative Engine Optimization (GEO) principles exposed via MCP for AI agents. | Remote · HTTP |
| Proximo — the Proxmox MCP you can hand the keysThe Proxmox MCP you can hand the keys: VE/PBS/PMG/PDM. Plan, prove, undo, diagnose. MCP/A2A/API. | Local · stdio |
| Proxmox VEManage Proxmox VE nodes, VMs, containers, storage and snapshots. Read-only by default. | Local · stdio |
| Proxy AIopsGoverned Traefik + Caddy + HAProxy ops: routes, upstreams, certs, 5xx RCA. 28 tools. | Local · stdio |
| ProxykeyIssue, rotate and revoke scoped API-key passes for 25+ providers — the agent never sees a real key. | Remote · HTTP |
| Proxylang website translationTranslate a website into other languages from one script tag. Free trial, no signup. | Remote · HTTP |
| Prufa MCPThe full Prufa QA agent over MCP: audits, flows, monitors, gremlin chaos, discovery. | Local · stdio |
| PrwebPRWeb MCP — press releases from PRWeb's all-releases feed. | Remote · HTTP |