Dgmo MCP Server

Render 29 diagram and chart types to SVG/PNG with browser preview and HTML reports.

Local serverstdio

What is the Dgmo MCP server?

Dgmo MCP server exists for a simple reason — assistants are far more useful when they can act on Dgmo directly instead of describing what you should do. Render 29 diagram and chart types to SVG/PNG with browser preview and HTML reports.

What you get

This MCP server gives Claude (and any MCP-compatible AI tool) the ability to render sequence diagrams, flowcharts, ER diagrams, C4 architecture, gantt charts, and 40+ other chart types from concise text markup — then hand the result off to a full editor for refinement. Ask for a diagram in chat; get a real one back.

What the assistant can call

Once Dgmo is connected, these are the calls the assistant has available:

  • render_diagram — Render DGMO markup to SVG or PNG
  • preview_diagram — Render one or more diagrams and open an HTML preview in the browser
  • generate_report — Build a polished multi-section HTML report with ToC and optional source
  • list_chart_types — List all supported chart types
  • get_language_reference — Get DGMO syntax documentation for accurate generation

Setting it up

@diagrammo/dgmo on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Dgmo's toolset — render_diagram, preview_diagram, generate_report and 2 more — is a fair guide to whether it matches your workflow. It is maintained by diagrammo; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • 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 dgmo mcp server does with a few real requests.

Available tools

ToolWhat it does
render_diagramRender DGMO markup to **SVG or PNG**
preview_diagramRender one or more diagrams and open an **HTML preview** in the browser
generate_reportBuild a polished **multi-section HTML report** with ToC and optional source
list_chart_typesList all supported chart types
get_language_referenceGet DGMO syntax documentation for accurate generation

How to install the Dgmo MCP server

{
  "mcpServers": {
    "dgmo": {
      "command": "npx",
      "args": ["-y", "@diagrammo/dgmo"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Dgmo to render diagram.
  • Use Dgmo to preview diagram.
  • Use Dgmo to generate report.

Frequently asked questions

It connects Dgmo to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (render_diagram, preview_diagram, generate_report, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Dgmo directly.