Connect iyedy to Gemini CLI

Add iyedy to Gemini CLI as a remote MCP server and work with your architecture diagrams from your terminal. Gemini CLI 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 Gemini CLI, and finish creating your account. Gemini CLI sees exactly the diagrams this account can read.
• A recent Gemini CLI, on a computer with a web browser. The sign-in comes back to Gemini CLI on this computer: it does not work over a remote shell or in a container without a browser.
• In an iyedy organisation (Team, Enterprise), access for MCP clients is off until an owner asks support@iyedy.com to turn it on, and Gemini CLI 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 settings.json

   Open ~/.gemini/settings.json and add iyedy to mcpServers, exactly as here:

   {
     "mcpServers": {
       "iyedy": {
         "httpUrl": "https://app.iyedy.com/mcp",
         "oauth": {
           "enabled": true,
           "clientId": "gemini-cli",
           "scopes": ["cartouche.read", "cartouche.graph", "cartouche.propose", "offline_access"]
         }
       }
     }
   }
   

   Save the file. Keep httpUrl (not url) and the four scopes: without them, Gemini CLI asks for scopes that iyedy does not give it, and the sign-in is refused.

2. Start the sign-in

   Start Gemini CLI and type /mcp auth iyedy. Your browser opens iyedy's sign-in page on auth.iyedy.com.

3. Sign in to iyedy

   Sign in as you do in the app: e-mail and password, Google, or your organisation's single sign-on.

4. Approve the access

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

   auth.iyedy.com1

   Gemini CLI wants to use your iyedy account

   Gemini CLI 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)

   2

   DenyAllow3

5. Ask Gemini CLI

   Type /mcp to see iyedy connected with its tools, then try: “List my iyedy diagrams and explain how the claims platform is built.”

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

From your shell, the list of servers and their state:

$ gemini mcp list

Use it

Name iyedy in your request when you want Gemini CLI 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.”

Gemini CLI may ask you to confirm a tool call before it runs it, depending on your settings.

What Gemini CLI can do

Gemini CLI 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 Gemini CLI sees, what stays in iyedy

• It acts as you. Gemini CLI 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. Gemini CLI 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 Gemini CLI does with what it reads is covered by the terms of the Google account or key it uses.

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

Disconnect

• In Gemini CLI. Remove iyedy from your settings:

$ gemini mcp remove --scope user iyedy$ gemini mcp remove \
    --scope user \
    iyedy

Gemini CLI keeps its sign-ins in ~/.gemini/mcp-oauth-tokens.json: delete iyedy's entry there to forget the sign-in too.

• On iyedy's side. There is no screen for this yet: write to support@iyedy.com. Support removes Gemini CLI'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. Gemini CLI 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 Gemini CLI. Members then connect 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.