Vaults Diagram Tools MCP Server

Render Mermaid and source-code diagrams via MCP.

Local serverstdio

What is the Vaults Diagram Tools MCP server?

Render Mermaid and source-code diagrams via MCP. Exposed over MCP by the vaults diagram tools mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

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.

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

Its toolset

Everything the assistant can do here goes through one of these:

  • render_mermaid_text — render_mermaid_file
  • LinksMermaid source / SVG /
  • 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

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at vaults-mermaid-render on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Vaults Diagram Tools's toolset — render_mermaid_text, Links, vaults-mermaid-render and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Malnati; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Vaults Diagram Tools's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the vaults diagram tools mcp server does with a few real requests.

Available tools

ToolWhat it does
render_mermaid_textrender_mermaid_file
Links[Mermaid source](docs/assets/diagrams/install-usage-flow.mmd) / [SVG](docs/assets/diagrams/install-usage-flow.svg) / [JPEG](docs/assets/diagrams/install-usage-flow.jpg)
vaults-mermaid-renderRender .mmd or .mermaid files to SVG/JPEG, manifests, and optional PNG/text sidecars.
vaults-source-diagramsGenerate Mermaid diagrams from source-code structure, including focused selections and traceability metadata.
vaults-diagram-mcpExpose render_mermaid_text, render_mermaid_file, and generate_source_diagrams through MCP stdio.

How to install the Vaults Diagram Tools MCP server

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

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Vaults Diagram Tools to render mermaid text.
  • Use Vaults Diagram Tools to Links.
  • Use Vaults Diagram Tools to vaults-mermaid-render.

Frequently asked questions

It connects Vaults Diagram Tools to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (render_mermaid_text, Links, vaults-mermaid-render, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Vaults Diagram Tools directly.