I connect Claude or the API

In about half an hour you work with your diagrams from Claude Code and from your own scripts. Claude reads your models and prepares proposals; the API reads, checks and proposes. Neither ever changes a model without a person.

This path is for you if

You want Claude, a script or a pipeline to read your architecture, run iyedy's checks or prepare changes, without opening the editor.

Not for you if you want to draw diagrams by hand: take I’m new to iyedy.

At the end you have

• iyedy connected to Claude Code, answering with your own diagrams.
• A clear view of the MCP tools, and of how a proposal from Claude reaches the people who apply it.
• A token with the right scopes, and a first API call that works.

The steps

1. Connect iyedy to Claude or Use iyedy in Claude Code

   Guide · 5 min

   Add iyedy to Claude Code and sign in once.
2. MCP tools reference

   Reference

   The 24 tools: 22 that read, 2 that store a proposal.
3. How proposals reach your team

   Explanation

   How a proposal from Claude waits in iyedy until a person applies or rejects it.
4. Your first API call

   Tutorial · 10 min

   Read your diagrams from a script, in a few minutes.
5. Create and manage API tokens

   Guide · 5 min

   Personal tokens and their lifetime; service accounts for CI.
6. Scopes

   Reference

   Give a token only what it needs: read, graph, propose.
7. Rate limits and errors

   Reference

   Requests per minute by plan, and what each error means.

Common questions

• What Claude can do with iyedy: what Claude can and cannot do with your diagrams.
• Assistants connected through MCP: what an AI client connected through MCP can read.
• Claude troubleshooting: Claude asks you to sign in again, or a diagram is missing.

Other paths