[BUG] Clerk connector activated without user action or Clerk account
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Summary:
The Clerk connector appeared as connected in Claude Desktop without me connecting it. I do not have a Clerk account and did not authorize this connection.
Steps to reproduce:
Not reproducible on demand — the connector appeared connected at some point during normal use of Claude Desktop.
Expected behavior:
Connectors should only become active when explicitly authorized by the user.
Actual behavior:
The Clerk connector appeared in the active tools list mid-session without any user action. I was not prompted to authorize it, and I have no Clerk account to authorize against.
Environment:
OS: Windows 11 Pro (10.0.26200)
Claude Desktop Version 1.1.8359 (64248d)
Additional context:
No other users have access to this machine
The mcpServers section of claude_desktop_config.json is empty — no custom MCP servers configured
The connector was discovered when it appeared in the available tools list during an active session
Disconnected manually upon discovery
What Should Happen?
Connectors should only become active when explicitly authorized by the user. A connector with no associated account should never appear as connected.
Error Messages/Logs
Steps to Reproduce
Unable to reproduce on demand. The connector appeared as connected during a normal Claude Desktop session without any user action. No installation steps were taken and no Clerk account exists to authorize against.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
1.1.8359 (64248d)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
Using the desktop version of Claude, not a terminal.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗