An AI app cannot connect

Pilot

Connected AI apps are currently enabled only for pilot organizations.

Go through the questions in order; the first one that fits is usually the reason. The codes in brackets are what the AI app or the dashboard reports.

Is the server address right?

The address has to be exactly https://mcp.focus.workify360.com/mcp, starting with https:// and ending with /mcp. An address without /mcp, or the address of the dashboard, does not work. Your owner or admin can copy the address from Settings → AI (connecting an AI app).

Are connected AI apps available to your organization?

When the app or the page after sign-in says that connected AI apps are not available (mcp_not_available), they are not part of your organization’s plan, your organization is not in the pilot, or they are turned off for this service. You cannot change this yourself; Settings → AI shows your owner and admins which of these applies.

Is AI access on?

When the answer is that AI access is turned off in your organization (ai_disabled), the owner has not turned on Allow AI access and Allow external AI apps (MCP) under Settings → AI, or has turned one of them off (AI settings).

Has your organization approved the app?

When the page after sign-in says that your organization has not approved the app yet (client_not_allowed), your request has been recorded. The owner sees it under Settings → AI → Apps and decides (approving AI apps). Try again once the app is approved. If the owner revoked the app, it cannot connect until it is approved again.

The owner cannot turn on access or approve the app

• The change asks for a confirmation (acknowledgement_required): turning something on or approving an app widens what leaves Focus, so the owner has to confirm the summary of what will be shared before saving. Save again and confirm it.
• The owner is asked to sign in again (step_up_required): turning something on and approving an app need a sign-in within the last 10 minutes (turning things off does not) (confirming sensitive actions).

Adding an app by its client ID fails

• The app’s description breaks the rules (client_metadata_invalid): the client ID has to be an https:// address, the document at that address has to name exactly that client ID, its return addresses have to use https:// or point to the computer itself, and it must not ask for a client secret or keys. Check the client ID with the app’s provider; a typo or an old address is the usual cause.
• The app’s description cannot be read (client_metadata_unreachable): Focus could not read the document within 5 seconds, it is larger than 64 KB, it redirects to another address, its certificate is not valid, or its address is not a public one. Try again later; if it keeps failing, the app’s provider has to fix it.

The app needs team data

When the app asks about other people or teams and gets insufficient_scope, you connected it with Only my data. The app sends you back to the consent page to allow Team data I can see; this is offered only when your role sees other people’s data (what AI apps can see).

The app was connected and stopped working

The app has to be connected again when:

• you or an admin chose Disconnect, or the owner revoked the app;
• your account was deactivated, or you left the organization;
• AI access was turned off (the app gets ai_disabled until it is turned on again).

When your role changes, the app keeps working with what your new role allows.

If none of this fits, contact support with the name of the app, the time it failed and the code it showed.