Connect iyedy to VS Code and GitHub Copilot

Add iyedy to Visual Studio Code as an MCP server and work with your architecture diagrams in GitHub Copilot's chat, next to your code. Copilot 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 VS Code, and finish creating your account. Copilot sees exactly the diagrams this account can read.
• A recent VS Code (1.106 or later) with GitHub Copilot, signed in to GitHub. If your company manages GitHub Copilot, its policy must allow MCP servers.
• In an iyedy organisation (Team, Enterprise), access for MCP clients is off until an owner asks support@iyedy.com to turn it on, and VS Code 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 an MCP server

   Open the Command Palette (Ctrl Shift P), run MCP: Add Server, choose an HTTP server and enter this address:

   https://app.iyedy.com/mcp

   Name it iyedy and keep it in your user profile, so that it works in every folder you open.

2. Let VS Code sign in

   VS Code starts the server, finds that iyedy uses OAuth and asks whether iyedy may sign in. Accept: your browser opens iyedy's sign-in page on auth.iyedy.com. You give no client ID: VS Code 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 Visual Studio Code on vscode.dev, read what VS Code asks for, then select Allow.

   auth.iyedy.com1

   Visual Studio Code wants to use your iyedy account

   Application

   Visual Studio Code

   Site

   vscode.dev

   2

   Visual Studio Code 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

5. Ask Copilot

   Open the chat, choose agent mode, and check that iyedy's tools are listed in the tools picker. Then try: “List my iyedy diagrams and explain how the claims platform is built.”

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

{
  "servers": {
    "iyedy": {
      "type": "http",
      "url": "https://app.iyedy.com/mcp"
    }
  }
}

Use it

In agent mode, Copilot picks iyedy's tools when your request needs your diagrams; name iyedy to help it. 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 workspace.”
• “Prepare a proposal that adds a Fraud Scoring service called by the Claims API.”

VS Code asks you to confirm a tool call before it runs it, unless you allowed that tool for the session.

What Copilot can do

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

• It acts as you. VS Code 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. Copilot 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 Copilot does with what it reads is covered by your GitHub Copilot terms and your company's Copilot settings.

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

Disconnect

• In VS Code. Sign out of iyedy from the Accounts menu, at the bottom of the activity bar. To remove iyedy, run MCP: List Servers, or delete its entry with MCP: Open User Configuration.
• On iyedy's side. There is no screen for this yet: write to support@iyedy.com. Support removes VS Code'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. VS Code 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 VS Code. 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.