Most connection problems come down to one of three things: the agent's sign-in, what you allowed it to do, or an out-of-date copy of Bloomlight's tools. Find your agent below. If you haven't connected one yet, start with Connect an AI agent to Bloomlight.
Any agent
"Agent connections need a paid plan"
None of your accounts is on a paid plan. Upgrade the account that holds your websites, then connect the agent again.
The agent can't see one of your websites
An agent only sees the websites you ticked when you connected it, and websites you add later aren't included automatically. Sign the agent in again: the connect screen shows the connection you already have, so tick the missing website and save. It also has to be on an account with agent connections, and you need access to it yourself.
The agent is refused a change
Either you didn't allow that kind of change when you connected it, or your role on the website doesn't allow it. An agent can never do more than you can: if you can only view a website, so can your agent. For the first case, sign the agent in again and tick the permission.
An audit is refused
Each agent can audit up to 5 pages a day, on top of your plan's on-demand audits, and a page that's already being audited can't start another. An audit takes about a minute; the agent can ask for its status until it's done.
The agent suddenly asks you to sign in again
Connections last 90 days, and revoking one in Connected apps signs it out everywhere. Sign in again to continue.
Claude Code
A new Bloomlight tool doesn't show up
If you connected Bloomlight as a connector on claude.ai, Claude Code can keep an old copy of its tools even after you reconnect or restart. Add Bloomlight to Claude Code directly instead. Remove the connector under Connectors on claude.ai, then, in your terminal, remove any copy Claude Code still has and add it again:
claude mcp list
claude mcp remove bloomlight
claude mcp add --transport http --scope user bloomlight https://mcp.bloomlight.app
Use whatever name claude mcp list shows for Bloomlight. Then start Claude Code, type
/mcp, pick bloomlight and choose Authenticate.
Bloomlight works in one folder but not another
claude mcp add adds a server to the folder you run it in unless you say otherwise. From the folder
where it works, remove that copy and add it again for every folder:
claude mcp remove bloomlight -s local
claude mcp add --transport http --scope user bloomlight https://mcp.bloomlight.app"Insufficient scope"
The agent tried something you didn't allow. Claude Code opens the connect screen in your browser so you can allow
it; approve it there and Claude Code carries on. If no browser opens, type /mcp, pick bloomlight and
sign in again.
Codex
"Insufficient scope", or Codex says it only has read access
Codex tried something you didn't allow when you connected it, such as ignoring a finding. Unlike Claude Code, it doesn't ask you to allow more, and it can't tell which permission is missing, so it may say the connection is read-only. Sign it in again from your terminal:
codex mcp logout bloomlight
codex mcp login bloomlight
The connect screen shows the connection you already have. Tick the permission and save. Then run
codex resume to pick up where you left off, and ask Codex to try again.
Antigravity CLI
"Insufficient scope", or a change is refused
Antigravity CLI tried something you didn't allow when you connected it. Like Codex, it doesn't ask you to allow
more, but you can fix it without leaving the CLI. Type /mcp, pick bloomlight, choose Sign out, then
choose Authenticate. The connect screen shows the connection you already have: tick the permission, save, and
paste the code back into Antigravity CLI. Then ask it to try again.