@proxies-sx/mcp-server

MCP (Model Context Protocol) server for Proxies.sx: residential and mobile proxies for AI agents, metered per GB. Claude, Cursor and any MCP client can get rotating or sticky HTTP/SOCKS5 proxy URLs, check live stock per country, rotate IPs and manage usage by themselves, for web scraping, data collection and browser automation.

The main product is the Pool Gateway: one endpoint, gw.proxies.sx (HTTP 7000, SOCKS5 7001), where the proxy username says which pool, country and session you want. With this server an agent reads live stock, gets its credentials, builds the proxy URL, watches usage and opens a support ticket when something is wrong. For a dedicated, unlimited-traffic device it rents a Private modem (one 4G/5G modem, by the day, week or month) and tops up the balance by card through a link a person pays. It can also manage dedicated ports on carrier modems, Private Pools and Reserved IPs.

Every tool carries MCP annotations (readOnlyHint, destructiveHint), so a client can ask before a delete, rotate, cancel or purchase. The tools that spend money do nothing until the agent passes confirm: true, which it sets only after the user agreed to the exact USD amount.

Quick start

1. Create an API key at client.proxies.sx/account and add traffic (GB) at client.proxies.sx/purchase.
2. Add the server to your client. Claude Code:

claude mcp add proxies-sx -e PROXIES_API_KEY=psx_your_api_key_here -- npx -y @proxies-sx/mcp-server

Or install it as a Claude Code plugin, which connects to the hosted server below, adds the Proxies.sx skill and asks for your API key once (stored masked in secure storage):

/plugin marketplace add bolivian-peru/proxies-sx-mcp-server
/plugin install proxies-sx@proxies-sx

Or connect to the hosted server, with nothing to install: https://api.proxies.sx/mcp (Streamable HTTP). Send the key as Authorization: Bearer psx_...; without a key only the public tools are listed (stock, proxy URL format, error help, service status).

claude mcp add --transport http proxies-sx https://api.proxies.sx/mcp --header "Authorization: Bearer psx_your_api_key_here"

{ "mcpServers": { "proxies-sx": { "url": "https://api.proxies.sx/mcp", "headers": { "Authorization": "Bearer psx_your_api_key_here" } } } }

Add ?toolset=full to the URL for every API-key tool. The x402 wallet mode runs only locally (npx), because the hosted server never holds a wallet key.

3. Ask for a proxy:

Check Pool Gateway stock for Germany, then give me a sticky residential proxy URL there.

The agent calls pool_get_stock, pool_get_my_credentials and pool_build_proxy_url and answers with a URL such as http://psx_abc123-peer-de-iptype-residential-sid-job1-rot-sticky:[email protected]:7000.

API key scopes

A customer key can hold: ports:read, ports:write, ports:rotate, billing:read, account:read, account:write, traffic:read, tickets:read, tickets:write. Select all of them for the full customer tool set. Two opt-in scopes are never in the default set and must be ticked on purpose: modems:purchase (proxies_modem_buy, proxies_modem_renew) and billing:topup (proxies_topup_checkout, proxies_topup_status; each key has a daily top-up cap, spendCapUsdPerDay, default 100 USD, set in the dashboard).

• billing:write is not available to customer keys. The tools that need it (purchase_shared_traffic, create_crypto_payment, cancel_crypto_payment) work with reseller and admin keys only; a customer buys traffic in the dashboard.
• The pak_ key tools (pool_mint_key and the other pool_*_key tools) need a reseller account, whose keys hold customers:read and customers:write.
• The ops_* tools answer only to admin keys with ops:* scopes.

Pool Gateway rules

The username grammar is psx_<account>-<pool>-<country>[-token-value ...]. pool_build_proxy_url writes it for you; these are the rules behind it.

This is the beginning of the README. Read the rest at the original. Read the full README ↗