Troubleshooting
The assistant cannot find or reach the server
Section titled “The assistant cannot find or reach the server”The address https://<your Foldr address>/mcp answers 404 when connected apps are off for the site, or the plan does not include them. An administrator checks Settings > Connected apps. Use the address you open Foldr at, including a custom domain if you have one.
The assistant connects and signs in, then every call is refused with 401
Section titled “The assistant connects and signs in, then every call is refused with 401”The assistant did not name the MCP address as the resource when it asked to sign in, so Foldr issued an API token, and /mcp accepts only a token tied to it. The refusal is a 401 with WWW-Authenticate: Bearer resource_metadata="https://<your Foldr address>/.well-known/oauth-protected-resource/mcp", error="invalid_token". A standard MCP client reads that, signs in again and sends resource=https://<your Foldr address>/mcp. If yours does not, it cannot connect to Foldr: ask its vendor for a client that sends the resource parameter (RFC 8707), as the MCP specification requires. Its sign-in still works on the REST API.
“Your account isn’t allowed to connect apps yet”
Section titled ““Your account isn’t allowed to connect apps yet””You are not on the Connect apps list. Ask an administrator to add you under Settings > Connected apps > Who may connect apps.
“(App) is waiting for an administrator to approve it”
Section titled ““(App) is waiting for an administrator to approve it””Approval is on. An administrator clicks Approve beside the app on the Apps tab.
It worked and then stopped
Section titled “It worked and then stopped”- Your connection ran out. It lasts up to 90 days by default, and ends after 30 days unused. Connect the app again.
- An administrator revoked the app or disconnected you. Check Security > Connected apps in your account settings.
- You lost Connect apps. Your apps are paused, and the Security page says so. They resume when you have it back.
- Your account was disabled or removed. Every connection ended with it.
The assistant sees fewer shares than I do
Section titled “The assistant sees fewer shares than I do”A share that opens with your own sign-in on its storage cannot be opened by a connected app. See Shares you may not see. A share you cannot open in Foldr is not shown either.
A change tool is refused
Section titled “A change tool is refused”- The tool needs a scope the app does not hold. The refusal names the scope. An administrator agrees scopes under Policy… on the app, and you agree them when you connect, so connect the app again after the policy changes.
- The share is not one the policy names, or you cannot write to it.
- The app reached its daily limit. It counts per person per app per day (UTC).
A tool the assistant remembers can go missing after an administrator narrows the policy. The assistant caches the tool list. Starting a new chat refreshes it.
A sharing request returned no link
Section titled “A sharing request returned no link”By design. A request waits for an approver, and the assistant is never handed a link. After approval, find the link in Foldr.
A result looks cut
Section titled “A result looks cut”Results are cut at 64 KB, and the result ends with a note saying so. Ask for less: a narrower search, one folder, a page number.
The server answers 429 (too many requests)
Section titled “The server answers 429 (too many requests)”The limit is 240 requests a minute for each person from each source address. An assistant stuck in a loop can reach it. Stop the chat and try again in a minute. If many people on one site register new apps from one address in an hour, registration is limited to 30 an hour, and to 100 attempts a day for the site.
Still stuck
Section titled “Still stuck”Ask an administrator to look at Activity for the person. Tool calls appear as Used a Foldr tool from a connected AI app, and connections as Connected apps events.