claude-code - 💡(How to fix) Fix [Bug] MCP Server Connection Status Not Reflecting After Chrome MCP Connection [1 comments, 2 participants]

[{"error":"Error: Claude Code web sessions require authentication with a Claude.ai account. API key authentication is not sufficient. Please run /login to authenticate, or check your authentication status with /status.\n at Ow (/$bunfs/root/src/entrypoints/cli.js:2647:1850)\n at async MX5 (/$bunfs/root/src/entrypoints/cli.js:3111:14629)\n at async iM7 (/$bunfs/root/src/entrypoints/cli.js:3111:15265)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T10:56:25.216Z"}]

TL;DR

Run the /login command to authenticate with a Claude.ai account, as API key authentication is not sufficient for Claude Code web sessions.

Guidance

• The error message indicates that authentication with a Claude.ai account is required, suggesting that the current authentication method (API key) is not enough.
• Check the authentication status using the /status command to verify the current authentication state.
• Run the /login command to authenticate with a Claude.ai account, which should resolve the "no MCP connected" issue.
• Ensure that the correct credentials are used during the login process to avoid further authentication errors.

Notes

The provided error message and environment information suggest that the issue is related to authentication, but the exact details of the MCP connection process are not specified.

Recommendation

Apply workaround: Run the /login command to authenticate with a Claude.ai account, as this is explicitly mentioned in the error message as the required step to resolve the authentication issue.