microsoft / microsoft/copilot-for-eclipse
[Feat] Add per-server enable/disable toggle to MCP preferences
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 126
- Forks
- 60
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe.
There is no way to temporarily disable a configured MCP server without destroying its configuration. A user needs to delete it from the MCP config JSON (losing the command, args, and environment settings)
Describe the solution you'd like
A per-server enable/disable toggle on the MCP preference page. When a server is disabled: its configuration is preserved and Copilot Language Server does not start or connect to it. Re-enabling it restores full functionality in a single action.
Describe alternatives you've considered
Unchecking all tools under the server: The server process still starts and connects every session. Re-enabling requires rechecking each tool individually and there is no memory of which tools were previously enabled.
Additional context
N/A
Contributor 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.
Research direction
Start at the MCP preference page and trace how per-server configuration is stored and how the Copilot Language Server starts or connects to configured servers. The change is done when each server can be disabled without losing its command, arguments, environment, or tool selections, and re-enabled in one action without starting while disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100