The MCP permission portal currently provides email and password sign-in rather than a Google sign-in button. An account used only through Google may therefore need an Institution password before it can connect there.
Manage or recover the password through the Institution dashboard’s account-access flow using the same account email. Then return to the MCP sign-in page and use that email and password.
Do not create a second Institution account merely to obtain a password field. A different account may not have access to the company or records you want the assistant to use.
If authenticator verification is enabled, complete it when the portal asks. Setting or changing a password does not remove the second factor. If the portal still rejects sign-in, check the account email and use support for the specific access issue. Never paste a Google session token, authenticator setup key, or password into the assistant’s chat as a substitute for the portal’s secure sign-in.
Was this article helpful?
Tell us whether this answered the question you came with.