add option for a token autentication given by the user and ability to replace the port also update readme accordignly

[ValeroK]

Summary

This PR introduces several major improvements to the Browser MCP Chrome extension and related tooling:

1. Extension Options Page

• Added an options/settings page (options.html + options.ts) to the Chrome extension.
• Users can now set and persist the authentication token and port override directly from the extension UI.
• Settings are stored using chrome.storage.local and persist across browser restarts.

2. Capability Reporting

• The extension now reports its capabilities (name, version, supported features) to the server and clients.
• Capabilities include: token-auth, port-override, capabilities-report.

43 Documentation Updates

• Updated README.md with:
  • Instructions for using the new options page.
  • Example MCP client configuration (including port override).
  • Details on extension capabilities and how to use them.

---

How to Test

1. Build the extension and load it into Chrome.
2. Open the options page via chrome://extensions/ > Details > Options.
3. Set a token and (optionally) a port, save, and verify persistence.
4. Confirm the extension uses these settings for all WebSocket connections.
5. Use the MCP client with the updated configuration as shown in the README.

---

[ValeroK]

Please add the above as this will enable a more secure connection to the extension will also appreciate information how to build this on my own so i can better test the code

[valdezm]

This is great!

[valdezm]

@ValeroK Can you update your project to include the way to build your changes?

[ValeroK]

@ValeroK Can you update your project to include the way to build your changes?

Unfortunately don't have one. Waiting for the owner to merge this and build.

[valdezm]

@ValeroK So to be clear, you haven't tested this out yet? You haven't built your code to see if this new port and authentication scheme works correctly?

[valdezm]

I am going to use your code and the build we do have access to and re-compile it -- if so. I don't think the author wants to make changes to this project(and the extension). I have started piecing together patches on my own..

[ValeroK]

I am going to use your code and the build we do have access to and re-compile it -- if so. I don't think the author wants to make changes to this project(and the extension). I have started piecing together patches on my own..

As I don't have a was to build and test yea this code is curenetly in tested

[valdezm]

Yeah, not only untested, but never actually ran.. I find that impressive, that you developed code you haven't been able to execute. I am surprised and equally think -- that's cool.

[valdezm]

The code in this PR, regardless of it works or not -- is a good idea, I'd love to "coerce" it in to the built code..

[ValeroK]

The code in this PR, regardless of it works or not -- is a good idea, I'd love to "coerce" it in to the built code..

you are more then welcome to use it. the idea was to get the owner to incoporate this into his codebase but i agree currently it seems this will not be the case. would love to get a link to your repo to try and assist.

PS - Yea coding blindly is fun but not so much....