AI Says "I Can't Access Your App" — Here's What's Actually Wrong

You set up the connection, it worked yesterday, and now AI says it can't access your Gmail/Notion/Calendar. This is the most common issue people hit with AI tool connections, and it's almost never what you think it is. I've debugged this dozens of times. Here's the actual checklist, from most likely to least likely.

The 30-Second Fix (Try This First)

Disconnect and reconnect the app. In 60% of cases, the OAuth token expired or got corrupted. The fix is the same as "turn it off and on again." Go to your connector settings, disconnect the app, reconnect it, re-authorize. Done.

If that doesn't work, keep reading.

The Real Causes (Ranked by Frequency)

1. Token expired and didn't auto-refresh (most common). Google tokens expire every hour. Most connectors auto-refresh them, but sometimes the refresh fails silently. You don't see an error — AI just says "can't access." The reconnect fix above solves this.

2. You authorized the wrong account. You have a personal Gmail and a work Gmail. You connected the personal one but you're asking about work emails. AI successfully connects but finds nothing relevant. Check which account you authorized — it's not always obvious in the OAuth flow.

3. Permissions were too narrow. During OAuth, you might have unchecked some permission boxes. Now AI can search your emails but can't read their content, or can read your calendar but can't create events. Re-authorize and check all the permission boxes.

4. The MCP server crashed (for non-built-in connectors). If you're using an independent MCP server (not a built-in connector), the server process might have stopped. Check if it's still running. For Docker-based servers, run docker ps to verify.

5. Config file got corrupted. For Claude Desktop, one misplaced comma in claude_desktop_config.json breaks everything. Paste your config into jsonlint.com to check. Common mistakes: trailing comma after the last item, wrong quote characters (curly quotes instead of straight), or accidentally editing the wrong config file.

How to Tell Which Problem You Have

"Can't access" with no error details → Usually token expiry (#1). Reconnect.

AI connects but returns wrong data → Wrong account (#2). Check which account.

AI can search but can't read/write → Narrow permissions (#3). Re-authorize.

"Connection refused" or "server not found" → Server crashed (#4). Restart it.

Nothing works at all, everything says error → Config corruption (#5). Validate JSON.

The Nuclear Option

If you've tried everything and nothing works, start clean: delete all MCP configs, remove all connected accounts, restart your AI tool, and set up one connection at a time. Test each one before adding the next.

Or consider a simpler architecture. Instead of managing 3-5 separate MCP servers with separate configs and separate auth, a unified tool layer gives you one URL, one auth flow, one thing that can break. When something goes wrong, there's one place to check.