Implement auto-open feature for browser launch on server start

[kawakamidev]

Motivation and Context

This eliminates the manual step of copying URLs and opening browsers, making the development workflow more efficient.

How Has This Been Tested?

Tested on macOS environments with various browsers (Chrome, Firefox, Safari). Verified that the feature respects user configuration and can be disabled via configuration options.

Breaking Changes

No breaking changes. The feature is enabled by default but can be disabled through configuration.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the [MCP Documentation](https://modelcontextprotocol.io)
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

[cliffhall]

I tested locally on Mac and it works ok, but a few things:

• There are conflicts to be resolved as the branch is behind.
• Yours launches with http://localhost rather than http://127.0.0.1 which we're using instead, to comply with OAuth requirements.
• Along with new config items comes a form field requirement in the sidebar. We need an affordance to turn this feature off.

[kawakamidev]

@cliffhall I've commited

[cliffhall]

This is a double negative that made me have to think about its validity for a second. Could it instead be "Enable Browser Auto-open" and default to true?

[kawakamidev]

@cliffhall Review please

[cliffhall]

Hey @moekiorg. Looks good, operates perfectly. Need to do npm run prettier-fix though.

[cliffhall]

@cliffhall Review please

@kawakamidev It works fine for opening, but the UI configuration field doesn't change the behavior. If I set it to false then close the inspector, when I run the inspector again, it just auto launches.

[cliffhall]

@kawakamidev It works fine for opening, but the UI configuration field doesn't change the behavior. If I set it to false then close the inspector, when I run the inspector again, it just auto launches.

The problem here is that for this to work, the setting can't just be stored in the browser's local storage, it also has to write back to a locally stored configuration that will be consulted before the app launches next time. That's tough, since we don't currently have such a file and plumbing backwards from the client to write it would be a pain.

Perhaps we should trim this back to the place you originally had it. Just the auto-open, no UI affordance.