The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the ProxyCove listing page.
Let an AI agent buy and manage real proxies — no signup, no dashboard, no card details in the chat.
ProxyCove sells residential, mobile and datacenter proxies prepaid per GB across 170+ countries. This MCP server exposes that as 14 tools, so an agent can create its own account, hand the human a payment link, buy a proxy and get working connection credentials — all inside one conversation.
Status: live. The endpoint above is public — connect and use it. Anonymous calls are allowed for
get_pricing,list_locationsandcreate_account; everything else needs a key. Clients that prefer OAuth 2.1 can discover it at/.well-known/oauth-protected-resource.
Who it's for: developers building scraping / automation / testing agents, anyone whose agent needs an exit IP in a specific country, and MCP clients that want a proxy provider they can call directly instead of wrapping a REST API by hand.
What an agent can do end to end
create_account → gets an API key (pc_live_...). No registration form, no email required.create_topup → gets a payment_url. The human pays in the browser (SBP, bank card, crypto).buy_proxy → gets http://login:password@go.proxycove.com:824 and starts using it.Prices: residential $2.7/GB · mobile $3.8/GB · datacenter $1.5/GB. Traffic is prepaid and does not expire while the account is active.
The server is remote — nothing to install. Add the endpoint to your client and (once you have a key) send it as a bearer token.
You can add the connector without a key: get_pricing, list_locations and create_account work unauthenticated. Run create_account, save the returned pc_live_... key, put it in the header, reconnect.
Without a key yet (to call create_account first):
Settings → Connectors → Add custom connector
| Field | Value |
|---|---|
| Name | ProxyCove |
| Remote MCP server URL | https://mcp.proxycove.com/mcp |
Until OAuth ships, Claude Desktop can also reach the server through the stdio bridge, which is where the header lives:
Settings → Connectors → Advanced → enable Developer mode, then Create:
| Field | Value |
|---|---|
| Name | ProxyCove |
| MCP server URL | https://mcp.proxycove.com/mcp |
| Authentication | Access token / API key → paste pc_live_YOUR_KEY |
~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):
~/.codex/config.toml:
Transport is streamable HTTP, stateless — POST only, one JSON-RPC request per call, no SSE stream and no session id. GET/DELETE on the endpoint return 405.
Beyond the tool descriptions, this repo ships an agent skill that tells an agent which tool to reach for: how to pick a proxy type for a job, when a sticky session is required, what each error code actually means, and the rules that keep the human in control — never handle payment details, quote the price before spending, save the key.
| Tool | What it does | API key |
|---|---|---|
get_pricing | Price per GB (USD) for residential / mobile / datacenter | no |
list_locations | Countries available for a given proxy type | no |
create_account | Creates an account with no signup form, returns a pc_live_... key | no |
get_account | Balance (USD), attached email, number of active proxies | yes |
create_topup | Creates an invoice, returns payment_url for the human | yes |
get_payment_status | Invoice status: pending / paid / cancelled | yes |
buy_proxy | Buys a proxy from the balance, returns connection credentials | yes |
list_proxies | All proxies with remaining traffic and credentials | yes |
get_credentials | Connection string for one proxy | yes |
extend_proxy | Adds prepaid GB to an existing proxy (credentials unchanged) | yes |
get_usage | Live used / remaining traffic for one proxy | yes |
set_rotation | Rotate every request ↔ sticky IP for 1–120 minutes | yes |
link_telegram | Returns a code to link the account to the Telegram bot (second way back in if the key is lost) | yes |
attach_recovery | Attaches an email so the human can log in on the website | yes |
Read-only tools carry readOnlyHint. No tool deletes anything — there is no destructive operation in this server, and no tool can move money out of the account.
Every proxy is reachable at go.proxycove.com:
| Port | Behaviour |
|---|---|
824 | New IP on every request |
10000 | Sticky IP, held for the configured 1–120 minutes |
set_rotation switches a proxy between the two modes; the login and password stay the same.
After
buy_proxy, wait ~5 seconds before the first request. The country filter takes a moment to propagate upstream, and an immediate first request may exit from another country.
pc_live_... and is sent as Authorization: Bearer pc_live_....create_account issues one. The three no-auth tools exist precisely so an agent can bootstrap: check prices, check countries, create the account — then the human stores the key in the connector config.Authorization header to the ProxyCove REST API and returns the JSON response.no_api_key error explaining what to do — not a crash.This is a hard boundary, enforced by the tool design:
create_topup returns a payment_url. That is all the agent gets.sbp (Russian instant bank transfer), card_ru, card_international, crypto, crypto_cryptomus. Minimum top-up $1.50.get_payment_status until paid and continues.Purchases (buy_proxy, extend_proxy) spend the prepaid balance only. An agent cannot spend money that the human has not already deposited.
The server is a thin, stateless wrapper over the public ProxyCove REST API — roughly 200 lines of Node with no database, no cache and no persistence. Self-host it if you want to audit the traffic, pin a version, or run it inside your own network.
Requirements: Node 20+ (or Docker).
Docker:
| Variable | Default | Purpose |
|---|---|---|
MCP_PORT | 4010 | Port the HTTP server listens on |
MCP_SECRET_PATH | /mcp | Path the MCP endpoint is mounted at |
BACKEND_BASE_URL | http://backend:5000 | Base URL of the ProxyCove API; use https://proxycove.com when self-hosting |
PUBLIC_API_INVITE_CODE | (empty) | Optional invite code forwarded by create_account |
Configuration is entirely from env — there is no config file and no secret baked into the image.
GET /healthz returns { "ok": true, "service": "proxycove-mcp" }.
Point your client at your own instance the same way:
Everything the MCP server does is available directly over HTTP — same endpoints, same key:
https://proxycove.com/api/v1https://proxycove.com/api/v1/openapi.jsonUse this if you are writing a normal client, a LangChain/LlamaIndex tool, a CI job, or anything that is not an MCP host.
create_account. Save it immediately — ProxyCove cannot show it again.attach_recovery or link_telegram early. Without a recovery channel on the account, a lost key means a lost balance.pc_live_... like a password: it is a spending credential. Never paste it into a shared chat, a public repo, or an issue on this tracker.bearer_token_env_var, ${VAR} substitution) over literal keys in config files that get committed.Issues and pull requests are welcome — bug reports, client-config recipes for MCP hosts not covered above, and tool-description improvements especially. The tool schemas are the product surface here; if a description misled your agent, that is a bug worth filing.
MIT © ProxyCove
Website: proxycove.com · MCP endpoint: https://mcp.proxycove.com/mcp · REST API: https://proxycove.com/api/v1 · Support: support@proxycove.com