Connect iyedy to Codex

Add iyedy to Codex with one command and work with your architecture diagrams next to your code. Codex reads your models, runs iyedy's checks and prepares changes. It never edits a model itself; you, or someone who can edit the diagram, apply each change in iyedy.

Before you start

• An iyedy account. Sign in once at app.iyedy.com with the identity you will use from Codex, and finish creating your account. Codex sees exactly the diagrams this account can read.
• A recent Codex CLI, signed in to your OpenAI account, on a computer with a web browser. The sign-in comes back to Codex on this computer, so run the command where you work, not over a remote shell.
• In an iyedy organisation (Team, Enterprise), access for MCP clients is off until an owner asks support@iyedy.com to turn it on, and Codex must be on the organisation's list of allowed clients (see In an iyedy organisation). Your personal workspace works right away.

Set up

1. Add iyedy to Codex

   In a terminal, run:

   TerminalCopy

   $ codex mcp add iyedy --url https://app.iyedy.com/mcp$ codex mcp add iyedy \
       --url \
       https://app.iyedy.com/mcp

   Codex adds iyedy to its settings, finds that iyedy uses OAuth and opens your browser. You give no client ID: Codex introduces itself with its own public address, which iyedy knows.

2. Sign in to iyedy

   The browser opens iyedy's sign-in page on auth.iyedy.com. Sign in as you do in the app: e-mail and password, Google, or your organisation's single sign-on.

3. Approve the access

   Check that the page is on auth.iyedy.com and that it names Codex on chatgpt.com, read what Codex asks for, then select Allow.

   auth.iyedy.com1

   Codex wants to use your iyedy account

   Application

   Codex

   Site

   chatgpt.com

   2

   Codex will be able to:

   • Read your iyedy diagrams: models, views, versions and findings
   • Search elements and analyse impact across your iyedy diagrams
   • Preview changes and submit proposals that a person reviews in iyedy
   • Keep access while you are away (offline access)

   3

   DenyAllow4

4. Ask Codex

   Back in the terminal, Codex prints Successfully logged in. Start Codex and try: “List my iyedy diagrams and explain how the claims platform is built.”

   You are done when Codex answers with the names of your own diagrams.

If the browser did not open, or you closed it too early, sign in again at any time:

$ codex mcp login iyedy

Use it

Name iyedy in your request when you want Codex to use your diagrams. Try:

• “What depends on the Claims API? Show me the impact across my diagrams.”
• “Run the checks on the Claims Platform diagram and summarise the findings.”
• “Compare the containers view of the Claims Platform with the services in this repository.”
• “Prepare a proposal that adds a Fraud Scoring service called by the Claims API.”

Codex may ask you to approve a tool call before it runs it, depending on your Codex settings.

What Codex can do

Codex picks the tools from your request. Reading tools never change anything. The two tools that store something only reach a proposal, never the model.

What Codex sees, what stays in iyedy

• It acts as you. Codex reaches the same workspaces, diagrams and roles as your iyedy account, never more. A diagram you cannot open does not exist for it.
• Up to a ceiling. Confidential on personal workspaces, Internal on Team and Enterprise. Restricted diagrams are never sent. Values that look like secrets are replaced before they leave iyedy.
• Nothing changes without a person. Codex can submit a proposal or withdraw its own; you, or someone who can edit the diagram, apply it in iyedy.
• Your data. iyedy does not use your diagrams to train AI models. What Codex does with what it reads is covered by your OpenAI account terms and your workspace's settings.

Full details: Assistants connected through MCP and the Privacy policy.

Disconnect

• In Codex. Forget the sign-in, and remove iyedy from Codex if you no longer need it:

$ codex mcp logout iyedy

$ codex mcp remove iyedy

• On iyedy's side. There is no screen for this yet: write to support@iyedy.com. Support removes Codex's access, which also ends its renewals; an access already issued stays valid for the rest of its 15 minutes.

See Sign-in, permissions and disconnecting.

In an iyedy organisation

In Team and Enterprise, access for MCP clients stays off until an owner writes to support@iyedy.com. Codex connects only when the organisation's list of allowed clients names it: without a list, a Team organisation allows Claude and Claude Code only, and an Enterprise organisation none. The owner asks support to add Codex. Members then connect Codex with their own iyedy account, under the organisation's ceiling and its single sign-on. See Claude and MCP for your organisation.

If it doesn't work

More symptoms: Coding assistant troubleshooting.