Feature request: expose an MCP server so AI agents can interact with PRs and issues
Los mantenedores suelen responder en 1 día
@alexr00 ya está trabajando en esto.
Desde el 16/10/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Summary
Add a Model Context Protocol (MCP) server to the extension so that AI coding agents running inside VS Code (Claude Code, GitHub Copilot extensions, etc.) can programmatically invoke the extension's PR and issue capabilities without a human clicking UI elements.
Motivation
The extension already exposes a rich set of commands through VS Code's command palette. Agents like Claude Code can call vscode.commands.executeCommand, but that requires the agent to be running inside VS Code and to know the exact command IDs. An MCP server would give any MCP-capable agent a stable, discoverable, schema-validated interface, regardless of how it is hosted.
Concretely: when an agent is working a PR (rebasing, fixing CI, iterating on review feedback) it currently has to shell out to gh CLI for everything. If the extension exposed an MCP server the agent could instead call typed tools and get back structured data that matches what the extension already knows — open diffs, review threads, CI status, notifications — without leaving the editor context.
Proposed tool groups
The list below was derived by querying contributes.commands from the extension's package.json and grouping commands by functional area. Each group maps naturally to one or more MCP tools.
Pull request lifecycle
| MCP tool | Source commands |
|---|---|
create_pull_request |
pr.create, pr.pushAndCreate, pr.createPrMenuCreate, pr.createPrMenuDraft |
get_pull_request |
pr.openDescription, pr.refreshPullRequest, pr.refreshList |
checkout_pull_request |
pr.pick, pr.checkoutByNumber, pr.checkoutFromDescription, pr.pickInWorktree, pr.pickInWorktreeFromDescription |
merge_pull_request |
pr.merge, pr.acceptMerge, pr.createPrMenuMerge, pr.createPrMenuMergeWhenReady, pr.createPrMenuRebase, pr.createPrMenuSquash |
mark_ready_for_review |
pr.readyForReview, pr.readyForReviewAndMerge |
get_pull_request_diff |
pr.openChanges, pr.openDiffView, pr.showDiffAll, pr.showDiffSinceLastReview |
add_to_stack |
pr.addToStack |
generate_title_and_description |
pr.generateTitleAndDescription |
Review
| MCP tool | Source commands |
|---|---|
start_review |
pr.startReview, pr.preReview |
submit_review |
review.approve, review.requestChanges, review.comment |
create_review_comment |
pr.createComment, pr.createSingleComment, pr.addFileComment |
edit_review_comment |
pr.editComment, pr.saveComment, pr.deleteComment |
resolve_review_thread |
pr.resolveReviewThread, pr.unresolveReviewThread |
create_suggestion |
pr.makeSuggestion, review.createSuggestionFromChange, review.createSuggestionsFromChanges |
apply_suggestion |
pr.applySuggestion, pr.applySuggestionWithCopilot |
mark_file_viewed |
pr.markFileAsViewed, pr.unmarkFileAsViewed, pr.resetViewedFiles |
diff_with_pr_head |
review.diffWithPrHead, review.diffLocalWithPrHead, pr.diffOutdatedCommentWithHead |
Issues
| MCP tool | Source commands |
|---|---|
create_issue |
issue.createIssue, issue.createIssueFromSelection, issue.createIssueFromClipboard, issue.createIssueFromFile |
get_issue |
issue.openIssue, issue.openDescription, issue.getCurrent |
start_working_on_issue |
issue.startWorking, issue.startWorkingBranchPrompt |
stop_working_on_issue |
issue.stopWorking |
copy_issue_link |
issue.copyIssueUrl, issue.copyIssueNumber, issue.copyGithubPermalink |
Notifications
| MCP tool | Source commands |
|---|---|
list_notifications |
notifications.refresh |
mark_notification_read |
notification.markAsRead, notifications.markPullRequestsAsRead |
mark_notification_done |
notification.markAsDone, notifications.markPullRequestsAsDone |
summarize_notification |
notification.chatSummarizeNotification |
Metadata helpers (new PR creation)
| MCP tool | Source commands |
|---|---|
add_assignees |
pr.addAssigneesToNewPr |
add_reviewers |
pr.addReviewersToNewPr |
add_labels |
pr.addLabelsToNewPr |
add_milestone |
pr.addMilestoneToNewPr |
add_projects |
pr.addProjectsToNewPr |
Implementation notes
- The MCP server can be registered via
vscode.lm.registerMcpServer(available since VS Code 1.99) and activated lazily when an MCP-capable client connects. - For read-only tools (
get_pull_request,list_notifications, …) the server can delegate directly to the extension's existing data models — no extra GitHub API calls needed. - For write tools (
submit_review,merge_pull_request, …) a confirmation prompt to the user would be appropriate before the first call, similar to how Copilot Edits asks for approval. - The
github.api.preloadPullRequestinternal command suggests there is already an API surface; the MCP server could build on that.
Alternatives considered
- Using the
ghCLI: works but has no awareness of what the extension has already fetched; forces duplicate API calls and loses the extension's diff/comment context. - VS Code Language Model tools: the
vscode.lmtool registration API is closer but limited to Copilot Chat inside VS Code; MCP reaches agents running outside the editor.
Related
- MCP spec: https://modelcontextprotocol.io/
- VS Code MCP extension hosting docs: https://code.visualstudio.com/api/extension-guides/mcp
- Lenguaje dominante
- TypeScript
- Estrellas
- 2.6k
- Forks
- 805
- Merge medio
- 2 d 9 h
- PR fusionados (30 d)
- 43
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/vscode-pull-request-github
-
Issue 3 — DocumentationAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
microsoft/vscode-pull-request-github#8792 ·
Los mantenedores suelen responder en 1 día
-
GitHub releases lag behind VS Code Marketplace by multiple versionsPosiblemente ocupada @alexr00 la tomó hoy. Abierto
microsoft/vscode-pull-request-github#9069 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Review requests and review dismissals are missing from the PR conversation timelinePosiblemente ocupada @alexr00 la tomó hoy. Abierto
microsoft/vscode-pull-request-github#9068 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Webview L10nPosiblemente ocupada @alexr00 la tomó hoy. Abierto
microsoft/vscode-pull-request-github#9067 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Plugin no longer gives access to GitHub issues while using personal account.Posiblemente ocupada @alexr00 la tomó hace 1 día. Abiertoinfo-needed
microsoft/vscode-pull-request-github#9064 · 2 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de microsoft/vscode-pull-request-github
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
aws/agentcore-cli#2606 ·
Los mantenedores suelen responder en 1 día
-
ai-driven-qa bug Cosmetic
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
ai-driven-qa bug claude Minor
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
linagora/twake-mail-admin#301 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
reproduced
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
anomalyco/opencode#56038 · 1 comentario ·
Los mantenedores suelen responder en 1 día