github / github/copilot-cli

[Feature Request] Send copilot-cli specific metadata when invoking MCP servers

未關閉
#432 5 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
area:mcp
主要語言
Shell
星號
11.2k
分支
1.9k
平均合併
14 小時 16 分鐘
30 天內合併 PR
6

描述

### Describe the feature or problem you'd like to solve

Send copilot-cli specific metadata when invoking MCP servers

### Proposed solution

Right now, the `copilot` CLI doesn’t include any identifier when it connects to MCP servers.

Here's a sample MCP request from the `copilot` CLI
```json
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"_meta": {
"progressToken": 2
},
"name": "cool_tool_name",
"arguments": {
"foo": "bar"
}
}
}
```

Environment:
```console
> copilot --version
0.0.353
Commit: f8fd3e3
```

Meanwhile, VS Code kind of labels itself.
```json
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"_meta": {
"progressToken": "f78b107c-d8f7-415e-9acb-9a924295e3c7",
"vscode.conversationId": "4bbaa913-a8a3-4807-8b22-39b38a640d52",
"vscode.requestId": "4578b866-66a0-41fe-a345-baec275a82b2"
},
"name": "cool_tool_name",
"arguments": {
"foo": "bar"
}
}
}
```

### Example prompts or workflows

_No response_

### Additional context

_No response_

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。