Claude proxy
Claude proxy is the Claude ISP: a dedicated native IP in the US, Frankfurt, Japan or London, 15 PTC for 30 days, HTTP for Claude Code — and Anthropic's region rules.
View options and pricingSet Claude Code up behind an HTTP proxy: the variables it reads, why SOCKS fails, how to keep the setting for background agents and how to check it.
The table lists the variables and what the documentation says about each. Lowercase names work as well. Claude Code uses the first one that is set, in this order: https_proxy, HTTPS_PROXY, http_proxy, HTTP_PROXY. Its WebSocket connections to localhost, ::1 and 127.0.0.0/8 never go through the proxy, so you do not need a loopback entry in NO_PROXY.
| Item | What it does | What the documentation says |
|---|---|---|
| HTTPS_PROXY | Proxy for HTTPS traffic | Marked "recommended"; the example is https://proxy.example.com:8080 |
| HTTP_PROXY | Proxy for HTTP traffic | Use it "if HTTPS not available"; the example is http://proxy.example.com:8080 |
| NO_PROXY | Hosts that skip the proxy | Space-separated or comma-separated; * skips the proxy for all requests |
| NODE_EXTRA_CA_CERTS | Extra certificate authority file | Path to a PEM file, for proxies that inspect TLS |
Summarised from the Claude Code documentation page cited below, read on 22 October 2026. Quoted phrases are the documentation's own.
The documentation states it directly: Claude Code does not support SOCKS proxies. A SOCKS5 endpoint will not work here, so use a proxy that speaks HTTP. For proxies that need advanced authentication such as NTLM or Kerberos, the documentation suggests an LLM gateway service instead.
For basic authentication, put the credentials in the URL, as in the example below.
The documentation warns against hardcoding passwords in scripts and recommends environment variables or secure credential storage instead. If the password contains characters such as @, : or /, percent-encode them in the URL, as in any URL with credentials.
export HTTPS_PROXY=http://username:[email protected]:8080Example only: replace the placeholder values with your own.
Variables exported in your shell are read once at startup, so a running session does not pick up later changes. Set them first, then launch Claude Code from the same shell.
In Command Prompt the session form is set HTTPS_PROXY=http://username:[email protected]:8080.
# macOS, Linux, WSL
export HTTPS_PROXY=http://username:[email protected]:8080
claudeExample only: replace the placeholder values with your own.
# Windows PowerShell
$env:HTTPS_PROXY = "http://username:[email protected]:8080"
claudeExample only: replace the placeholder values with your own.
Every environment variable on that documentation page can also be set in settings.json. That matters for background agents. A per-user supervisor process hosts sessions started with claude agents, --bg and /background. It outlives your shell and inherits the environment of whichever shell started it first, so a variable exported only in your shell reaches background agents by luck. The documentation says settings are the only configuration that reaches every background session.
Put the block below in ~/.claude/settings.json, or in managed settings if an administrator deploys them.
{
"env": {
"HTTPS_PROXY": "http://username:[email protected]:8080"
}
}Example only: replace the placeholder values with your own.
By default Claude Code trusts its bundled Mozilla certificates and your operating system's certificate store. The documentation says enterprise TLS-inspection proxies work without extra configuration when their root certificate is installed in the OS trust store and Claude Code can read it. The native installer always can. npm installs need Node 22.15 or later. Otherwise point NODE_EXTRA_CA_CERTS at the certificate file, as shown below.
This only matters for a proxy that inspects traffic. A plain forward proxy does not need it.
export NODE_EXTRA_CA_CERTS=/path/to/ca-cert.pemExample only: replace the placeholder values with your own.
Claude Code does not validate most network settings when it reads them. The one exception is the proxy URL: if it cannot parse the value, for example because http:// is missing, it stops at launch with an error naming the variable to fix. To confirm the rest:
• Run /status in an interactive session. The Proxy row shows the active proxy URL, and marks a value it cannot parse as invalid and ignored.
• Start with claude --debug. The log goes to ~/.claude/debug/<session-id>.txt, or to a path you set with --debug-file.
• Test the proxy itself from a terminal with the command below. It shows the exit IP, country and network that sites will see.
The fields ip, country, city and org are explained in the guide on how to check your proxy's IP, country and ISP.
curl -x http://username:[email protected]:8080 https://ipinfo.io/jsonExample only: replace the placeholder values with your own.
• Claude Code stops at launch: the proxy URL has no scheme. Write the full http://... URL.
• 407 Proxy Authentication Required: the proxy rejected the username or password. Copy them again instead of retyping them.
• A SOCKS5 address: not supported. Use an HTTP proxy.
• Works in your shell but not in a background agent: set the variable in settings.json.
• A firewall in between: the documentation lists the hosts Claude Code needs, including api.anthropic.com, claude.ai and platform.claude.com. Allow them in your proxy rules.
MCP adds tools to Claude Code. With the proxy302-mcp server, Claude Code can get a Proxy302 proxy and fetch pages through it from the chat, without switching to the console. The command below adds it for all your projects.
proxy302-mcp is the official Proxy302 MCP server, open source on GitHub and maintained by the Proxy302 team. Proxy302 also runs it at https://proxy302.com/v1/mcp: clients that can send an Authorization header, such as Claude Code, Cursor and VS Code, connect with an API key and install nothing.
This is a separate setting from the rest of this page. The proxy that Claude Code itself uses to reach Anthropic is set with HTTPS_PROXY, as described above; the MCP server's tools have their own settings, and installing the server does not change how Claude Code connects. The guide to the Proxy302 MCP server covers the tools, the other clients and the limits.
claude mcp add proxy302 -s user -e PROXY302_API_KEY="<key id>:<secret>" -- npx -y github:proxy302/proxy302-mcpReplace <key id>:<secret> with your Proxy302 API key. -s user makes the server available in every project; without it, Claude Code adds it to the current project only.
A static ISP proxy fits this task: the IP stays fixed while the lease runs and does not rotate, and you choose HTTP at purchase, which is the protocol Claude Code needs. The Claude preset in the console starts on SOCKS5, so switch Protocol to HTTP before you generate. The page on Claude proxies has the preset and the full setup. The table below is our latest hourly check of Claude through exits in seven countries, with the network of each exit and the response time of the site.
| Item | Network (ISP) | ASN | Response, ms |
|---|---|---|---|
| United States | Verizon Business | AS5650 | 1729 |
| United Kingdom | British Telecommunications Limited | AS2856 | 1556 |
| Germany | Marco Bungalski GmbH | AS59790 | 1262 |
| Japan | Sony Network Communications Inc. | AS2527 | 2994 |
| Singapore | MobileOne Ltd. Mobile/Internet Service Provider Singapore | AS4773 | 3388 |
| Brazil | Claro NXT Telecomunicacoes Ltda | AS28573 | 2244 |
| Indonesia | PT INDONESIA COMNETS PLUS | AS9341 | 1225 |
Hourly check of the Proxy302 probe, 22 October 2026, 14:18 UTC: one request to Claude per country through a dynamic residential exit, using the public Proxy302 entry. Only the first three octets of an IP are public. One sample per country, not an average; later checks will differ.
Open the static ISP page, choose the country, set Protocol to HTTP, choose the term and the quantity, then click Review cost and generate.
Open My assets and copy HOST, PORT, USERNAME and PASSWORD. The Tools & checks page shows a ready example with your own endpoint.
Set HTTPS_PROXY=http://USERNAME:PASSWORD@HOST:PORT in your shell, or in the env block of ~/.claude/settings.json.
Start claude, run /status, and check the exit with the curl command above.
A static ISP IP costs US$0.50 for one day and US$7.99 for 30 days, about US$0.27 per day, and the price is the same in every country. Availability changes daily and is shown on the order page. There is no free trial, and the smallest purchase is one IP for one day. A proxy changes only the network exit: Anthropic's rules on supported regions still apply to you, as the guide to Claude, ChatGPT and Gemini supported countries explains.
| Item | Price | Protocols | Locations | Fits agent work like |
|---|---|---|---|---|
| Rotating residential | From US$1.50 per GB (Budget line); US$5 per GB (Premium line); lower per GB in larger packages | HTTP, SOCKS5 | 195+ countries and regions; state and major city on lines that support it | Browsing and research agents, data collection |
| Static ISP, per IP | US$0.50 for 1 day, US$7.99 for 30 days, the same in every country | HTTP or SOCKS5, chosen per IP | 30 countries on the order form; stock changes daily | One fixed IP for each account an agent signs in to |
| ISP for AI subscriptions | Per 30 days: Claude 15 PTC, GPT / Grok 10 PTC, Gemini 8 PTC; the first order in each tier is 50% off | HTTP or SOCKS5 | Claude: US, UK, DE, JP. GPT / Grok: US, UK, FR, JP, KR. Gemini: US, UK, FR, JP | Coding tools and agents signed in to ChatGPT, Claude, Gemini or Grok |
| Datacenter, per IP | US$0.25 for 1 day, US$3.99 for 30 days | HTTP or SOCKS5, chosen per IP | 8 countries | API calls and tool traffic where the IP type does not matter |
| proxy302-mcp | Free, open source (MIT) | MCP over stdio, started with npx | Uses the products above | Lets Claude Code, Codex, Cursor and other MCP clients get a proxy and fetch pages through it |
Prices are in PTC, paid from the wallet; 1 PTC = US$1. There is no free trial: the smallest purchase is 1 GB of rotating residential traffic or one IP for one day. Checked on 4 November 2026.
No. The Claude Code documentation says it does not support SOCKS proxies. Use an HTTP proxy.
Yes. The documentation shows basic authentication in the URL, as in http://username:[email protected]:8080.
Not reliably. The supervisor that hosts them inherits the environment of whichever shell started it first. Set the variables in the env block of ~/.claude/settings.json.
No. A proxy changes only the network exit. Anthropic's supported-regions policy still applies to your account and to where you use it.
Official documentation · Confirmed on:
Read on 22 October 2026: proxy variables and their lookup order, no SOCKS support, basic authentication in the proxy URL, the env block of settings.json and background agents, custom certificate authorities and the OS certificate store, /status, --debug and the hosts Claude Code needs.
Product observation · Confirmed on:
Product facts file of the site (values checked against the console, the backend and the price table on 18-19 October 2026): products, prices in US$ (1 PTC = US$1), lease terms, protocols and ports, countries, quantity limits, no free trial.
Product observation · Confirmed on:
Public JSON of the probe at proxy302.com/live/connectivity/claude.json, read 22 October 2026, 14:18 UTC: one request per exit country through a dynamic residential exit; exit city, ASN, network and response time.
Official documentation · Confirmed on:
Read on 4 November 2026: claude mcp add syntax, the -- separator before the server command, -e for environment variables, and the local (default), project and user scopes.
Product observation · Confirmed on:
README of the official Proxy302 MCP server: install commands, environment variables, the seven tools, the read-only, spend-free scope and the hosted endpoint https://proxy302.com/v1/mcp.
Product observation · Confirmed on:
Public JSON at proxy302.com/v1/proxy/ai-isp/catalog, read 4 November 2026: three tiers (Claude, GPT / Grok, Gemini), price per 30 days in PTC, 50% off the first order in a tier, cities by country.
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.