How-to guide

How to fix Agiflow connection problems

This guide shows you how to restore Agiflow when your AI assistant is disconnected, authorized to the wrong scope, missing expected tools, or using old project context.

Published 29 May 2026. Last updated 14 July 2026.

At a glance

If authorization failed or the wrong workspace or project is connected, disconnect Agiflow from your assistant and connect it again. In Agiflow, choose the intended access level and approve the authorization request.

If Agiflow appears connected but a tool or project is missing, check the MCP scope first. Then check whether the expected tool is available within that scope. If you reconnect or change scope, start a new conversation before verifying again.

Fix authorization and scope in the connection flow

Use this path when Agiflow is unavailable, authorization was denied, or the assistant opens the wrong workspace, project, goal, or task.

Prerequisites

You can sign in to Agiflow.
The workspace or project you want to authorize already exists.
Your AI assistant account or workspace policy allows Agiflow connections.

Reconnect and choose the intended access level

Open your assistant's connection settings and confirm that Agiflow is enabled.
If Agiflow is disconnected, authorization was denied, or the wrong scope is active, remove or disconnect the existing Agiflow connection. Then connect it again.
On Choose access level, select your organization.
If you want to restrict the connection, expand Limit access (optional) and select a project, work unit, or task. Leave it unrestricted only when the assistant needs workspace-level access.
Select Continue to Authorization.
Review the Authorization Request, then select Authorize.
Return to your assistant. If the client requires connections to be enabled per conversation, enable Agiflow and start a new conversation.

For client-specific connection settings, see Connect Agiflow to ChatGPT, Connect Agiflow to Claude, or Connect Cursor and coding agents.

Expected result

Agiflow appears as connected or enabled in the assistant. The connection is limited to the workspace, project, work unit, or task you approved.

Verify the connection

Ask:

What is my current Agiflow scope?

The response should name the scope you selected. If you granted project access, it should identify that project rather than another board.

Limitations and recovery

Connection labels vary between ChatGPT, Claude, Cursor, and other MCP clients. Use the matching connection guide if you cannot find the setting.
If Connect or custom connectors are unavailable, ask your assistant workspace administrator whether app or MCP connections are allowed.
If the wrong scope appears, reconnect and authorize the intended resource. A project-scoped connection cannot read another project.
Supported OpenAI app clients may show a Current Scope card with Change Scope. If your client does not show that action, reconnect through the client's connection settings.
If the correct scope appears but the assistant still mentions an old project, start a new conversation and verify again.

Next steps

See Choose a supported AI tool for client-specific setup, or Connect AI tools for endpoint and authentication details.