How do I repair a Claude Desktop connector authorized to the wrong account?
A connector can exist and still point at an unintended Montage workspace because the consent browser was signed in differently than expected. Correct the account association before asking the assistant to inspect private research or retained audiences. Treat the first unexpected workspace as a stop condition. Reauthorization should correct the account association through supported connector controls, not explore private records or force account selection through invented parameters.
Help me repair a Claude Desktop connector authorized to the wrong account. Compare the actual signals_status workspace with the task’s expected destination. Accept recovery only after the real response identifies the intended workspace. No writes.Recognize the mismatch carefully
Compare the actual signals_status workspace with the task’s expected destination. Do not explore the unexpected workspace simply to determine whose data it contains; stop at the mismatch. The mismatch report needs only the fact that the returned workspace was unexpected; additional private-record exploration is not necessary.
Preserve the connector address
Review the remote HTTPS URL without changing it if it already targets Montage. A workspace mismatch is not evidence that the hosted transport endpoint should be replaced. Keep configuration identity and account identity in separate notes so a future operator does not confuse URL correctness with correct consent.
Use supported reauthorization controls
Return to the connector’s documented authentication flow and deliberately select the intended Montage identity. Do not transfer cookies or embed credentials into the connector description to force account selection. Review the account selection at the documented authorization step, not by pasting an email address into an invented tool argument.
Re-enable in a bounded conversation
Make the corrected connector available to the intended Claude conversation and ask only for status. Earlier conversation text referring to another workspace should not drive follow-up research automatically. A fresh bounded prompt reduces the chance that stale conversation context asks the newly authorized account to perform unintended research.
Confirm the corrected association
Accept recovery only after the real response identifies the intended workspace. If the client cannot reauthorize through supported controls, report the limitation without claiming that removing a local entry revokes every remote grant. Do not assume reauthorizing one connector disconnects every other client; this workflow validates the corrected association only where tested.
Keep the boundaries clear.
- Review the account selection at the documented authorization step, not by pasting an email address into an invented tool argument.
- Do not assume reauthorizing one connector disconnects every other client; this workflow validates the corrected association only where tested.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.