Don't always autoconnect/auth

[grrowl]

Any use of useMcp connects to the server and then triggers auth flow if required. This means we can't have it existing across our whole app.

Currently we work around this by specifying url: '' which errors, but fails connecting until we decide.

It would be great if we could start the app normally without auto-connect, and call connect() at our discretion which then would do auth etc.

[geelen]

I've actually built this already, it's just on a branch tied up with other stuff so it should land soon.

The way I designed it was it'll always automatically attempt to connect, but if it gets an auth error it'll just wait until you manually trigger it to continue. But I could see the need to not even attempt straight away, but offer a connect and a clearAuthentication function...

[grrowl]

Happy with either — connecting but not popping auth as a result of mount would be fine for my use case. Would be ideal for it to be reflected in status with authUrl filled in in all cases it would be necessary.

[geelen]

Merged #18 into my working branch, should have that merged & released v soon.

[geelen]

Released in v0.0.17. New flag is preventAutoAuth

[MTG2000]

Hey @geelen

I noticed that even with this option set to true, the popup still appears on first mount.

You can actually test this on the chat example: https://chat.use-mcp.dev/ by adding any MCP server that requires auth & closing the popup then reloading the page. (& ensuring your browser isn't blocking it)
You will notice that it appears right away on every reload even though the preventAutoAuth is set to true in the code:

use-mcp/examples/chat-ui/src/components/McpServerModal.tsx

Line 22 in 5b54994

preventAutoAuth: true, // Prevent automatic popups on page load

Is this expected or is it a bug?