Connector troubleshooting

Most connector problems are one of a short list of known things, and several of them are working as intended. Read down this page before assuming something is broken.

Claude will not let me add the connector

Any Claude plan can add Floot, including Claude Free. The free plan is fine for trying the connector out; a paid Claude plan is recommended for real builds. If nothing happens on a Team or Enterprise workspace, see the next section.

On Claude Team or Enterprise, nothing happens

An organization Owner has to enable Floot once for the whole organization, from the Claude connector directory or under Organization settings → Connectors. Each member then clicks Connect for themselves. A member cannot self-install before the Owner has enabled it.

ChatGPT asks permission before every action

That is ChatGPT's default for connectors. A Floot build makes many tool calls, so the approval prompt reappears every few seconds and the build reads as stalled. Open Floot's app settings in ChatGPT and choose Allow all actions. You can change it back at any time.

My assistant says a Floot call was blocked, declined, or cancelled

Messages such as user cancelled MCP tool call, No approval received, or this tool requires approval, but the user declined are about your AI client's confirmation step. The card asking you to approve the action was dismissed, timed out, or never answered, so the request stopped there and did not reach Floot. Nothing was saved or changed. A preview that looks the same afterwards is showing the project as it really is.

Floot does not ask you to approve individual tool calls. When Floot itself refuses something, the refusal comes back as the tool's result and says why — a daily limit with its reset time, a missing project, a limit you set for that assistant, an error from your code.

1. 1

   Run the step again and approve it

   Ask your assistant to repeat the step, and choose Allow when the card appears. If there is an Always allow option, it saves you from being asked again for that tool.

2. 2

   Stop the prompts for the whole build

   In ChatGPT, open Floot's app settings and choose Allow all actions. In Claude, open Floot under Settings → Connectors and set its tools to Always allow, or work in Cowork with approvals skipped — see Build from Claude & ChatGPT.

3. 3

   If one tool keeps failing while the others work

   It was probably declined once in that chat, which some clients remember for the rest of the conversation, or it is switched off in the connector's per-tool settings. Switch it back on there and start a new chat.

4. 4

   If writes are still refused

   Disconnect Floot in your client, connect it again, and start a new chat. Your projects are not affected by reconnecting.

My assistant says the account owner set what it may do

That refusal comes from Floot: the assistant has a limit on your account page. It may be read only, unable to publish, or limited to one project. Nothing was changed. To change the limit, open Connected agents on the account page and click the assistant's access setting. A limited assistant has a shield next to its row. See Limit what an assistant can do.

"This tool call was blocked by OpenAI's safety checks"

ChatGPT shows this when its own safety check stops a tool call before sending it. The call never reached Floot: nothing ran, nothing was changed, and nothing is restricted on your Floot account or your project. The check runs inside ChatGPT, so Floot cannot see it or switch it off, and it can stop a request one time and let the same request through the next.

• Try again. If the same step is stopped twice, start a new chat and ask for it there.
• For database work, ask for the database tools. Tell your assistant to use query_database for reads and execute_sql for changes, instead of running a script. Most blocked calls are SQL sent through a script.
• Do the one blocked step from another assistant. The project is the same whichever assistant opens it, so you can make that change from Claude, for example, and carry on in ChatGPT afterwards.
• If it keeps happening, tell support and include a link to the chat.

ChatGPT only searches — it will not edit anything

In a regular ChatGPT chat, the Floot app from the ChatGPT app directory can create, edit, and publish your apps. Some ChatGPT features, such as deep research, can use only two tools from any connector, named search and fetch. Floot ships both, but those two only search and read your projects. It is not a Floot restriction — Floot registers the same full tool set for every client, and which tools ChatGPT puts in front of the model is decided on ChatGPT's side. If ChatGPT only searches, start a new regular chat (not deep research), add Floot from the + menu or start your message with @Floot, and ask it to make the change. If it still will not edit, use another client — see Connect any MCP client.

My assistant does not seem to know about Floot

Enabling a connector is usually per chat. In Claude, mention with Floot in your message. In ChatGPT, add Floot from the + or tools menu, or start your message with @Floot. In other clients, switch Floot's tools on for the chat. If it still does not appear, check the connector is enabled in the client's own settings and start a new chat.

The server URL will not open in my browser

It is not meant to. https://mcp.floot.com/mcp answers MCP requests, not browser requests. It goes in your client's MCP server settings — see Connect any MCP client.

My client is asking for an API key or bearer token

Leave those fields empty. Floot authenticates with OAuth: your client opens a Floot page in your browser and you approve the connection there. Floot gives you no token or key to paste. Floot also requires PKCE with S256, so a client that offers only plain or no PKCE cannot connect at all.

The Floot sign-in page does not take my password

Floot accounts have no password, so there is none to type. On the sign-in page your client opens, use Google, GitHub, Microsoft, or your email address: Floot emails you a 6-digit code to type into that same page, in the same browser (there is no sign-in link in the email). Use the same email address your projects are under: signing in with a different one opens a different Floot account, and your projects will not be there.

Sign-in ends on a Floot page instead of back in my chat

That is the normal end of the flow. Consent runs on floot.com so your Floot credentials stay on Floot, and the page you are left looking at is Floot's, telling you to go back and enable Floot in your chat. Nothing has gone wrong — switch back to your assistant and start building.

The connection drops, or the tools disappear

There is no session to lose. Floot's MCP server holds no state between calls and issues no session ids — every request carries its own token and stands alone. When a client reports a lost connection, what it actually needs is to list Floot's tools again, which reconnecting or reloading the client does. Nothing on Floot's side is holding stale state.

ChatGPT says Floot is disabled or unavailable, "Unknown tool", or "Too many requests"

These messages appear inside ChatGPT, most often late in a long conversation: Floot shown as disabled or unavailable, Unknown tool, Invalid MCP request metadata, Resource not found: Floot.read_file, or a Too many requests banner. When one of them appears, the call has not reached Floot. Your work is saved in Floot, not in the chat, so nothing is lost by starting again.

My assistant says no browser picked up the code

Reading the live app's screen, or clicking something in it, runs inside a Floot tab on your own device. So a tab with the project has to be open, and it has to be in front: browsers freeze tabs that are in the background.

• Open the project's preview link, keep it in its own window next to your chat, and ask again.
• If it keeps happening in Chrome, add floot.com under Settings → Performance → Always keep these sites active.
• On a phone, keep the preview on screen while your assistant works.

Work that does not need the page — running a script on the server, querying the database, a typecheck — runs on Floot's servers and needs no tab open.

My assistant says it cannot publish

It can. publish_app and unpublish_app are real tools, and publishing through them runs the same code as the Publish button in the Floot web app. If your assistant insists publishing has to happen in the browser, ask it directly to call publish_app. The things it genuinely cannot do are connecting an Apple or Google Play account (which native app builds need), starting a mobile test build, switching an app between public and private, and finishing a custom-domain setup — see What your AI can do.

A publish never finishes

The connector waits at most 15 minutes for a production build. Past that the status check reports the publish as failed rather than still running, so your assistant stops polling and tells you instead of waiting forever. Ask it to publish again.

Actions are being refused

You have hit a build-action limit. The refusal names which limit and when it resets, and status polling, list_projects, get_preview_url, cancel_request, and unpublish_app keep working meanwhile. On Pro and Power it also offers an Action Boost if you cannot wait for the reset. See Build actions.

"Too many Floot calls are running at once for this account"

Floot runs at most 50 calls at the same time for one account. This is not the daily limit and nothing is counted: wait a moment, then ask your assistant to carry on with fewer calls in parallel.

I upgraded, but my assistant still says I am on Free

Your assistant is almost certainly connected to a different Floot account from the one you paid on — two Google accounts, two browsers, or a sign-in that created a second account. Limits follow the account your assistant is connected as. Use the upgrade link in your assistant's limit message rather than going to floot.com directly: it shows which account your assistant is connected to before you pay. If you already paid on the other one, see Your account.

My assistant says "Project not found", or cannot see a project I know exists

The full message is Project … not found or you don't have access. It means the Floot account your assistant is connected as cannot open that project. The project is almost never gone.

• Give it the link, not the name. Start a new chat and paste the project's link from your dashboard, rather than typing a name or an id from memory.
• Check which account the project is on. A project belongs to the Floot account your assistant was connected as when it created the project, which may be a second Google account or another email. If the project is on your dashboard at floot.com but your assistant cannot find it, the assistant is connected as a different account: disconnect Floot in the assistant, sign in to floot.com as the account that owns the project in the same browser, and connect again.
• A mistyped id. Assistants sometimes change a character or two of a project id. When the id is that close to one of your projects, the message names the project it probably meant.
• Check it is not someone else's project. A project another person shared with you needs a paid Floot plan on your own account before the connector will open it — see the section further down.

For a project that is missing from your dashboard as well, see A project is missing, or you have two accounts.

Sign-in fails with a redirect or callback error

Floot accepts a client's sign-in callback only on an https URL, on localhost or 127.0.0.1, or from Cursor's desktop app. A desktop client that returns through a different custom URL scheme cannot connect yet — tell support which client it is.

A project someone shared with me will not open

Opening a project owned by another Floot user over the connector needs a paid Floot plan on your own account, for reading as well as writing. A public project's code is the exception: anyone can read it, though not its database, logs or stored files. Projects you own yourself are never affected.