Fix Claude Tool / Connector Showing "Unavailable"

Q: How do I tell if it's an Anthropic outage or just my account?

Check `status.anthropic.com` first — if there's an open incident naming the tool (Anthropic logs per-connector incidents like the Google Drive one), it's their side and you wait. If the status page is green but a coworker on the same workspace *can* use the tool, the problem is local to your account or client.

Q: Why can my coworker use web search but I can't?

Web search has two gates: the admin must enable it under `Admin settings > Capabilities`, and you must turn it on per chat via the slider icon in the composer. If the admin gate is open, click the slider and toggle "Web search" on — it's off by default in new chats.

A Claude tool greys out or shows "unavailable in your workspace." Triage status, plan, and admin policy in the right order to get it back fast.

Published: May 17, 2026 Updated: Jun 15, 2026 Author: AI Productivity Guide Team 🌐 查看中文版本

Yesterday you used Web Search, a Connector, or some other tool in Claude. Today it’s greyed out, won’t click, or shows “unavailable in your workspace.” You didn’t change a thing.

Fastest fix: “Worked yesterday, broken today” is almost never a Claude-wide outage (that would make headlines). Your workspace state changed. Triage in this exact order — doing it backwards wastes hours:

Status page (status.anthropic.com) — is there an open incident for this tool?
Your plan (Settings → in the model/capability list) — does your current tier still include it?
Workspace admin policy (Team/Enterprise → Organization settings > Connectors / > Capabilities) — did an Owner disable it?
Your app version + cache — is the desktop app or browser showing a stale tool list?

The single most common cause on Team and Enterprise plans is #3: an Owner or Primary Owner toggled the tool off org-wide. The single most common cause on personal Free/Pro/Max plans is a stale desktop app or browser cache (#4).

Which bucket are you in?

Run this 30-second test before anything else.

Symptom you see	Most likely cause	Jump to
Nobody in your workspace can use it	Admin disabled it org-wide	Step 3
Only you can’t use it; coworkers can	Stale app/cache, or your per-chat tool setting	Step 4
Tool card shows “Request access” / “Beta”	Limited preview, not in your cohort	Step 5
Error says “not available in your region”	Region / data-residency lock	Region restriction
`status.anthropic.com` shows an incident	Anthropic-side outage	Step 1
Plan recently downgraded / trial ended	Tier no longer covers the tool	Step 2

Common causes

Ordered by hit rate, highest first.

1. Workspace admin disabled the tool

On Team and Enterprise plans, an Owner or Primary Owner can disable connectors and individual tool calls for the whole organization. As of June 2026 the controls live in two places:

Connectors (Google Workspace, custom MCP, Desktop extensions): Organization settings > Connectors. Owners can disable a connector entirely, or disable specific tool calls a connector exposes.
Web search and other capabilities: Admin settings > Capabilities (also labeled Organization settings > Capabilities). Web search must be enabled here before any member can switch it on in a chat.

Common reasons an admin flips these off: a compliance/data-egress audit, or monthly cost control.

How to spot it: ask another member of the same workspace whether tool X works for them. If nobody can use it, it’s almost certainly admin-disabled.

2. Your plan no longer covers the tool

Connectors are available on Free (limited to one custom connector), Pro, and Max. Some enterprise-grade connectors, Enterprise Search, and admin-controlled capabilities require Team or Enterprise. A downgrade (Team → Pro) or the end of a trial silently drops the higher-tier tools.

How to spot it: open Settings and confirm your current plan name, then compare against Anthropic pricing for which tier includes the tool.

3. Anthropic-side maintenance or incident

Specific tools — especially newer connectors — get temporarily taken down for fixes. A real example: Anthropic’s status history has logged a “Degraded Google Drive Connector Experience” incident scoped to one connector, not the whole product.

How to spot it: status.anthropic.com shows an open or recently-resolved incident naming the tool (the page tracks six components).

4. Region restriction / data residency

Claude.ai and the API are available in 150+ countries, but export-control rules and workspace region locks block some tools in certain places. A VPN that lands you in an unsupported region can trigger it. Anthropic also restricts China-controlled organizations.

How to spot it: the error reads “access to Anthropic models is not available in your region,” or switching off a VPN / changing network restores access. Check the official supported countries list.

5. Beta / preview feature not enabled for you

Some tools are closed beta or invite-only. You see others using it but your workspace isn’t in the cohort. Mobile connector installation (iOS/Android), for instance, has shipped as beta.

How to spot it: the tool card has a “Request access” button, or Anthropic’s docs/blog flag it as a limited preview.

6. Stale desktop app or browser cache

The backend enabled the tool, but your client still shows the old list. This is more common than it sounds: a known Claude Desktop build (the v1.8555.x line, mid-2026) shipped with the Customize > Connectors panel rendering but completely un-clickable, and some Anthropic-curated plugins vanishing from the UI even though they were still enabled server-side.

How to spot it: a hard refresh (web) or a full app restart/update (desktop) brings the tool back, or it appears in a different browser.

Shortest path to fix

Step 1: Check the status page first

Visit https://status.anthropic.com
  -> any ongoing incident naming this tool?
  -> check the past 24h history for a recent one

If there’s an open incident, wait for the fix and click Subscribe to updates so you’re notified. Don’t burn time chasing a config problem that isn’t yours.

Step 2: Self-check your plan

Claude Settings -> your plan name
  -> compare against https://www.anthropic.com/pricing
  -> confirm your current tier still includes the tool

If your trial ended or a seat was downgraded, that’s your answer. Test the tool on a trial of the higher tier before committing to an upgrade.

Step 3: Ask your admin about org policy

If you’re on a Team or Enterprise workspace and nobody can use the tool, email the Owner. Give them the exact path so they can check in seconds:

Subject: Tool "X" greyed out in our Claude workspace

Hi [admin],

Tool "X" stopped working today for our team in Claude.
status.anthropic.com shows no incident, and my plan covers X.

Could you check whether it was disabled recently?
  - Connectors: Organization settings > Connectors
  - Web search / capabilities: Admin settings > Capabilities

If it was deliberate, can we discuss re-enabling? We use X for:
[brief description of the workflow]

Step 4: Reset your app version, cache, and per-chat tool access

If coworkers can use the tool but you can’t, the problem is on your client. Work top to bottom:

Web:    hard refresh  -> Cmd+Shift+R (Mac) / Ctrl+Shift+R (Windows)
        still stuck   -> incognito window or a different browser
Desktop: check for an update and fully restart the app
         (a known v1.8555.x build greys out the Connectors panel)

Then confirm the tool isn’t muted for this conversation. In the chat composer:

Click "+" (lower-left) or type "/"  -> Connectors -> Tool access
  -> set "Auto" or "Always available" (not "On demand")
For web search: click the slider icon in the input -> turn on "Web search"

On demand only loads connectors when Claude decides it needs them, which can look like the tool is “missing” mid-chat.

Step 5: Request beta / preview access

For a limited-preview tool, the tool card usually has a “Request access” button — submit it with your use case. On Enterprise, ask your account team to add your workspace to the cohort.

Step 6: Stand up a fallback

While it’s broken, keep working:

Web search down -> search manually, paste the results into the chat
Connector down  -> upload the file or copy-paste the content
A specific tool down -> screenshot the output and show it to Claude

Note how long it’s been down so admin or support can correlate it to their logs.

How to confirm it’s fixed

Reload Claude (hard refresh on web, or restart the desktop app).
Start a new conversation — old chats can cache the disabled state.
Open the composer’s + > Connectors > Tool access and confirm the tool is listed and not greyed.
Run a one-line task that actually exercises it (for web search: “search the web for today’s date”; for a connector: ask it to read one file). If it returns live, tool-backed output, you’re done.

Prevention

Keep a short doc (Notion / wiki) mapping each workflow-critical tool to its purpose and a fallback.
Never put a critical workflow on a single tool — always keep an alternate path.
Subscribe to status.anthropic.com notifications.
On Team/Enterprise, ask admins to announce tool and connector changes instead of silent toggles.
Treat new Anthropic features as beta first; don’t deeply integrate a pre-GA tool into a critical workflow.
Review monthly which tools you rely on versus your current plan, to catch silent downgrades.

FAQ

Why did a Claude tool work yesterday and break today with no change from me? Your workspace state changed even if your settings didn’t. On Team/Enterprise the usual cause is an admin disabling it in Organization settings > Connectors or Admin settings > Capabilities; on personal plans it’s usually a stale desktop app or browser cache. Check the status page, your plan, then admin policy in that order.

How do I tell if it’s an Anthropic outage or just my account? Check status.anthropic.com first — if there’s an open incident naming the tool (Anthropic logs per-connector incidents like the Google Drive one), it’s their side and you wait. If the status page is green but a coworker on the same workspace can use the tool, the problem is local to your account or client.

The connector panel is greyed out and won’t click at all — is that my fault? Not necessarily. A specific Claude Desktop build (the v1.8555.x line in mid-2026) shipped with the Customize > Connectors panel un-clickable. Update to the latest desktop version and fully restart, or use the web app to confirm the connector is actually enabled.

Why can my coworker use web search but I can’t? Web search has two gates: the admin must enable it under Admin settings > Capabilities, and you must turn it on per chat via the slider icon in the composer. If the admin gate is open, click the slider and toggle “Web search” on — it’s off by default in new chats.

Does upgrading my plan always restore a missing tool? Only if the tool is genuinely tier-gated. Connectors work on Free (one custom connector), Pro, and Max; admin-controlled capabilities and Enterprise Search need Team or Enterprise. If a coworker on the same plan can use it, upgrading won’t help — it’s an admin policy or client-cache issue instead.

I get “not available in your region” — how do I fix that? This is a region or data-residency lock. Turn off any VPN that lands you in an unsupported country, and confirm your location against Anthropic’s supported countries list. China-controlled organizations are restricted by policy, which a VPN won’t lawfully work around.

Tags: #Claude #Debug #Troubleshooting