proxy-seller-mcp

Model Context Protocol server for the Proxy-Seller Client API.

Lets Claude inspect your proxies, balance, payments and place/extend orders on your behalf using your API key.

Setup

1. Get an API key at https://proxy-seller.com/personal/api.
2. Add the entry to your MCP config:
   • Claude Code — .claude.json in your project root or ~/.claude.json globally

{
  "mcpServers": {
    "proxy-seller": {
      "command": "npx",
      "args": ["-y", "proxy-seller-mcp"],
      "env": {
        "PROXY_SELLER_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

3. Restart the client.

Tools

| Tool | Description | |---|---| | list_proxies | List your proxies (filter by type, country, expiry) | | get_balance | Check account balance | | list_payments | Available payment methods (pay from balance with paymentId: 1) | | add_balance | Top up the balance with an external method — returns a payment URL to confirm | | get_reference | Available countries and rental periods for a proxy type | | calc_order_cost | Preview order cost before buying | | make_order | Place a new proxy order (charges balance) | | calc_prolong_cost | Preview renewal cost | | make_prolong | Renew existing proxies (charges balance) | | export_proxies | Export proxies as a ready-to-use txt/csv list (filter by country, protocol, expiry) | | list_auth | List authorization records (login/password and IP-whitelist) — reminds credentials | | add_auth | Create an authorization for an order — login/password (auto-generated) or IP-whitelist (state-changing) | | change_auth | Change a proxy's login/password or whitelisted IP, or toggle it (state-changing) | | delete_auth | Delete a proxy authorization (destructive) | | replace_proxy | Request a replacement for a bad proxy IP (state-changing) | | get_resident_package | Residential traffic balance, expiry and package_key | | get_resident_geo | Available residential locations (countries; regions/cities/ISPs per country) | | list_resident_lists | List residential proxy access lists (geo, rotation, credentials) | | add_resident_list | Create a residential list with geo + rotation + ports (state-changing) | | set_resident_rotation | Change a residential list's IP rotation (state-changing) | | rename_resident_list | Rename a residential list (state-changing) | | delete_resident_list | Delete a residential list (destructive) |

make_order, make_prolong, add_auth, change_auth, delete_auth, replace_proxy, add_resident_list, set_resident_rotation, rename_resident_list and delete_resident_list are not idempotent — calling them twice repeats the action. Claude will always ask for confirmation before executing write operations.

Paying for orders

• No default payment source. For every order/renewal the assistant always asks the user how they want to pay and presents the options together:
  • Account balance — paymentId: 1
  • Saved card — paymentId: 43
  • Payment method (PayPal, crypto, card) — an id from list_payments
• Topping up the balance (add_balance) can be done only with a payment method or the saved card (not from the balance). It returns a url the user opens in the browser to confirm; there is no payment-status webhook, so poll get_balance to confirm the funds arrived.
• Paying by an external method may return a url in the response — the payment is not complete until the user confirms it on that page.
• The balance field in order/renewal responses is the authoritative post-transaction balance from the API. When paid by card/crypto the account balance is unchanged.

Residential proxies

Residential proxies are sold as a traffic pool, not as individual IPs. You access the pool through lists — each list is a geo-filtered access configuration with its own rotation and a number of ports. To get a ready-to-use set of residential proxies (e.g. "5 in Germany"):

1. get_resident_geo with country: "DE" — find valid geo values.
2. add_resident_list with country: "DE", ports: 5, rotation — creates the list, returns its id.
3. export_proxies with type: "resident" and listId: <id> — download the connectable login:password@host:port lines.

get_resident_package shows remaining traffic and the package expiry.

Authorizations

Each proxy order has authorizations that control how you connect. There are two types, both created with add_auth by passing the order's orderNumber (get it from list_auth / list_proxies):

• Login/password — call add_auth with just orderNumber. The login and password are generated automatically by the API — you cannot choose them at creation. To set custom credentials, create the authorization first, then change them with change_auth.
• IP whitelist — call add_auth with orderNumber and ip. The whitelisted IP is applied immediately from the value you pass; no login/password is involved.

Use list_auth to read existing authorizations (and their id), change_auth to edit one (login/password, IP, or enable/disable), and delete_auth to remove one.

Auto-renewal

Auto-renewal (auto_renew) cannot be toggled through the API — it is configured only in the web dashboard. The API exposes auto_renew / auto_renew_period as read-only fields, so list_proxies shows the current status, but enabling or disabling it must be done in the dashboard.

License

MIT