# Claude connectors not working? Fixes for Drive, GitHub, Gmail > Fixes for Claude connector errors in Google Drive, Gmail, GitHub, Notion and custom MCP servers, from dynamic client registration to Claude Desktop. Updated 2026-11-15 · https://upsy.ai/guides/claude/connectors-not-working ## Short answer Most broken Claude connectors come down to one of four things: a sign-in that didn't finish, a connector that's off in this chat, an admin who hasn't allowed it, or a problem on Claude's or the app's side. Check [status.claude.com](https://status.claude.com) first. Then click **Disconnect** and **Connect** again under **Customize › Connectors**, and check the connector is on under **+ › Connectors** in the chat. On Team and Enterprise, an Owner adds a connector before you can connect it. ## First: is it Claude's side? Claude's status page lists connector outages. Recent ones: all connectors on [October 22, 2026](https://status.claude.com/incidents/wj6r4t6mxq1r), Google Calendar on [October 26 to 28](https://status.claude.com/incidents/phg1y2yh07n2), Gmail on [October 27](https://status.claude.com/incidents/9ftx658xtd5z), Microsoft 365 on [November 12 and 13](https://status.claude.com/incidents/sqn3fg1l96dl) (an incident at Microsoft), and adding new connectors on [November 13](https://status.claude.com/incidents/34wq7gxnxvvm). If your error lines up with one, wait for the fix. | Error or symptom | Where | Fix | |---|---|---| | "Couldn't reach the MCP server" | Custom connector | A public HTTPS address on port 443 | | "Couldn't register with … sign-in service" | Custom connector | Add it again with your own OAuth client ID | | Connected, but no tools in the chat | Chat, Cowork | Switch it off and on under **+ › Connectors** | | "Access blocked: … admin needs to review Claude" | Google Workspace | A Workspace admin trusts Claude | | Shared drive files come back empty | Google Drive | Open bug; copy the files to My Drive | | "Claude cannot access that resource" | GitHub | Give the Claude GitHub App that repo | | "Invalid MCP state. Please enable browser cookies and try again." | Notion | Allow Notion's cookies and reconnect | | "A personal account can't sign in through 'Work or school account'" | Microsoft 365 | Choose **Personal account**, on the web | ## Custom connectors (remote MCP servers) The [custom connector guide](/guides/claude/custom-connector) covers "Authorization with the MCP server failed", "Unexpected error while invoking tool" and a missing **Add custom connector** button. ### "Couldn't reach the MCP server" Claude connects from Anthropic's cloud, not your computer. The address must use HTTPS on port 443 and resolve to a public IPv4 address, and no firewall may block Anthropic ([help article](https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp), [Anthropic's troubleshooting](https://claude.com/docs/connectors/building/troubleshooting)). The same message shows when Claude can't find how the server signs in. So a server can work in Claude Code, which connects from your machine, and still fail on claude.ai. ### Dynamic client registration not supported To sign you in, Claude needs a client ID from the server's sign-in service. The add dialog's **OAuth client** setting has three ways to get one ([Anthropic](https://claude.com/docs/connectors/custom/add-unlisted)): **Use Claude's published identity** (a Client ID Metadata Document that Anthropic hosts, recommended), **Register automatically** (dynamic client registration, or DCR), or **Use your own OAuth client**. When a server supports neither of the first two, Claude says it "couldn't register with" its sign-in service and suggests adding an OAuth Client ID ([example](https://github.com/anthropics/claude-ai-mcp/issues/848)). If the service lets you create an OAuth client, create one with `https://claude.ai/api/mcp/auth_callback` as the redirect URL. Then remove the connector and add it again with **Use your own OAuth client**, since sign-in settings can't be edited. Some servers that do support registration have shown this message too since July 2026 ([issue](https://github.com/anthropics/claude-ai-mcp/issues/699)); report those. - **Claude Code** says "Incompatible auth server: does not support dynamic client registration". Add the server with `--client-id`, `--client-secret` and `--callback-port`, register `http://localhost:PORT/callback` at the service, then run `/mcp` ([Claude Code docs](https://code.claude.com/docs/en/mcp)). - **OpenAI Codex** says "Registration failed: Dynamic registration failed: Registration failed: Dynamic client registration not supported" on `codex mcp login`, for example with Slack's server ([issue](https://github.com/openai/codex/issues/13200)). See [Slack in Codex](/guides/codex/slack). The MCP spec made DCR optional, and its July 2026 version marks it deprecated in favor of Client ID Metadata Documents ([spec](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization)). [GitHub's](https://github.com/github/github-mcp-server/blob/main/docs/host-integration.md) and [Slack's](https://docs.slack.dev/ai/slack-mcp-server/) MCP servers don't support it. ### "Connector couldn't be added" On November 13, 2026, many people got this, often after "Couldn't determine how this server signs in", when adding any custom connector ([issue](https://github.com/anthropics/claude-ai-mcp/issues/1275)). It was that day's outage and cleared within hours. ### Connected, but Claude has no tools Check the connector is on for this chat, and name it in your prompt. A November 2026 report found new chats sometimes saw a connected custom connector with no tools, and switching it off and on in that chat fixed it ([issue](https://github.com/anthropics/claude-ai-mcp/issues/1264)). ## Google Drive, Gmail and Calendar ### "Access blocked: your institution's admin needs to review Claude for Google Drive" A Google Workspace admin sets Claude to **Trusted** under **Security › Access and data control › API controls › Manage third-party app access** in the Admin console, then waits about 15 minutes ([Anthropic](https://support.claude.com/en/articles/10166901-use-google-workspace-connectors)). Full steps are in the [Google Drive guide](/guides/claude/google-drive). For "You may need to reconnect", disconnect and connect again, and if it returns, remove Claude at [myaccount.google.com/connections](https://myaccount.google.com/connections) first. ### Shared drive files come back empty Since April 2026, users report that search and folder lists return nothing in Shared Drives while My Drive works ([issue](https://github.com/anthropics/claude-code/issues/53442), still open). One user's fix was a Workspace admin approving Claude for Google Drive for the organization; others found none. The usual workaround is copying files into My Drive. ### Gmail: "This app is blocked" In April and May 2026, Google showed this, with no way past it, when users reconnected Gmail in Cowork ([issue](https://github.com/anthropics/claude-code/issues/52177)). Revoking Claude's access didn't help, and the report closed without a fix. "Couldn't reach Gmail" on November 13 was the outage and [cleared that afternoon](https://github.com/anthropics/claude-ai-mcp/issues/1268). ## GitHub ### "Add from GitHub" is missing, or "Claude cannot access that resource" Connect **GitHub Integration** under **Customize › Connectors** first. On Team and Enterprise, it's listed only once GitHub is turned on for the organization. "Claude cannot access that resource" means the repo is private and the Claude GitHub App can't reach it: follow the link in the message to grant or request access ([Anthropic](https://claude.com/docs/connectors/github)). Missing organization repos are covered in the [GitHub guide](/guides/claude/github). ### Adding GitHub's MCP server fails GitHub's server doesn't support DCR, and GitHub's own guide says Claude's custom connectors aren't supported ([GitHub](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-claude.md)). In July 2026, a Claude Desktop user got a "couldn't register" error on every try ([issue](https://github.com/anthropics/claude-code/issues/74330)). Use the built-in integration, Claude Code with a token, or Upsy. ### In Cowork, GitHub says Connected but has no tools Reported since May 2026 on Windows and macOS, while other connectors work ([issue](https://github.com/anthropics/claude-code/issues/61682)). It's still open, and reconnecting doesn't help. Reporters say GitHub works in Claude Code. ## Notion ### "Invalid MCP state. Please enable browser cookies and try again." The page comes from Notion's own server, mcp.notion.com. Cursor's staff advised allowing cookies for notion.com and notion.so, trying another browser, and contacting Notion support if it fails everywhere ([forum, August 2026](https://forum.cursor.com/t/notion-mcp-cannot-authenticate/167714)). In April 2026, claude.ai users got it on every reconnect until it was marked fixed in May ([issue](https://github.com/anthropics/claude-ai-mcp/issues/182)). ### Claude shows "Disabled by admin" On Notion Enterprise, owners can allow only approved clients under **Settings › Notion MCP › Manage workspace clients** ([Notion's help](https://www.notion.com/help/notion-mcp)). Ask one to approve Claude. See the [Notion guide](/guides/claude/notion). ## Slack and Microsoft 365 ### Slack shows "Request to install" Claude's Slack connector needs Anthropic's Claude app installed in Slack first. Where apps need approval, Slack shows **Request to install** until an admin approves it ([Anthropic](https://claude.com/docs/connectors/slack)). See the [Slack guide](/guides/claude/slack). ### "A personal account can't sign in through 'Work or school account'" As of November 2026, Claude's Microsoft 365 connector takes personal Outlook.com, Hotmail, Live and MSN accounts on Free, Pro, Max and Ultra, for Outlook and OneDrive. Each sign-in option accepts only its own kind of account, so pick the one that matches. Connect a personal account on claude.ai in a browser; Team and Enterprise don't offer it. On a work account, a feature Anthropic adds later can fail with a permission error until an Entra admin approves it, and reconnecting doesn't help ([Anthropic](https://claude.com/docs/connectors/microsoft/365)). ## Claude Desktop, mobile and Team plans ### Claude Desktop: a local MCP server doesn't show up Servers in `claude_desktop_config.json` run on your computer. Check the JSON is valid and paths are absolute, then fully quit and reopen Claude Desktop. Logs are in `~/Library/Logs/Claude` on macOS and `%APPDATA%\Claude\logs` on Windows: `mcp.log` for connection failures, `mcp-server-NAME.log` for each server ([MCP docs](https://modelcontextprotocol.io/docs/develop/connect-local-servers)). A server with an `https://` address goes in as a custom connector instead. ### Mobile, Cowork, Team and Enterprise - **Mobile:** add connectors on the web or desktop, since installing them in the app is still in beta. They appear in the iOS and Android apps the next time you log in ([help article](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities)). - **Cowork:** merged with chat on September 16, 2026, with connectors carried over ([release notes](https://support.claude.com/en/articles/12138966-release-notes)). The fixes above apply. - **Request instead of Connect:** an Owner hasn't added the connector. On Team, **Request** notifies the Owners ([Anthropic](https://claude.com/docs/connectors/directory)). Once it's added, click **Connect** yourself. - **"This corporate identity belongs to an Enterprise that manages access through their own Claude account":** the service's email domain belongs to a company on Claude Enterprise. Connect from that organization's Claude account, or ask its admin ([help article](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities)). ## When Upsy is a way around Upsy helps where the problem is a connector's limits or sign-in: more than one account, read-only or per-action access, and servers Claude can't register with. You connect each app once in Upsy and add Upsy to Claude as one custom connector, `https://upsy.ai/connect`, with no client ID to enter. - **GitHub:** Upsy signs in to GitHub's MCP server with its own GitHub OAuth App, so the registration error doesn't come up. - **Google:** up to five accounts per app, each at No access, Read-only, Full access or Pick actions. - **Personal Outlook on Team and Enterprise:** Upsy's Outlook connector is waiting on Microsoft's approval, so for now Claude uses outlook.com in Upsy's cloud browser. It doesn't fix an admin block. While Google reviews Upsy's own app, Gmail, Calendar and Drive sign in through Composio, and a Workspace admin's block applies there too. A Notion sign-in error can hit Upsy too, since it uses Notion's own server. And custom connectors run on the same infrastructure as directory ones ([Anthropic](https://claude.com/docs/connectors/directory)), so an outage on Claude's side affects Upsy as well. ## Before you contact support When a connection fails, copy the reference that starts with `ofid_` from the error or the page address, and report it soon, since it expires. Server owners report at [anthropics/claude-ai-mcp](https://github.com/anthropics/claude-ai-mcp/issues) with the server URL and their logs. A failed tool call has no reference: give the tool's name, the time in UTC and the connector's URL ([Anthropic](https://claude.com/docs/connectors/building/troubleshooting)). Never include passwords, tokens or client secrets. ## FAQ ### Why are my Claude connectors not working? Usually an unfinished sign-in, a connector that's off in this chat, an admin who hasn't allowed it, or an outage. Check status.claude.com, then disconnect and connect again. ### Why is the Claude Google Drive connector not working? Disconnect and connect again. "Access blocked" needs a Workspace admin. Files in Shared Drives can come back empty because of an open bug. ### Why is the Claude GitHub connector not working? Private repos need the Claude GitHub App to have access. In Cowork, an open bug leaves GitHub connected with no tools. GitHub's own MCP server can't be added, because Claude can't register with it. ### Why is the Claude Gmail connector not working? Check the status page, then disconnect and reconnect. It holds one Google account and can't read what's inside attachments, by design. See [multiple Gmail accounts](/guides/claude/multiple-gmail-accounts). ### Why is the Claude Notion connector not working? On "Invalid MCP state", allow cookies for notion.com and notion.so and reconnect. On Notion Enterprise, an owner may need to approve Claude. ### What does "dynamic client registration not supported" mean? The server won't let apps register themselves. Add the connector again with your own OAuth client ID, or use `--client-id` in Claude Code. ### Why is my MCP server not working in Claude Desktop? For a local server, use absolute paths, fully restart Claude Desktop, and read `mcp.log`. A remote server goes in as a custom connector instead. --- Upsy connects personal AI assistants (Muse, Grok, ChatGPT, Claude, Cursor, Claude Code, Codex, Devin) to your Gmail, Google Calendar, Google Drive, Slack, Notion and other apps through one MCP server, with a shared memory, files and a cloud browser signed in to your sites. You choose what each assistant may do in each app, see everything it did, and turn it off in one click. Upsy is free. To add Upsy to an assistant, add a remote MCP server (Streamable HTTP) named Upsy at https://upsy.ai/connect. It signs in with OAuth; there is no API key.