MCP does not work with remote-ssh and extension installed in host side

未关闭
#319 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
postgresql, typescript, vscode

调研方向

The problem sits where VS Code's remote.extensionKind setting decides which side runs the extension, and where the extension exposes its MCP tools to Copilot. Start from the extension's activation and MCP registration code, then reproduce with the extension forced to ui in a remote-ssh session. Done when the MCP tool appears in the available tools list while the extension runs on the host.

由索引模型根据 Issue 内容生成。

描述

Failing to use MCP tool

I have installed the extension in both my host machine and in the remote-ssh VM I am using it, but because of glibc version incompatibility I added to my User Settings the following:

  "remote.extensionKind": {
    "ms-ossdata.vscode-pgsql": [
      "ui"
    ]
  },

That made the trick and I can use the extension in remote-ssh side, though when trying invoking the MCP tool
it doesn't seem available with the latest copilot harness, at a previous version of copilot after switching to local mode I could invoke it successfully.

This is what I see in the available tools:

Image

To Reproduce

Steps to reproduce the behavior:

  1. Install the extension
  2. Configure it to work in vs-code host side
  3. Try using MCP tool

Expected behavior

MCP tool should be available even when extension is running on host

VS Code version

Version: 1.144.1 (system setup)
Commit: 261c84cb1eddf11235f9e2c921425e9663fbe556
Date: 2026-11-01T07:37:53-08:00
Electron: 43.8.3
ElectronBuildId: 15784459
Chromium: 150.0.7871.250
Node.js: 24.22.1
V8: 15.0.245.31-electron.0
@github/copilot: 1.0.103.r40031404408.gba6c003
@github/copilot-sdk: 1.0.27.40031404408.gba6c003
OS: Windows_NT x64 10.0.26200

** PostgreSQL Version **
v1.32.1

主要语言
没有语言数据
星标
406
派生
35
平均合并
2 小时 47 分钟
30 天内合并 PR
5

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/vscode-pgsql 的其他 Issue

查看 microsoft/vscode-pgsql 的全部 Issue

相似的 Issue

更多 DevTools Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。