[Feat] Support secure storage for secrets (API tokens) in MCP server configuration
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- Java
- Stars
- 128
- Forks
- 70
- Avg merge
- 5d 20h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/copilot-for-eclipse
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/copilot-for-eclipse#522 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
microsoft/copilot-for-eclipse#521 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 30/100
microsoft/copilot-for-eclipse#519 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
microsoft/copilot-for-eclipse#517 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/copilot-for-eclipse#512 ·
All issues in microsoft/copilot-for-eclipse
Similar issues
-
JPA security login throws when the stored password or roles string is nullPossibly taken @SebTardif claimed this today. Openarea/security env/windows
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
quarkusio/quarkus#58548 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
marchof/java-almanac#354 ·
-
bug posit-ai
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linkedin/shaky-android#103 ·