Request: Replace GitHub CLI usage with direct HTTP requests to support proxy environments

[gerson-vfs]

Description:

I attempted to install and use the tool but encountered an issue related to the GitHub CLI.
In my company’s network environment, we must use an HTTP proxy to access GitHub. Without the proxy configured, we cannot reach GitHub endpoints from within the corporate network.

Unfortunately, the GitHub CLI does not natively and easily support configuring an HTTP proxy. This limitation prevents us from performing operations such as creating pull requests through the CLI when working behind a proxy.

Proposed Change:

Replace the current implementation that relies on the GitHub CLI with a direct HTTP request approach (using the GitHub REST API).
This would:

• Remove the dependency on the GitHub CLI.
• Allow proxy configuration through standard environment variables or request libraries.
• Improve compatibility with corporate environments that restrict direct access to GitHub.

Expected Behavior:

The tool should be able to open pull requests directly through HTTP requests (e.g., using the GitHub API) even when behind a proxy, as long as the proxy configuration is properly set.

Environment Details:

• Corporate environment with HTTP proxy required for GitHub access
• GitHub CLI currently blocked or misconfigured due to proxy restrictions

Additional Context:

Please consider implementing this change to make the tool more flexible for users working behind enterprise proxies.

[Farenheith]

Thank you for the suggestion. I'll take a look into it ASAP.

[Farenheith]

This was solved in #10. Now, gh cli is still used to obtain an authentication token, but all HTTP communication is done by calling the github api. I'll appreciate if you test it in your proxied environment

[gerson-vfs]

Comment:

Thanks for the quick fix in PR #10 — I really appreciate that the GitHub CLI dependency was removed. That solved part of the problem and made the workflow much easier 👏

However, I’m still facing issues when running the tool behind a corporate HTTP proxy. Even though the implementation now uses direct HTTP requests to the GitHub API, it seems the proxy settings are not being respected.

Here’s the error returned by the tool:

Although you appear to have the correct authorization credentials, the `xyz` organization has an IP allow list enabled, and your IP address is not permitted to access this resource.

(Reference https://docs.github.com/rest/pulls/pulls#create-a-pull-request)

This error indicates that the HTTP requests are still being sent directly from my machine’s public IP instead of being routed through the corporate proxy, which is required for GitHub access in my environment.

Additional Context From My Tests

• Installed the package globally using:
  npm i -g mcp-pr-command
• Configured VS Code to use the globally installed package.
• GitHub Copilot was able to communicate with the MCP service normally, confirming that the MCP server itself is running correctly.
• The only failure occurs when the MCP tries to perform the HTTP request to create the pull request — which fails because the proxy is not being used.

Given this, it looks like the HTTP client used in the tool is not honoring system or environment proxy settings (e.g., HTTP_PROXY, HTTPS_PROXY, or OS proxy configuration).

Request

Would it be possible to update the HTTP request logic so that it respects system proxy settings?
That would ensure the tool works properly in corporate environments where GitHub access is only allowed through a proxy.

Thanks again for the fast response and for removing the GitHub CLI dependency — the remaining issue now seems to be purely proxy-related.

[Farenheith]

Could you help me with that?
Given you experiencing the problem, you can try out a solution to see if it works and open a pr following that.

Here's a little snippet to follow (to change in gh-client-api.ts):

import { HttpsProxyAgent } from 'https-proxy-agent';
...
...
private async getOctokit(): Promise<Octokit> {
  if (!this.octokit) {
    const token = await run('gh auth token');
    
    let octokitOptions = { auth: token };
    
    const proxyUrl = process.env.HTTPS_PROXY || process.env.https_proxy || process.env.HTTP_PROXY || process.env.http_proxy;
    if (proxyUrl) {
      const { HttpsProxyAgent } = await import('https-proxy-agent');
      const agent = new HttpsProxyAgent(proxyUrl);
      octokitOptions.request = { agent };
    }
    
    this.octokit = new Octokit(octokitOptions);
  }

  return this.ocktoki;
}

You may even use "context" variable to pass a proxy config to the server on initialization if env is not an option.
Could you try to implement this solution and test it locally?

Here's how you can run and test it:

		"mcp-pr-command": {
			"type": "stdio",
			"command": "node",
			"args": [
				"~/personal/mcrp-pr-command/local-test.js"
			]
		},

local-test.js may be something like this:

#!/usr/bin/env node
const { execSync } = require('child_process');
const fs = require('fs');
const path = require('path');
const ini = require('ini');

function checkBranch(branch, defaultValue) {
  try {
    execSync(`git show-ref --verify --quiet refs/heads/${branch}`, { cwd });
    return branch;
  } catch {
    return defaultValue;
  }
}

/** @type {import('mcp-pr-command').McpPRCommandOptions} */
const options = {
  cardLinkWebSite: 'https://your-board-site',
  cartPathLinkReplacePattern: 'ctrl_board/$2/cards/$1/details',
  branchCardIdExtractPattern: '[\\w\\-]+/(\\d+)-(\\d+)',
  complementaryMcpDescription: 'Used for the company I work for',
}

const mcpOptionsStr = JSON.stringify(options).replace(/\\/g, '\\\\').replace(/"/g, '\\"');
execSync(`node  ~/personal/mcrp-pr-command/libs/mcp-pr-command/dist/cli.js --mcp-options="${mcpOptionsStr}"`, { stdio: 'inherit' });