Assistants connected through MCP
What Claude, ChatGPT or another assistant you connect to iyedy can read and change, what iyedy keeps, and how to remove the access.
On this page
You can connect an assistant of your own, such as Claude, Claude Code, ChatGPT or a coding assistant (Codex, VS Code with GitHub Copilot, Zed, Cursor, Gemini CLI), to iyedy through the Model Context Protocol (MCP). It then works on your diagrams in its own conversation. This page is for the person who decides whether to allow that: what the assistant receives, what it can change, and what stays in iyedy. To set it up, see Connect iyedy to Claude or Connect iyedy to ChatGPT, or Connect a coding assistant.
It acts as you
You sign in to iyedy from the assistant, on auth.iyedy.com, and approve what it asks for. The assistant never sees your password. From then on it reaches exactly the workspaces, diagrams and roles your account has, never more. A diagram you cannot open does not exist for it.
The access page lists what the assistant will be able to do: read your diagrams; search elements and analyse impact; preview changes and submit proposals that a person reviews. Nothing on that list edits, deletes or shares a diagram.
What it can read
Only what your account can read, up to a ceiling of classification:
| Where | An assistant connected through MCP reads up to |
|---|---|
| A personal workspace | Confidential |
| A Team or Enterprise organisation | Internal |
| Any space | never Restricted |
A diagram above the ceiling is never listed, never found by a search and never walked by an impact analysis; asked for directly, it answers “not found”. Values in a model that look like secrets are replaced before they leave iyedy.
What it can change
Nothing directly. An assistant can preview a change and submit it as a proposal, or withdraw a proposal it made. The proposal waits in iyedy, labelled with the assistant's name, until someone who can edit the diagram applies it or rejects it. A proposal nobody handles is deleted 30 days after it was made (How proposals reach your team).
Where the data goes
- What the assistant receives. The results of the tools it calls go to the assistant, under your agreement with its publisher and its terms. iyedy does not decide what the assistant does with them.
- What iyedy keeps. Your diagrams stay in iyedy, with the proposals waiting for a person. iyedy does not use your diagrams to train AI models.
- iyedy's own Assistant is a different thing, with its own rules: see AI and your diagrams.
The legal text is the privacy policy, section “Who receives your data”.
In an organisation
In a Team or Enterprise organisation, access for connected assistants is off until an owner of the organisation asks support@iyedy.com to turn it on (Claude and MCP for your organisation). If the organisation requires single sign-on, the assistant's sign-in goes through it too.
Remove the access
- In the assistant. Disconnect iyedy there; in Claude Code, see Connect iyedy to Claude; in ChatGPT, see Connect iyedy to ChatGPT; for a coding assistant, see its guide in Connect a coding assistant.
- On iyedy's side. There is no screen for it yet: write to support@iyedy.com, and we remove the access. The assistant then has to ask you again.
What this means for you
- Connect only an assistant you trust, from the account whose diagrams it should see.
- Classify sensitive diagrams before you connect: the ceiling applies from the first call.
- Read every proposal before you apply it, as you would a colleague's.
Was this page helpful?Your answer is anonymous and counts only if you accepted measurement.
What went wrong?
Don't write personal data.