Free tools Windows power users keep installed
One-click scans. No signup required.
Configure a proxy where the process making the network request can use it. If the coding agent itself needs to reach its API through a proxy, set that up in the agent’s supported runtime or host environment. If an MCP server needs its own proxy setting, configure that server’s launch environment or plugin entry when the host supports it. These are distinct boundaries: setting one does not guarantee that the other inherits it.
Decide by identifying which process connects
“Proxy configuration” can refer to two different outbound connections: the coding agent’s own traffic, or traffic initiated by an MCP server. Start by identifying the client process that opens the connection, then configure the proxy at the layer that owns that process.
| What needs the proxy | Preferred configuration owner | Reason |
|---|---|---|
| The coding agent’s API or other client traffic | The agent process, shell, service manager, or host-level setting supported by that agent | The agent client initiates those requests. Anthropic documents HTTP and HTTPS proxy variables for Claude Code specifically: Claude Code corporate proxy configuration. |
| One MCP server’s network traffic or runtime requirements | That server’s configuration or plugin entry, if the host can pass the required environment values to the server | The setting belongs with the process that launches and runs the server. VS Code documents MCP server commands, arguments, and optional environment variables in plugin configuration: Agent plugins in VS Code. |
| A proxy policy for tools in a managed development environment | An organization-approved machine, container, or remote-host configuration, subject to each product’s documented support | A managed environment can provide settings to processes running there, but that does not establish identical proxy behavior for every agent, host, or operating system. |
When the agent itself needs the proxy
Set the proxy in the environment that starts the coding agent, or through another configuration mechanism the agent officially supports. Do not assume that an MCP server’s environment variables will route the agent’s own API requests; the server and the agent may run as separate processes.
Claude Code example
Anthropic documents HTTP_PROXY and HTTPS_PROXY for Claude Code’s HTTP/HTTPS proxy configuration. Anthropic also says Claude Code currently does not support NO_PROXY or SOCKS proxies. In practical terms, do not rely on NO_PROXY to bypass the configured proxy for selected destinations, and do not expect a SOCKS endpoint to work through this documented configuration.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors#1 Best Overall
For basic authentication, Anthropic’s documented pattern places credentials in the proxy URL, but the guide warns against hardcoding proxy passwords in scripts and recommends secure credential storage. For custom proxy certificates, the guide documents SSL_CERT_FILE and NODE_EXTRA_CA_CERTS. Check Anthropic’s current guide for the service domains that must be reachable through the proxy and for any version-sensitive requirements.
When an MCP server needs the proxy
Put server-specific settings where the host defines that server’s launch configuration. This can include its command, arguments, and environment, provided the host supports passing the needed values to the process. A plugin entry is useful for settings tied to that plugin’s server; it is not automatically a setting for the coding agent’s separate outbound traffic.
Rank #2
- Used Book in Good Condition
VS Code agent plugins
VS Code’s agent-plugin guide places MCP server definitions in mcp.json at the plugin root. A server entry can specify a command, arguments, and optional environment variables. That makes the entry a plausible place for a proxy value needed by that particular server process.
VS Code workspace and remote configuration
VS Code also documents MCP configuration in .vscode/mcp.json, including inputs for sensitive values. In a remote window, the configuration location and environment variables resolve in the remote environment. If a remote host or container launches the server, check that environment—not just the local desktop’s variables—to confirm what the server receives. See the VS Code MCP configuration reference.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #3
Protect credentials and account for certificate trust
- Keep secrets out of committed files. Do not put reusable proxy passwords in a repository or plugin configuration that will be shared. Use the host’s supported secret-handling or input mechanism; VS Code documents inputs for sensitive MCP configuration values.
- Check which process receives credentials. A credential available to the agent is not necessarily available to a separately launched MCP server, and the reverse is also true.
- Verify certificate trust for the connecting process. With a TLS-intercepting corporate proxy, the relevant client must trust the organization’s certificate bundle. For Claude Code, Anthropic documents
SSL_CERT_FILEandNODE_EXTRA_CA_CERTS; other products may use different mechanisms.
Validate the actual host and deployment
- Map the connection. Determine whether the agent, an MCP server, or both make the outbound request that must pass through the proxy.
- Choose the corresponding boundary. Configure agent traffic in the supported agent or runtime environment; configure server traffic in that server’s launch configuration or the managed environment that starts it.
- Check inheritance and support. Confirm that the process receives the intended variables and that the selected client supports the proxy scheme, authentication method, certificate setup, and any required bypass behavior.
- Test the deployed combination. Validate the exact agent version, host, remote or container setup, and MCP server. A successful test in a local shell does not establish that a remote server process receives the same environment.
Proxy behavior is product-specific. The examples above establish documented behavior for Claude Code and VS Code, not a universal proxy variable or field for every coding agent, plugin, MCP host, or server. For background on MCP documentation servers, see OpenAI’s MCP documentation; it does not establish proxy behavior for other products.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




