1001Proxy MCP Server

Overview

The 1001Proxy MCP Server connects MCP-compatible clients such as Claude Desktop, Claude Code, Cursor, Windsurf, and generic stdio clients to 1001Proxy account, billing, and proxy-order APIs.

Installation

Recommended no-install launch from the official docs:

npx -y @1001proxy-mcp/server

The docs also show global install:

npm install -g @1001proxy-mcp/server

Configuration

Set PROXY_API_KEY in the MCP client environment. The API key is required; the server exits if it is missing or blank. PROXY_API_URL is optional and can override the API base URL for staging or self-hosted instances. The published package source defaults to https://1001proxy.io and appends /api/v1/... endpoint paths internally; the public docs page also lists https://api.1001proxy.io/api/v1 as an API URL default, so overrides should be tested carefully.

Example MCP client configuration:

{
  "mcpServers": {
    "1001proxy": {
      "command": "npx",
      "args": ["-y", "@1001proxy-mcp/server"],
      "env": {
        "PROXY_API_KEY": ""
      }
    }
  }
}

Capabilities

The docs and package describe 12 tools: get_account, list_proxy_types, get_reference_data, calculate_order, create_order, list_orders, get_order, get_proxies, download_proxies, extend_order, get_transactions, and get_deposit_addresses.

Operational Notes

create_order and extend_order can debit account balance and should require explicit user confirmation in the agent loop. The 1001Proxy API may return 429 rate-limit responses and 402 insufficient-balance responses. Node.js 18+ and npm/npx access to the npm registry are required for the documented npm launch.