Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

VS Code Github Copilot calling create_pull_request_with_copilot on remote MCP using fine-grained PAT gets 401

Aperta
#942 7 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github, vscode

Direzione di ricerca

Inizia riproducendo create_pull_request_with_copilot sull’endpoint MCP remoto di Copilot usando la configurazione di VS Code e il fine-grained PAT descritti nell’issue. Confrontalo con list_branches e con l’endpoint MCP repos, quindi traccia il flusso di autenticazione; il lavoro è completato quando la funzione restituisce un URL di pull request invece di una risposta 401.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Describe the bug

The create_pull_request_with_copilot function from the remote GitHub MCP server (https://api.githubcopilot.com/mcp/x/copilot) consistently returns "API returned status 401: Unauthorized" even when authentication appears to be properly configured. This affects the ability to create pull requests programmatically through GitHub Copilot's MCP integration.

Affected version

Remote GitHub MCP Server: https://api.githubcopilot.com/mcp/x/copilot
(This is the hosted service, not the self-hosted Docker version)

Steps to reproduce the behavior
  1. Create fine grained PAT

    Repository access
     This token has access to all repositories owned by the organization.
    Organization permissions
     Read access to organization administration, organization copilot seat management, and organization private registries
    Repository permissions
     Read access to metadata
     Read and Write access to actions, administration, code, codespaces, issues, pull requests, and workflows
    
  2. Make sure the owner of the PAT has a copilot seat and the copilot coding agent is enabled for the target repositories

    • I was able to assign a task to the coding agent using github.com UI in the target repo and get a pull request from it.
  3. Make sure other tools work with the PAT

    • I tested list_branches on the target repositories with the PAT and it worked
  4. Configure VS Code with GitHub Copilot authentication a the remote MCP server at https://api.githubcopilot.com/mcp/x/copilot

    "github_copilot": {
        "type": "http",
        "url": "https://api.githubcopilot.com/mcp/x/copilot",
        "headers": {
         "Authorization": "Bearer ${github_pat}"
        }
    },
    
  5. Call mcp_github_copilo_create_pull_request_with_copilot with valid parameters:

    {
        "owner": "org",
        "repo": "repo", 
        "base_ref": "release/2025.8.21",
        "title": "Fix bug",
        "problem_statement": "Fix this bug..."
    }
    
  6. Observe the 401 Unauthorized error response

    {
        "kind": "toolInvocationSerialized",
        "invocationMessage": {
        "value": "Running Perform task with GitHub Copilot coding agent",
        "isTrusted": false,
        "supportThemeIcons": false,
        "supportHtml": false
        },
        "pastTenseMessage": {
        "value": "Ran Perform task with GitHub Copilot coding agent ",
        "isTrusted": false,
        "supportThemeIcons": false,
        "supportHtml": false
        },
        "originMessage": {
        "value": "[github\\_copilot \\(MCP Server\\)](command:workbench.mcp.showConfiguration?%255B%2522mcp.config.usrlocal%2522%252C%2522mcp.config.usrlocal.github_copilot%2522%255D)",
        "isTrusted": true,
        "supportThemeIcons": false,
        "supportHtml": false
        },
        "isConfirmed": true,
        "isComplete": true,
        "resultDetails": {
        "input": "{\n  \"owner\": \"org\",\n  \"repo\": \"repo\",\n  \"base_ref\": \"release/2025.8.21\",\n  \"title\": \"Fix bug\",\n  \"problem_statement\": \"Fix bug...\"\n}",
        "output": [
            {
            "type": "embed",
            "isText": true,
            "value": "API returned status 401: Unauthorized\n"
            }
        ],
        "isError": true
        },
        "toolSpecificData": {
        "kind": "input",
        "rawInput": {
            "owner": "org",
            "repo": "repo",
            "base_ref": "release/2025.8.21",
            "title": "Fix bug",
            "problem_statement": "Fix bug..."
        }
        },
        "toolCallId": "eb01d33e-8afb-4b0e-b014-5a1150131e91",
        "toolId": "mcp_github_copilo_create_pull_request_with_copilot"
    }   
    
Expected vs actual behavior

Expected: The function should successfully create a pull request using GitHub Copilot's PR creation capabilities, returning a success response with the PR URL.

Actual: The function returns "API returned status 401: Unauthorized" indicating authentication failure, despite having valid GitHub Copilot authentication configured in VS Code.

Additional Context
  • Using the remote GitHub MCP server at https://api.githubcopilot.com/mcp/x/copilot (not Docker version)
  • The create_pull_request_with_copilot function is only available in this remote server, not in the self-hosted version
  • GitHub Copilot is properly authenticated in VS Code and other Copilot features work correctly
  • Other GitHub MCP functions from the repos server (https://api.githubcopilot.com/mcp/x/repos) work correctly with the same authentication setup
  • The issue appears to be specific to the Copilot MCP server endpoint or the PR creation function
  • This blocks automated workflows that depend on programmatic PR creation through Copilot
  • The error suggests either insufficient permissions for the Copilot service or an issue with the authentication flow between the MCP client and the remote Copilot server
Lingua principale
Go
Stelle
33.1k
Fork
5k
Merge medio
2g 1h
PR unite (30g)
25

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/github-mcp-server

Tutte le issue di github/github-mcp-server

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.