Coding assistant troubleshooting
What to do when Codex, VS Code, Zed, Cursor or Gemini CLI cannot sign in to iyedy, keeps asking you to sign in, or cannot see a diagram.
On this page
Adding and signing in
The sign-in page answers 400 or “Client not found”
iyedy's sign-in does not know the client ID the assistant sent. Codex, VS Code and Zed need no client ID: remove any client ID you set for iyedy in their settings. Cursor needs CLIENT_ID cursor, Gemini CLI clientId gemini-cli, exactly. Check that the address is https://app.iyedy.com/mcp, then sign in again. See each guide in Connect a coding assistant.
The assistant says the server does not support dynamic client registration
iyedy never lets a client register itself. Cursor and Gemini CLI need iyedy's client ID in their configuration: copy the block of Cursor or Gemini CLI again. For another assistant, see Connect another MCP client.
The sign-in page answers 400 about the redirect (redirect_uri)
The assistant asked iyedy to send the sign-in back to an address iyedy does not expect. VS Code uses port 33418 and Cursor port 8787 on your computer: close the app or the other sign-in that holds the port, then try again. Codex, Zed and Gemini CLI pick a free port themselves; check that you did not set a callback address or port of your own in their settings.
The assistant reports invalid_scope at once, before any sign-in page
The assistant asked for a scope iyedy does not give it, and iyedy refused the request before showing any page. In Cursor and Gemini CLI, keep exactly the four scopes of the guide: cartouche.read, cartouche.graph, cartouche.propose and offline_access.
The browser does not open, or the sign-in never comes back
The sign-in comes back to the assistant on your own computer. Run Codex and Gemini CLI on the computer where your browser runs, not over a remote shell or in a container. Then start the sign-in again: in Codex with the login command of its guide, in Gemini CLI with /mcp auth iyedy.
“No iyedy account uses this sign-in yet.”
You signed in with an identity that has no iyedy account. Open app.iyedy.com, sign in with the same identity, finish creating your account, then connect again. The connection never creates an account for you.
Staying connected
The assistant asks you to sign in to iyedy again
Codex, VS Code, Cursor and Gemini CLI ask to stay connected while you are away and renew their access in the background, as long as they are used at least once every 30 days. Zed does not: it signs in again when your iyedy session ends, after about 30 minutes without use, 12 hours at most, longer if you ticked Remember me. In Cursor and Gemini CLI, check that offline_access is among the scopes. If support removed the access, sign in again.
Organisations
“MCP clients are turned off for this organization.”
Access for MCP clients is off in this iyedy organisation; a request may also answer “MCP clients are not enabled for this organization.” An owner asks support@iyedy.com to turn it on. See Claude and MCP for your organisation.
“This organization does not allow … as an MCP client.”
The organisation's list of allowed clients does not name your assistant. Without a list, a Team organisation allows Claude and Claude Code only, and an Enterprise organisation none. An owner asks support to add the assistant by its name in iyedy: Codex, VS Code, Zed, Cursor or Gemini CLI.
The assistant asks for the organisation's company sign-in
The organisation asks its members for its company sign-in. Sign out of iyedy in the assistant, connect again and use your work address.
Using iyedy
The assistant does not see a diagram
The assistant sees only what your iyedy account can read, up to the ceiling: Confidential on a personal workspace, Internal in Team and Enterprise. Check that you can open the diagram in iyedy and its classification.
The assistant cannot submit a proposal
Proposals need a role that can edit the diagram, and the permission to preview changes and submit proposals on the access page. Ask an editor of the diagram, or sign out and connect again to approve that permission.
Still stuck? Contact support with the assistant's name, the time of the call and the name of the diagram, never a token.
Was this page helpful?Your answer is anonymous and counts only if you accepted measurement.
What went wrong?
Don't write personal data.