AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam4d agoNeeds helpSolved

    mcp-remote ECONNRESET behind corporate proxy: does it respect http_proxy/https_proxy?

    Using mcp-remote 0.1.18 via npx on Ubuntu under WSL2 with Node v24.4.0 and npm 11.4.2, the connection to a remote MCP server fails with ECONNRESET behind a corporate proxy. The debug log shows a direct connection attempt, even though http_proxy/https_proxy and npm proxy settings were configured. Is proxy support available, and what works?

    Originally asked on GitHub: https://github.com/punkpeye/mcp-remote/issues/124

    4 answers

    • Best answerAgentArmorHQ teamTeam4d ago

      Status: the issue is closed as completed, and a pre-release build from PR #131 was reported to work. The thread does not show which release contains the change, so use the build below until a published version is confirmed.

      A collaborator suggested trying the PR #131 build published on pkg.pr.new instead of the npm tag:

      bash
      npx https://pkg.pr.new/mcp-remote@131

      With this build, a commenter ran it against https://mcp.atlassian.com/v1/sse (opens external site). The log showed the browser-based OAuth flow completing, the HTTP-first POST returning 404, an automatic fallback to SSE transport, and finally "Proxy established successfully between local STDIO and remote SSEClientTransport." The thread does not confirm this on the original reporter's corporate network or with the original server.

      The thread does not show the exact command or argument order beyond the line above, so check the PR for usage details. Debug output is written to ~/.mcp-auth/, so on a shared machine make sure that directory is restricted to your user.

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What a GitHub user tried on GitHub (Didn't work)

      Set http_proxy, https_proxy, HTTP_PROXY and HTTPS_PROXY, npm config proxy and https-proxy, and no_proxy exclusions, then ran npx -y mcp-remote@latest https://mcp.company.com/ --debug. It still attempted a direct connection and failed with ECONNRESET.

      Source: https://github.com/punkpeye/mcp-remote/issues/124 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @geelen tried on GitHub (Outcome unclear)

      A collaborator suggested running npx https://pkg.pr.new/mcp-remote@131 to test the PR #131 build. The thread does not say whether the original reporter ran it.

      Source: https://github.com/punkpeye/mcp-remote/issues/124#issuecomment-3226378403 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @rohanpower tried on GitHub (Worked)

      A commenter ran npx https://pkg.pr.new/mcp-remote@131 against https://mcp.atlassian.com/v1/sse (opens external site). The HTTP-first POST returned 404, the client fell back to SSE transport, and the log ended with "Proxy established successfully".

      Source: https://github.com/punkpeye/mcp-remote/issues/124#issuecomment-3226528737 (opens external site)

      Did this work for you?

    Add your answer or comment