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

Offen
#518 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
15/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java
Bereich
security

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
Java
Sterne
128
Forks
70
Ø Merge
5 T. 20 Std.
Gemergte PRs (30 T.)
3

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/copilot-for-eclipse

Alle Issues in microsoft/copilot-for-eclipse

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.