NO_PROXY environment variable not working for MCP server HTTP calls

Resolved 💬 5 comments Opened Sep 25, 2025 by othmane399 Closed Jan 15, 2026

Description

The NO_PROXY environment variable feature introduced in v1.0.93 doesn't seem to work for HTTP calls made to configured MCP servers.

Expected Behavior

When NO_PROXY is set with specific hostnames/IPs, all HTTP requests from Claude Code should bypass the proxy for those destinations, including requests to MCP servers.

Actual Behavior

NO_PROXY appears to only affect main API calls but not the HTTP requests made to MCP servers, which still go through the proxy even when the MCP server hostname/IP is listed in NO_PROXY.

Environment

  • Claude Code version: v1.0.93+
  • Using proxy configuration with MCP servers

Impact

Users behind corporate proxies cannot properly configure MCP servers that should bypass the proxy, limiting the functionality of Claude Code in enterprise environments.

Suggested Fix

Ensure that the NO_PROXY environment variable is respected by all HTTP client instances used throughout Claude Code, including those used for MCP server communication.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗