← Plugin catalog
Productivity

nifdi diagrams

Nifdi Systems Limited v0.3.0

Editable cloud diagrams

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Write

Declared limitations

  • A request for photorealistic image generation is outside nifdi's structured diagram tools. Run in a new conversation.
  • The hosted connector cannot write directly to the reviewer's local filesystem. Run in a new conversation.
  • Sharing permissions cannot be changed through the nifdi MCP tools. Prerequisite: create the web architecture diagram with positive case 2. Run in a new conversation.

Not specified in the available declarations: pricing & account requirements.

Onboarding example

Create a three-tier web architecture diagram.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 17, 2026. Package observed Nov 17, 2026.

View package source →

Description

From the marketplace listing

Create and edit structured architecture, flow, system and network diagrams in the nifdi cloud. Refine diagrams through follow-up requests, view rendered previews, and open the nifdi editor to edit and share them.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 17, 2026. Last seen Nov 17, 2026.

Keywords

Files & skills

File archives

Plugin package19 files · 59.1 KBBrowse files →
Skill instructions
nifdi8.17 KB

View saved version →

---
name: nifdi
description: Author and edit nifdi block-and-connector diagrams — architecture diagrams, flowcharts, system and network diagrams — through a nifdi MCP server: the hosted one (server "nifdi", diagrams in the nifdi cloud, a Pro account) or the local one (server "nifdi-diagram", .nifdi.svg files in the project). Use when building or changing a diagram of boxes and arrows, recreating one from a picture or a written description, or when a task mentions nifdi, a nifdi.app diagram link, .nifdi.svg files, diagrams-as-code, or the nifdi tools. Covers the block model, containment versus attachment, the placement grammar for labels and badges, the semantic style vocabulary, connectors and their labels, and the render-and-fix loop that keeps what you build looking like what you meant.
license: Apache-2.0
metadata:
  nifdi-mcp-version: "0.3.0"
---

# Building diagrams with nifdi

nifdi is a **structured** diagram editor: containers, text and icons, wired by paths.
Reach for it when the picture is boxes and arrows. It is not a vector canvas — the server
owns layout, and completes and repairs geometry rather than honouring pixel-exact
composition. Fighting that is the single most expensive mistake available here.

## The model in one screen

A diagram is a tree of **blocks** plus **paths** that wire them.

- **container** — a box that holds other blocks. Nesting is containment: a `<container>`
  holds its children directly, and there is no nested `<canvas>`.
- **text** — words.
- **icon** — artwork, referenced by `asset="library:name"` (find one with `search_icons`)
  or `asset="#asset-…"` for artwork already in the diagram.
- **path** — a connector between two blocks, wired through `<from>` and `<to>`.

Blocks carry `pos="x y"` and `size="w h"`, **both optional**. Omitted geometry is completed
by the server; a declared `pos` arranges blocks *against one another* rather than fixing
canvas coordinates. Style is a `<style>` block of `selector { property: value; }` rules with
nifdi's own semantic property names — not CSS.

## Keep the diagram id

There is no current diagram. `create_diagram` returns the id every diagram-scoped tool needs;
for an existing diagram, get that id from `list_diagrams`. Keep it and pass it as `diagramId`
on every call that reads, edits, preflights or renders that diagram. A pasted editor URL is also
accepted wherever `diagramId` is taken.

What an id looks like, and what it means, depends on where the server keeps diagrams. Read one
of these before your first `create_diagram`:

| The tools come from | Diagrams are | Read |
|---|---|---|
| the server named `nifdi`, at `https://nifdi.app/api/mcp` | in the nifdi cloud; ids are short codes such as `Kq3vR8xTn2Wd` | [references/cloud.md](references/cloud.md) |
| the server named `nifdi-diagram`, run by `npx @nifdi/mcp` | `.nifdi.svg` files in the project; ids are paths such as `design/system.nifdi.svg` | [references/local-workspace.md](references/local-workspace.md) |

If both servers are connected, a diagram that belongs in the repository is local, and one the
person shares or edits in the browser is cloud. Never copy a diagram from one to the other unless
asked.

```xml tool=insert
<container id="vpc" size="400 240"><text place="on top-edge">Production VPC</text>
  <icon id="api" asset="aws:amazon-ec2"><text>API server</text></icon></container>
```

That fragment shows the two relationships that matter, and they are **different**:

- `<icon>` is **inside** the container — containment. It lives in the box.
- `<text place="on top-edge">` is **attached** to the container — it is the box's title,
  riding its border, and it travels with the box.

## The one rule to internalise: attach labels, never place them beside

Text sitting beside, above or below an icon in the picture you are recreating **is that
icon's label**. A name across a container's top border **is that container's attached
child**. Author both as nested elements naming a `place` — never as a sib

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 7 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
Apache-2.0
Package author
Nifdi Systems Limited
Keywords
See keywords
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Write

Package observed Nov 17, 2026.

Technical details
First seen
Nov 17, 2026 · 00:00 UTC
Last seen
Nov 17, 2026 · 12:00 UTC
Collection status
Collected

plugin_asdk_app_6ae72d9926148191be288bf70fbcf8ee

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.