claude.ai MCP connectors unavailable on some installations despite same account

Description

The claude.ai MCP integrations (Slack, Figma, Sentry) are available on one macOS installation but not on another, despite both using the same Claude Max account, same organization, and same Claude Code version (2.1.37).

Environment

• Claude Code version: 2.1.37 on both machines
• OS: macOS on both machines
• Login method: Claude Max Account (same email, same organization UUID)
• Install method: native on both

Observed behavior

Machine A (/mcp output):

• Shows claude.ai section with Slack (connected), Figma, Sentry
• cachedGrowthBookFeatures.tengu_claudeai_mcp_connectors: true

Machine B (/mcp output):

• No claude.ai section at all — only Built-in MCPs
• cachedGrowthBookFeatures.tengu_claudeai_mcp_connectors: false

Both machines share the same oauthAccount.organizationUuid and emailAddress.

Steps to reproduce

1. Log in to Claude Code with the same Claude Max account on two different macOS machines
2. Run /mcp on both
3. One shows claude.ai integrations, the other does not

Investigation

• Manually changing tengu_claudeai_mcp_connectors to true in ~/.claude.json works within a running session
• However, the flag is reset to false on every new session startup (server sync overwrites the cached value)
• Copying anonymousId from Machine A to Machine B did not change the server-side flag evaluation
• The plugin:slack:slack (SSE-based) plugin fails on both machines, so it is not a viable alternative

Expected behavior

The claude.ai MCP integrations should be consistently available across all installations logged in with the same account, or there should be a user-facing way to enable them.