[Feat] Support secure storage for secrets (API tokens) in MCP server configuration

オープン
#518 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
15/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
java
領域
security

調査の方向性

The payload names no files, so start by locating where the MCP server configuration is read and saved in the plugin. The issue asks for two things: MCP configs that reference secrets instead of holding them, and storage through Eclipse Secure Storage, modelled on VS Code's inputs mechanism. Work out the design before coding. Done means a token can be referenced rather than typed in plain text. This is design work, so discuss the approach with maintainers first.

索引モデルが issue の本文から書いたものです。

説明

enhancement

Is your feature request related to a problem? Please describe.
I'm frustrated that MCP server credentials, such as API tokens for Jira, have to be entered directly into the MCP configuration in Copilot for Eclipse. There is currently no other way to provide them: the configuration doesn't support referencing environment variables, and MCP servers don't pick up OS environment variables either. The token must be saved in plain text in the configuration.

As a result, these tokens are:

  • readable by any process or user with access to the Eclipse configuration files
  • at risk of being exposed through backups, synced settings, screenshots, or screen sharing

As MCP servers become more common, users are handing more and more tokens to AI agents, so this is a growing security concern. In corporate environments, storing credentials in plain-text files may also violate security policies, which can prevent teams from using MCP servers in Eclipse at all.

Describe the solution you'd like
Allow MCP configurations to reference secrets instead of containing them, and store the actual values in a secure way. One approach could be to save it using Eclipse's built-in Secure Storage.

The integration into the MCP mechanism could be similar to VS Code's inputs mechanism (from the local harness).

Describe alternatives you've considered
Not even the Copilot harness in VS Code supports the "inputs" mechanism yet (as opposed to the local harness). To at least reach parity with the Copilot harness in VS Code, support for environment variables could be added.

Additional context
None so far

主要言語
Java
スター
128
フォーク
70
平均マージ
5日 20時間
マージ済み PR(30日)
3

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoft/copilot-for-eclipse のほかの issue

microsoft/copilot-for-eclipse の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。