Skip to content
Enjoy complimentary data migration when switching from your existing bookkeeper or CPA to Institution.
AI connections and developer tools

Reconnect after MCP authentication is no longer valid

A confirmed invalid account session requires renewed sign-in and authorization.

Updated 2026-11-11

MCP returns an authentication challenge when the saved Institution session is confirmed no longer valid. The assistant may then ask you to reconnect or reauthorize Institution.

Use the assistant’s connection flow to sign in again and review the company and access. Complete authenticator verification when required. Do not paste a dashboard session token into the assistant to repair the connection manually.

A fresh sign-in at the permission portal can renew active connections while their OAuth credentials remain valid. The portal reports when existing connections have been renewed without changing their companies, permissions, or expiry choices.

Temporary outages, rate limits, and unclassified upstream errors are different from confirmed invalid authentication and can remain retryable. Read the actual error before revoking and recreating every connection. If the issue persists, provide support with the assistant name, company, operation, and safe error wording. Avoid sending access tokens, refresh tokens, or session cookies as diagnostic material.

Was this article helpful?

Tell us whether this answered the question you came with.

Related articles

Still stuck?

Tell us what you were trying to do and where it went wrong. If you are already a client, you can also open a support case from Help and support in your workspace.

We confirm who you are before we change anything on an account.