Claude and MCP for your organisation
Claude, ChatGPT and the coding assistants connect to iyedy through MCP and work with the diagrams their user can read. In a Team or Enterprise organisation, this access is off until an owner asks support to turn it on. They then read up to Internal, and never change a model: a person applies each proposal.
On this page
There is no screen for this in iyedy yet. An owner of the organisation writes to support@iyedy.com to turn on access for Claude, ChatGPT and the coding assistants.
Before you start
- You are an owner of the organisation.
- Decide what Claude may read. In Team and Enterprise, Claude reads diagrams up to Internal; Confidential and Restricted diagrams do not exist for it. Your organisation can keep that limit. See Classification and AI ceiling.
- Know which clients your members use. claude.ai, Claude Desktop and the Claude mobile apps connect from the Claude directory or with a custom connector added with iyedy's address; Claude Code connects with one command. See Connect iyedy to Claude. ChatGPT connects from ChatGPT on the web, on Business, Enterprise, Edu and Pro. See Connect iyedy to ChatGPT. Codex, VS Code with GitHub Copilot, Zed, Cursor and Gemini CLI connect from your members' computers. See Connect a coding assistant.
Ask for it
Write to support@iyedy.com from the address of an owner, with:
- the organisation's name, as the context selector shows it;
- the clients to allow: Claude, Claude Code, ChatGPT, Codex, VS Code, Zed, Cursor, Gemini CLI. Without a list, a Team organisation allows Claude and Claude Code only; the others are allowed only when you name them. An Enterprise organisation needs the list.
Until access is on, a member who tries gets the message MCP clients are not enabled for this organization.
What members do next
Each member connects Claude, ChatGPT or a coding assistant with their own iyedy account: see Connect iyedy to Claude, Connect iyedy to ChatGPT and Connect a coding assistant. Claude then sees exactly what that member can read, up to Internal, and nothing in a workspace they have no role in. If your organisation asks for its company sign-in, members sign in with their work address.
What connected assistants can and cannot do
- Read and analyse: diagrams, views, versions, findings, dependencies across diagrams. See MCP tools reference.
- Propose, never apply: a proposal from a connected assistant waits in iyedy, labelled with the app it came from, until someone who can edit the diagram applies or rejects it.
- Leave a trace: each refusal by your organisation's rule is recorded in its audit log.
Turn it off
Write to support@iyedy.com. A member can also disconnect their assistant on their side at any time. See Connect iyedy to Claude, Connect iyedy to ChatGPT and the guide of each coding assistant.
If it doesn't work
“MCP clients are not enabled for this organization.”
Access for MCP clients, every assistant alike, is still off in this organisation. An owner asks support to turn it on.
Claude does not see a diagram of the organisation
The diagram is above Internal, or the member has no access to it. Claude, like ChatGPT, sees only what the member can read, up to Internal.
Claude asks for the organisation's company sign-in
The organisation asks its members for its company sign-in. Disconnect iyedy in your assistant, connect again and use the work address. In Claude Code, run /mcp and select iyedy to sign in again.
More cases: Claude troubleshooting, ChatGPT troubleshooting and Coding assistant troubleshooting.
Was this page helpful?Your answer is anonymous and counts only if you accepted measurement.
What went wrong?
Don't write personal data.