chore: modifies MCP server activation flow MCP-169 #1114
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Earlier we were starting the server only after a connection was connected for the first time and then additionally showing notification to disable the auto connect and auto start. With this change, we will start the server as soon as the extension activates and will show a notification to the user that auto-start of MongoDB MCP server has been enabled. If they wish to disable this behavior, the popup has buttons to do that. If they choose to disable then we will stop the server and set the auto-start to disable.
himanshusinghs
added
the
no-title-validation
kmruiz
approved these changes
Sep 3, 2025
nirinchev
approved these changes
Sep 4, 2025
himanshusinghs
deleted the
chore/MCP-169-modified-server-activation-flow
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Earlier we were starting the server only after a connection was connected for the first time and then additionally showing notification to disable the auto connect and auto start.
With this change, we will start the server as soon as the extension activates and will show a notification to the user that auto-start of MongoDB MCP server has been enabled. If they wish to disable this behavior, the popup has buttons to do that. If they choose to disable then we will stop the server and set the auto-start to
disabledotherwise we keep itenabled.I would recommend reviewing this with whitespace hidden.
A small screenshot of the popup:
Checklist
Motivation and Context
Open Questions
Dependents
Types of changes