Claude Connectors Not Connecting: Fix Setup and Access

When a Claude connector is not connecting, not showing, or keeps dropping, the cause is almost always in one of three areas: the account or plan does not include connectors, the organization settings have disabled or not yet enabled the connector, or the authentication with the external service has failed or expired. Working through these checks in order gets you to the fix faster than trying things at random.

While you work through the checks below, keep a note of what you have tried and what each step showed. If you need to hand the problem to a teammate or IT admin, a clear account of what was checked saves everyone time. fenbs keeps that troubleshooting record alongside the project the connector was meant to serve.

First: confirm connectors are available on your plan

Claude connectors are available on Team and Enterprise plans. If you are on a free or Pro plan, the connectors section may not appear in your settings. Open claude.ai, go to Settings, and check which plan is active. If connectors are not listed in the settings menu, your plan likely does not include them.

For an overview of what Claude connectors are and which plans support them, see Claude connectors explained before continuing with the troubleshooting steps here.

Check your organization settings

On Team and Enterprise accounts, connectors are controlled at two levels: the organization and the individual user. An organization admin can enable or disable specific connectors, and their settings take effect for all members. If a connector is not showing for you but your plan includes it, the organization admin may not have enabled it yet.

Check with your admin whether the connector you need is turned on in the organization console. Ask them to verify that your user account is included in any access group that controls connector availability. In Enterprise accounts, access groups can restrict which connectors individual users see.

Re-authenticate the connector

If a connector shows in the settings but fails to connect, the most common cause is expired or revoked authentication. Connectors use OAuth to connect to external services, and that token can expire, be revoked when a password changes, or be invalidated when account permissions change.

To re-authenticate, go to the connector settings in Claude, disconnect the existing connection, and reconnect it. You will be taken through the sign-in flow for the external service again. Use the account that has access to the content you want Claude to search.

• Make sure you are signing in with the account that owns or has access to the content, not a personal account that lacks access to a shared drive.
• Check that the account used to authenticate has not had its permissions changed since the connector was first set up.
• If you use SSO, confirm that the SSO session is active before reconnecting.

When the connector keeps disconnecting

A connector that reconnects and then drops again usually has an underlying session or permission issue on the external service's side. Common causes include a short-lived access token from the external service, an account password change that invalidates existing tokens, or a policy on the external service that limits third-party app connections.

Check the external service's settings for any third-party app access controls. Google Workspace and Microsoft 365 admins can restrict which apps may request OAuth access, and a recently changed policy may be revoking the token silently. For Microsoft 365 connections, check the tenant-level app consent settings.

When the connector is not showing at all

If you expect a connector to appear in the settings but it is not listed, there are a few things to check beyond the plan and organization settings. Some connectors have geographic availability limits, and some are in limited release to specific accounts. Check Anthropic's support pages for the connector you need to see if it is in a limited rollout.

Also try a hard refresh of the page or signing out and back in. Browser caching can sometimes show a stale version of the settings page that does not include a recently added connector. If the problem persists across browsers and devices, contact Anthropic support with your account details.

Keep troubleshooting progress and context safe

When a connector problem blocks a project, the troubleshooting itself becomes part of the project's context. What was tried, what each check showed, who was contacted, and which steps are still open are all useful for whoever picks up the work next, whether that is you tomorrow or a teammate.

fenbs keeps that troubleshooting record alongside your project. Add a task for the connector issue, note what each check showed, and record any decision about a workaround or alternative. The next session starts with that context instead of starting over.

How to do this with fenbs

1. Create a free account and add a project for the work the connector was meant to support.
2. Add a task for the connector issue. Use the task notes to record each check: plan status, organization settings, authentication attempt, and the result of each.
3. If you find a workaround, record the decision in Decisions and rules so future sessions know the approved approach.
4. Connect Claude or another supported assistant via Integrations once the connector is working. The assistant reads the project context, including any decisions made during the troubleshooting, before starting work.

For comparison, the ChatGPT connectors not working guide covers the same kind of checks for ChatGPT connectors. Many of the authentication patterns are similar.

If the problem is specific to Claude Code not working or Claude.md not working, those are separate issues with different causes.