Skip to main content
Most connector problems fall into a small number of patterns — expired tokens, revoked permissions, or browser state that needs a reset. Work through the section that matches your symptom and you’ll be back up in a few minutes. For general questions about Bridge, see the FAQ.

​
Connector won’t connect or OAuth fails

If clicking Connect opens an authorization window that errors out, closes immediately, or loops back without completing:
1

Allow pop-ups for the Bridge domain

The OAuth flow opens in a pop-up window. If your browser is blocking pop-ups, you’ll see the authorization window never appear or close instantly. Allow pop-ups for bridge-mcp-967806289134.us-central1.run.app and try again.
2

Clear your browser cache

Stale cookies or cached auth state can interrupt the OAuth flow. Clear your browser cache, reload the Connectors page, and try connecting again.
3

Disconnect and reconnect

If the connector is partially connected, disconnect it first:
  1. Go to the Connectors page.
  2. Find the connector and click Disconnect.
  3. Click Connect again and complete the full authorization flow.

​
Connector shows as connected but commands fail

If Bridge reports a connector as connected but your commands return errors or no results:
OAuth tokens issued by third-party tools have expiration dates. When a token expires, Bridge can no longer act on your behalf even though the connector still appears connected.Fix: Go to the Connectors page, disconnect the affected connector, and reconnect it to issue a fresh token.
If your role changed in the connected tool — for example, someone removed your admin access in ClickUp or Google Workspace — Bridge may no longer be able to complete certain actions.Fix: Check your permissions in the connected tool’s settings and restore the access level that was active when you authorized Bridge.
For connectors that use API keys rather than OAuth (such as Shopify), the key may have been rotated or deleted in your tool’s dashboard.Fix: Log in to your tool’s admin panel, generate a new API key, and re-enter it in Bridge from the Connectors page.

​
”You’ve reached your connector limit” error

The Free plan supports a maximum of 3 connected tools. If you try to connect a fourth connector, Bridge blocks the request.
Upgrade to the Individual, Team, or Agency plan for unlimited connectors. Go to your Profile → Manage Subscription to upgrade.
If you need to stay on the Free plan, disconnect a connector you’re not using before adding a new one.

​
Commands seem to fail silently

If you send a command and nothing happens, or the response is vague with no clear outcome:
1

Check the progress panel

The Command Center shows a step-by-step progress panel while Bridge executes your command. If a step failed, the panel will show where it stopped. Look for a red indicator or an error message in the panel.
2

Try a simpler command

Run a basic read-only command against the same connector — for example, “list my ClickUp tasks” or “show my Gmail inbox.” If that works, the connector is healthy and the issue may be with the specific action you were trying.
3

Reconnect the connector

If even a simple command fails, disconnect and reconnect the affected connector to rule out a token issue.

​
File upload not working

Bridge accepts files up to 10 MB. Files larger than that won’t upload. If your file is too large, try compressing it or splitting it before uploading.
Bridge supports: PDF, DOCX, XLSX, CSV, JSON, TXT, MD, PNG, JPGIf your file is a different type, convert it to one of the supported formats before uploading.
Drag the file directly onto the chat input area at the bottom of the Command Center — not the page itself. If drag-and-drop isn’t working, try clicking the file upload icon in the input bar to browse for the file instead.

​
Can’t log in or stuck in a redirect loop

If Bridge keeps redirecting you to the login page even after signing in, the stored session token may be corrupted.
1

Open browser DevTools

Press F12 (or Cmd+Option+I on Mac) to open DevTools, then click the Application tab.
2

Clear your stored session token

In the left sidebar, expand Local Storage and select the Bridge domain. Find the bridge_token key, right-click it, and choose Delete.
3

Reload and sign in

Close DevTools, reload the page, and sign in again at the login page. Bridge will issue a fresh token and redirect you to the Command Center.
If you need to clear the token regularly, check that your system clock is set to the correct time — an incorrect clock can cause sessions to expire immediately after signing in.

​
MCP connection issues (Claude or Gemini)

If Bridge isn’t responding when accessed through an MCP client like Claude Desktop or Claude.ai:
Make sure you’re using the correct endpoint — a single incorrect character will cause the connection to fail.
Check the URL in your AI client’s MCP server settings and correct it if needed.
Visit the health endpoint in your browser to verify Bridge is reachable and your session is active:
If you’re not logged in, go to the login page first, then retry from your MCP client.
Some MCP clients cache the server connection and don’t automatically pick up a refreshed token. If your session expired and you signed in again, remove the Bridge MCP server from your AI client’s settings and add it again with the same URL.