Vaults Diagram Tools

Name: Vaults Diagram Tools
Author: Malnati

by Malnativersion 0.1.4i★ –iRuns on your computer

Registry nameio.github.Malnati/vaults-diagram-tools

Install

Overview

Description from the maker (original English)

Mermaid to assets. Source code to maps. MCP for agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Design, images & audio

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "vaults-diagram-tools": {
      "command": "npx",
      "args": [
        "-y",
        "vaults-diagram-tools"
      ]
    }
  }
}

Run this in your terminal

claude mcp add vaults-diagram-tools -- npx -y vaults-diagram-tools

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "vaults-diagram-tools": {
      "command": "npx",
      "args": [
        "-y",
        "vaults-diagram-tools"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "vaults-diagram-tools": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "vaults-diagram-tools"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Malnati, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Design, images & audioi

More stars than 0% of the other 2754 servers in this category
Published to the registry more recently than 7% of the other 2754 servers in this category
Basic checks equal to or better than 100% of the other 2754 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Vaults Diagram Tools safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.4) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Figma Context MCP

by GLips

Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.

Runs on your computer★ 16,165MITUpdated 5 months ago

Install

Claude Real Video

by HUANGCHIHHUNGLeo

Let any LLM watch a video locally — and search everything it has ever watched.

Runs on your computer★ 2,284MITUpdated 2 months ago

Install

Figma MCP Server

by figma

Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.

Runs in the cloud★ 2,152Updated 13 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

vaults-diagram-tools

Mermaid to assets. Source code to maps. MCP for agents.

vaults-diagram-tools is a standalone toolkit for teams that need reproducible Mermaid SVG/JPEG assets, source-code diagrams, and agent-friendly diagram workflows without carrying Vault-specific content.

What is included

Mermaid renderer extracted from the Vaults toolchain.
Source-code to Mermaid diagram generator.
MCP stdio server with three explicit tools, published in MCP Registry as io.github.Malnati/vaults-diagram-tools.
Offline-capable release assets for zip and container distribution.
Dedicated GitHub Actions Marketplace wrapper repository for render/source/policy automation.
Packaging templates for Homebrew, deb/rpm, CDN, Docker, and Podman, plus a publishable VS Code extension package.

Content-management workflows outside diagram generation are not part of this package.

Quick start

Install in a project:

npm install -D vaults-diagram-tools

Render one Mermaid source to durable assets:

npx vaults-mermaid-render path/to/diagram.mmd --output-dir out --manifest out/manifest.json

Generate Mermaid diagrams from source code:

npx vaults-source-diagrams --source-dir src --output-dir diagrams

Run the MCP stdio server:

npx vaults-diagram-mcp

Use one-shot npx when the project should not keep a dependency:

npx --yes --package vaults-diagram-tools vaults-mermaid-render path/to/diagram.mmd --output-dir out

npx --yes --package vaults-diagram-tools vaults-source-diagrams --source-dir src --output-dir diagrams npx --yes --package vaults-diagram-tools vaults-diagram-mcp

Core tools

Command	Purpose
`vaults-mermaid-render`	Render `.mmd` or `.mermaid` files to SVG/JPEG, manifests, and optional PNG/text sidecars.
`vaults-source-diagrams`	Generate Mermaid diagrams from source-code structure, including focused selections and traceability metadata.
`vaults-diagram-mcp`	Expose `render_mermaid_text`, `render_mermaid_file`, and `generate_source_diagrams` through MCP stdio.

Additional package binaries are compatibility entrypoints for older Vaults paths, optional text renderers, and Podman workflows.

Workflows

Markdown docs: keep the Mermaid source as a linked .mmd, render .svg and .jpg, and show source inline with a fenced mermaid block.
Source graph reviews: generate diagrams from real source paths and inspect manifest selection data for requested files, omitted connectors, and rendered outputs.
Agent automation: use the MCP server when clients need diagram rendering through a narrow, explicit tool surface. Current registry entry is active at version 0.1.4, and the Smithery server page is already published.
Release packaging: ship npm, zip, container, and offline vendor artifacts while preserving license and notice files.

Download and distribution

npm registry

Use the published npm package when you want the normal Node.js toolchain installation. Current npm latest is vaults-diagram-tools@0.1.4:

npm install -D vaults-diagram-tools

npx vaults-mermaid-render path/to/diagram.mmd --output-dir out --manifest out/manifest.json npx vaults-source-diagrams --source-dir src --output-dir diagrams npx vaults-diagram-mcp

One-shot with `npx`

Use --package when the project should not keep the dependency:

npx --yes --package vaults-diagram-tools vaults-mermaid-render path/to/diagram.mmd --output-dir out

npx --yes --package vaults-diagram-tools vaults-source-diagrams --source-dir src --output-dir diagrams npx --yes --package vaults-diagram-tools vaults-diagram-mcp

GitHub Actions Marketplace

Use the dedicated Marketplace action when the diagram workflow should run inside GitHub Actions without adding project-local scripts:

steps:

uses: actions/checkout@v4
name: Render Mermaid assets id: diagrams uses: Malnati/vaults-diagram-tools-action@v0 with: mode: render input: docs/diagrams output-dir: diagram-assets
name: Upload diagram assets uses: actions/upload-artifact@v4 with: name: diagram-assets path: ${{ steps.diagrams.outputs.output-dir }}

GitHub Actions Marketplace listing
Action repository
Initial action release: v0.1.4; moving compatibility tag: v0.

npm package from GitHub

Use the GitHub package source when testing a commit before a registry release:

npm install github:malnati/vaults-diagram-tools

npx vaults-mermaid-render path/to/diagram.mmd --output-dir out

GitHub release assets

The latest GitHub Release, GHCR image, npm package, MCP Registry metadata, and VS Code VSIX are published at v0.1.4; the Quay.io Podman image remains at v0.1.0:

vaults-diagram-tools-0.1.4.tgz
vaults-diagram-tools-0.1.4.zip
vaults-diagram-tools-vscode-0.1.4.vsix
ghcr.io/malnati/vaults-diagram-tools:v0.1.4
quay.io/ricardomalnati/vaults-diagram-tools:v0.1.0

Local checkout

Use the checkout for development, validation, or release preparation:

git clone https://github.com/malnati/vaults-diagram-tools.git

cd vaults-diagram-tools npm ci npm test node packages/renderer/render-mermaid-assets.mjs examples/simple/flowchart.mmd --output-dir tmp/rendered node packages/source-diagrams/source-diagrams.mjs --source-dir packages/mcp --output-dir tmp/source-diagrams node packages/mcp/server.mjs

Container, Docker, and Podman

Build locally:

docker build -f containers/Containerfile -t vaults-diagram-tools:local .

podman build -f containers/Containerfile -t vaults-diagram-tools:local .

Run a render from the GHCR image:

docker run --rm \

-v "$PWD/examples/simple:/work/input:ro" \ -v "$PWD/tmp/container-output:/work/output:rw" \ ghcr.io/malnati/vaults-diagram-tools:v0.1.4 \ --output-dir /work/output /work/input/flowchart.mmd

Run the published Podman image from Quay.io:

podman run --rm \

-v "$PWD/examples/simple:/work/input:ro" \ -v "$PWD/tmp/container-output:/work/output:rw" \ quay.io/ricardomalnati/vaults-diagram-tools:v0.1.0 \ --output-dir /work/output /work/input/flowchart.mmd

Quay.io also exposes 0.1.0 and latest tags for the same published package line.

Podman helper scripts are available through vaults-mermaid-podman-build, vaults-mermaid-podman-render, and vaults-mermaid-podman-test.

CDN facade

The package is CLI-first. CDN endpoints expose browser-safe metadata/helpers only; SVG/JPEG rendering still runs through Node.js, MCP, or the container runtime.

https://cdn.jsdelivr.net/npm/vaults-diagram-tools/packaging/cdn/vaults-diagram-tools.mjs

https://unpkg.com/vaults-diagram-tools/packaging/cdn/vaults-diagram-tools.mjs

VS Code extension

The desktop VS Code extension is published as malnati.vaults-diagram-tools and can also be installed directly from the GitHub Release VSIX. It uses a hybrid runtime: a bundled offline fallback plus a managed cache that can follow vaults-diagram-tools@latest without republishing the extension. It contributes:

Command Palette actions for Mermaid SVG/JPEG rendering, source-diagram generation, and Markdown diagram-policy validation.
Runtime commands: update managed runtime now, show runtime status, and force the bundled runtime.
A native VS Code MCP server definition provider for the resolved vaults-diagram-tools stdio server.
Marketplace/Open VSX publish scripts for manual publication from an authenticated local shell. Keep npm, VS Code Marketplace, and Open VSX credentials in the local terminal; GitHub Actions does not use those secrets.

Install options after v0.1.4 is released:

Local package validation:

npm run vscode:install

npm run vscode:test npm run vscode:package code --install-extension dist/vaults-diagram-tools-vscode-0.1.4.vsix

Sequential local publication:

make auth

make publish-all

make publish-all runs local-terminal authentication first, validates guard-only release metadata, packages artifacts, creates the GitHub tag/release, publishes npm, VS Code Marketplace, Open VSX, GHCR, Quay.io, and MCP Registry, then verifies public availability. It fails when the current version/tag/npm package already exists; bump and commit release metadata before running.

Command line usage

After installing from npm, run public CLIs directly from node_modules/.bin, npm exec, or npx:

vaults-mermaid-render path/to/diagram.mmd --output-dir out --png --ascii --manifest out/manifest.json

vaults-source-diagrams --source-dir src --output-dir diagrams --langs auto --diagrams dependency,class vaults-diagram-mcp

One-shot examples:

npx --yes --package vaults-diagram-tools vaults-mermaid-render examples/simple/flowchart.mmd --output-dir tmp/vaults-diagram-tools

npx --yes --package vaults-diagram-tools vaults-source-diagrams --source-dir packages/mcp --output-dir tmp/source-di

Only the beginning is shown; read the rest in the repo

Vaults Diagram Tools

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Design, images & audioi

Common questions

Alternatives

Figma Context MCP

Claude Real Video

Figma MCP Server

README from the maker

vaults-diagram-tools

What is included

Quick start

Core tools

Workflows

Download and distribution

npm registry

One-shot with npx

GitHub Actions Marketplace

npm package from GitHub

GitHub release assets

Local checkout

Container, Docker, and Podman

CDN facade

VS Code extension

Command line usage

One-shot with `npx`