Reconnect after MCP authorization expires
Reconnect customer Cloud MCP with the intended account and organization after an HTTP 401 response.
If your client reports HTTP 401 after authorization expires or is revoked, use its offered reconnection flow for Altifigence Cloud.
Reconnect to your account
Start reconnection in the MCP client and sign in through the authorization page it opens.
Check that the account and organization are the ones you intend to use. Review the requested read tools before approving consent.
Return to the client and refresh its tool list. Read your connected identity and accessible projects, then select a returned project and verify a small saved-file read.
Check access after reconnecting
If your organization has blocked MCP access, ask an organization administrator to review the block. After it is removed, reconnect and complete a new authorization.
Authorization and project access are checked against current permissions. If the next response is HTTP 403, check the organization's tool policy, your consent and your project access.
Keep authorization codes, tokens and cookies private. If you need help, share the client name and version, the time and the error message with sensitive information removed.