A connector or MCP server won't authorize

Connector states

• Pending — you started the connection but never finished authorizing. Tap the row → Authorize and complete it in the window that opens.
• Failed — the provider rejected the authorization. Disconnect, then connect again from scratch.
• Connected — working.

Common causes

• The popup was blocked or closed early. Authorization has to finish in the window that opens; closing it leaves the connector pending.
• Wrong account. If you’re signed into several Google or Slack accounts, the flow may have used the wrong one. Disconnect, sign into the right account, reconnect.
• Admin restrictions. Workspace and enterprise accounts (Google Workspace, Slack, ChatGPT enterprise) often require an admin to approve third-party apps first.
• Expired access. Providers expire tokens periodically; a connector that worked for months can simply need reconnecting.

Custom MCP servers

• Auth needed / Auth error — open the server and use Authorize / Re-authorize.
• Unavailable — the agent couldn’t reach the server. Check the URL, that the server is running, and any required headers. For STDIO servers, check the command and its environment variables.
• After changing a STDIO server, restart the agent (Actions → Restart agent) so the container picks it up.

See Connect apps and tools for the full setup, and Contact support if a provider keeps refusing — tell us which one.