proxies-sx-mcp-server

name: proxies-sx-mcp-server description: Manage Proxies.sx mobile/residential proxies, mint x402 USDC sessions, rotate IPs, and consume marketplace data services from any MCP-compatible AI agent (Claude Desktop, Cursor, Windsurf, Continue, Cline, Claude Code). Trigger this skill the moment the user wants to install / configure / use the Proxies.sx MCP server, integrate proxies into a Claude Desktop or Cursor workflow, mint a proxy without an API key (x402 autonomous mode), build an AI scraping agent that buys its own bandwidth, troubleshoot MCP tool errors, or pick between API-key mode and x402 wallet mode. Use it whenever the user mentions "Proxies.sx MCP", "@proxies-sx/mcp-server", "MCP proxy tools", "Claude Desktop proxy", "x402 mcp", "agent proxy purchase", "proxy MCP", or anything implying machine-driven proxy management — even if they don't explicitly ask for "this skill".

Proxies.sx MCP Server

Open-source Model Context Protocol server that exposes 61 typed tools to any MCP-compatible AI agent. Two operating modes:

• API Key mode — agent acts on behalf of a logged-in Proxies.sx user (44 tools: ports, rotation, billing, payments, support, etc.)
• x402 Autonomous mode — agent pays for its own proxies with USDC on Base or Solana, no human account needed (17 tools: x402_get_proxy, x402_rotate_ip, x402_get_pool_access, …)

Source: https://github.com/bolivian-peru/proxies-sx-mcp-server · npm: @proxies-sx/mcp-server · License: MIT.

When to use this skill

Use it for any of these intents:

• "Set up Proxies.sx MCP in Claude Desktop / Cursor / Windsurf / Cline / Continue"
• "Configure my agent to buy proxies with USDC"
• "Add the proxy MCP server to my AI workflow"
• "Help me debug an MCP tool error from @proxies-sx/mcp-server"
• "Pick between API key and x402 mode"
• "What tools does the Proxies.sx MCP have?"
• "How do I scrape with mobile IPs from Claude / Cursor?"
• "Use x402 to mint a proxy from my agent"
• "My agent wallet balance is low — top up the session"

If the user mentions any of: @proxies-sx/mcp-server, MCP proxy, x402 MCP, agent-driven proxy buying, AGENT_WALLET_KEY, PROXIES_API_KEY env var, psx_ keys, pak_ keys (in MCP context), or mcp.json configuration — this skill applies.

Decide the mode FIRST

Before installing or generating code, ask which mode the user wants. They behave very differently.

Mode A — API Key (44 tools, requires Proxies.sx account)

Use when the user already has a Proxies.sx account and wants their agent to manage their proxy fleet.

• Tools: account, ports, rotation, billing, crypto payments, support tickets, x402 session management
• Auth: PROXIES_API_KEY=psx_... env var (mint at client.proxies.sx/account)
• Cost: pays from the user's existing account balance

Mode B — x402 Autonomous (17 tools, no account needed)

Use when the user is building an autonomous agent that should pay for its own bandwidth without human intervention.

• Dedicated-proxy tools: x402_get_proxy, x402_get_pricing, x402_wallet_balance, x402_rotate_ip, x402_list_sessions, x402_check_session, x402_list_countries, x402_list_cities, x402_list_carriers, x402_service_status
• Pool Gateway tools: x402_get_pool_access, x402_pool_credit, x402_pool_topup, x402_pool_regenerate, x402_pool_connection, x402_pool_pricing, get_pool_stock
• Auth: AGENT_WALLET_KEY=<base58 Solana key | hex EVM key> env var
• Cost: USDC paid per request from the agent's own wallet (Solana ~$0.0001 gas, Base ~$0.01 gas). $4/GB, metered.

Mode C — Both at once

The MCP server happily exposes both modes simultaneously. Set both env vars; tools that need API key use it, tools that need wallet use that. Many production setups run both.

Install — copy-paste configs

The user just needs one of these blocks in their MCP client's config file. Generate the right one based on their client + chosen mode.

Claude Desktop

File: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)

Mode A (API Key):

{
  "mcpServers": {
    "proxies-sx": {
      "command": "npx",
      "args": ["-y", "@proxies-sx/mcp-server"],
      "env": {
        "PROXIES_API_KEY": "psx_YOUR_API_KEY"
      }
    }
  }
}

Mode B (x402 Autonomous):

{
  "mcpServers": {
    "proxies-sx": {
      "command": "npx",
      "args": ["-y", "@proxies-sx/mcp-server"],
      "env": {
        "AGENT_WALLET_KEY": "your_solana_or_base_private_key",
        "PREFERRED_NETWORK": "solana"
      }
    }
  }
}

Mode C (both): combine both env vars in the same env object.

After editing, fully quit Claude Desktop and reopen — MCP servers are loaded at startup.

Cursor

File: .cursor/mcp.json in the project root.

{
  "mcpServers": {
    "proxies-sx": {
      "command": "npx",
      "args": ["-y", "@proxies-sx/mcp-server"],
      "env": { "PROXIES_API_KEY": "psx_YOUR_API_KEY" }
    }
  }
}

Windsurf

Same JSON shape, in ~/.codeium/windsurf/mcp_config.json.

Cline / Continue / Roo Code

All use the same mcpServers JSON format. Drop the same block into their config (paths vary).

Verify install

npx -y @proxies-sx/mcp-server --help
# Should print version + usage.

If your MCP client has a "Tools" panel, you should see ~61 tools prefixed proxies-sx. If you see 0, the env vars are missing or the binary failed to download — check the client's MCP error log.

Tool catalog

61 tools organized by category. Use the table to pick the right tool for the user's intent.

API Key mode (44 tools)

x402 Autonomous mode (17 tools)

Dedicated proxy (10 tools)

(To extend a dedicated-port session, use calculate_x402_topup / topup_x402_session from the session-management group.)

Pool Gateway access (7 tools) — one credential reaches every country in your tier via the username DSL. v1 tier = mbl ($4/GB, production modems, HTTP :7000).

Pool quality copy: mbl is the production tier. Sticky pins the modem, not the IP — carrier NAT may still re-issue the egress IP. Never claim peer reliability.

Common patterns

Generate code that matches the user's intent. Here are the recipes most users want:

"Buy a proxy and use it" (x402 mode)

1. Tool: x402_get_proxy with country="us", traffic=1, tier="shared"
2. Save the returned sessionToken (x402s_...) and proxy credentials
3. Use the proxy in any HTTP client
4. When done, optional: calculate_x402_topup + topup_x402_session to add traffic

"Buy pool access, one credential for every country" (x402 mode)

1. Tool: x402_pool_pricing — see the tier catalog + username DSL (no wallet needed)
2. Tool: get_pool_stock — check which countries currently have capacity
3. Tool: x402_get_pool_access with traffic_gb=5 (tier defaults to mbl)
4. Use the returned credential, switching country via the username DSL:
   psx_xxx-mbl-us, psx_xxx-mbl-de, ... (HTTP proxy on port 7000)
5. Tool: x402_pool_credit — check remaining GB; x402_pool_topup to add more

"Manage my account's proxies" (API key mode)

1. Tool: list_ports — see what you have
2. Tool: create_port with country="us" — add a new one
3. Tool: get_proxy_connection_string with portId — get formatted URLs
4. Tool: rotate_port — get a new IP on demand
5. Tool: configure_auto_rotation with interval=30 — set up auto IP rotation every 30 minutes

"Refill my proxy session before it expires"

1. Tool: x402_check_session with sessionToken — see remaining traffic + duration
2. Tool: calculate_x402_topup with addTrafficGB=2 — preview cost
3. Tool: topup_x402_session with addTrafficGB=2 + paymentSignature — pay USDC and extend

"Replace an offline port for free" (x402 mode)

1. Tool: list_x402_ports with sessionToken — find offline ones
2. Tool: replace_x402_port with portId — get a new port on a different device (free, max 3/session)

"Top up account balance with crypto" (API key mode)

1. Tool: create_crypto_payment with amount=50 — get a payment URL/QR
2. User pays at the URL with any of 50+ supported coins
3. Tool: check_crypto_payment_status with paymentId — confirm
4. Balance auto-credited

Environment variables

Errors and how to fix them

The server returns structured errors with a retryable boolean and a suggestion field — surface those to the user verbatim when an error happens.

Security non-negotiables

DO NOT skip these. Burn them into any setup the user follows:

1. PROXIES_API_KEY is sensitive. Treat it like a password. Don't paste it in shared chat logs, GitHub gists, or screenshots. If exposed, regenerate it at client.proxies.sx/account.
2. AGENT_WALLET_KEY is even more sensitive. It controls real USDC. Rotate it if exposed; transfer remaining funds to a fresh wallet first.
3. Don't run the MCP server with --inspect or any debugger flag when these env vars are set — heap dumps include them.
4. Audit mcp.json files in project repos before committing; the standard pattern is to use a local .env and reference it indirectly, not inline secrets.
5. The pak_ keys (Pool Gateway sub-keys) are scoped per-customer, not per-agent — a leaked pak_ only consumes the reseller's pool, not the platform's.

Pricing rule

Wholesale rates are platform-configurable and change. Don't hardcode dollar amounts when the user asks "how much does X cost". Instead:

• For a precise live answer: Tool: get_pricing (API key mode) or x402_get_pricing (x402 mode).
• For ballpark guidance: tell the user "the live rate is in your client.proxies.sx dashboard or the /v1/x402/pricing endpoint — pin nothing in code".

Reference files in the repo

Smoke test (run before reporting "done")

After setting up, verify the MCP client actually sees the tools.

# 1. Verify the package installs and runs
npx -y @proxies-sx/mcp-server --help
# Should print version + usage info.

# 2. (Optional) Run a single tool via curl-equivalent — only works if the MCP
#    client exposes a way to call tools directly. Most don't, so the real test
#    is asking your AI: "List my proxies via proxies-sx.list_ports"

In Claude Desktop / Cursor: ask the agent to call a tool and watch for the proxies-sx tool icon to appear in the response.

Checklist before handing off

• User has psx_* and/or AGENT_WALLET_KEY env vars set
• MCP client config file has the proxies-sx entry
• Client fully restarted (not just window reload)
• User can call at least one tool successfully
• User knows where to mint a fresh API key if leaked: client.proxies.sx/account
• User knows pricing is live (don't quote stale numbers)

Links

• npm: https://www.npmjs.com/package/@proxies-sx/mcp-server
• Source: https://github.com/bolivian-peru/proxies-sx-mcp-server
• Customer dashboard MCP page: https://client.proxies.sx/mcp-server
• Master Proxies.sx skill: https://agents.proxies.sx/skill.md
• LLM-friendly API reference: https://api.proxies.sx/v1/reseller/docs/llm
• Telegram support: @proxyforai