Connect iyedy to Zed

Add iyedy to Zed as a remote MCP server and work with your architecture diagrams in Zed's Agent Panel, next to your code. The agent 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 Zed, and finish creating your account. Zed sees exactly the diagrams this account can read.
• A recent Zed with its agent set up (Agent Panel), on a computer with a web 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 Zed 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 as a remote server

   In Zed, open Settings, then AI, then MCP Servers. Select Add Server, then Add Remote Server, name it iyedy and enter this address, without any header:

   https://app.iyedy.com/mcp
2. Let Zed sign in

   Zed finds that iyedy uses OAuth. Select Authenticate next to iyedy: your browser opens iyedy's sign-in page on auth.iyedy.com. You give no client ID: Zed introduces itself with its own public address, which iyedy knows.

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 Zed on zed.dev, read what Zed asks for, then select Allow.

   auth.iyedy.com1

   Zed wants to use your iyedy account

   Application

   Zed

   Site

   zed.dev

   2

   Zed 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

   3

   DenyAllow4

5. Ask Zed's agent

   In MCP Servers, the dot next to iyedy turns green. Open the Agent Panel and try: “List my iyedy diagrams and explain how the claims platform is built.”

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

{
  "context_servers": {
    "iyedy": {
      "url": "https://app.iyedy.com/mcp"
    }
  }
}

Use it

Name iyedy in your request: it helps the agent pick iyedy's tools. 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 project.”
• “Prepare a proposal that adds a Fraud Scoring service called by the Claims API.”

Zed does not ask to stay connected while you are away. Your iyedy session ends after about 30 minutes without use, 12 hours at most, longer if you ticked Remember me. Then select Authenticate again.

What Zed can do

The agent 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 Zed sees, what stays in iyedy

• It acts as you. Zed 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. The agent 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 happens to what the agent reads depends on the model provider you chose in Zed and its terms.

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

Disconnect

• In Zed. Remove iyedy in MCP Servers, or delete its entry from settings.json. Zed also forgets its sign-in.
• On iyedy's side. There is no screen for this yet: write to support@iyedy.com. Support removes Zed's access, which also ends its renewals; an access already issued stays valid for the rest of its 5 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. Zed 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 Zed. 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.