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

Abierto
#518 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
security

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Java
Estrellas
128
Forks
70
Merge medio
5 d 20 h
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/copilot-for-eclipse

Todos los issues de microsoft/copilot-for-eclipse

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.