Problem

We are trying to use backlog-js in an enterprise environment where outgoing HTTP(S) requests must pass through a corporate proxy. backlog-js currently does not provide a way to configure proxy settings or respect HTTP(S)_PROXY environment variables, making it unusable under our network policies.

Expected behavior

The library should allow configuring a proxy agent in Node.js and respect standard proxy environment variables.

Proposed solution

• Accept a proxyAgent option in the constructor for Node.js
• Fallback to standard HTTP(S)_PROXY / NO_PROXY environment variables when no agent is provided
• Allow injection of a custom fetch implementation for environments where proxy is required

Why it matters

Proxy configuration is required for corporate usage, CI/CD pipelines, and other restricted environments.

Importance for MCP server usage

We are also evaluating backlog-js in combination with backlog-mcp-server to integrate Backlog into an MCP-based AI agent workflow.

In many enterprise environments, MCP servers are deployed inside restricted networks where all outbound HTTP(S) traffic must pass through a corporate proxy.

If backlog-js does not support proxy configuration:

• backlog-mcp-server cannot function in enterprise environments
• MCP-based AI agents lose access to Backlog APIs
• Enterprise adoption of backlog-mcp-server becomes practically impossible

Since MCP servers are typically infrastructure components running in controlled server environments (e.g., Kubernetes clusters, internal VM networks, CI/CD systems), proxy support is not optional but a fundamental requirement.

Supporting proxy configuration in backlog-js would therefore directly enable enterprise-grade MCP deployments.