Fork differences
Agentic Mermaid adds styled rendering, typed editing, deterministic verification, CLI, MCP, and more families.
Agentic Mermaid (agentic-mermaid) forks beautiful-mermaid for a job the render-only original did not have: agents creating polished, branded diagrams that stay editable as Mermaid source.
- Typed agent surface. A render-only library forces an agent to regenerate a whole diagram to change one node. Here new diagrams are authored as source then parsed/verified/rendered, and existing diagrams go parse → narrow → mutate → verify → serialize via
agentic-mermaid/agent. Every registered built-in family is structured when narrowed; unmodeled syntax still round-trips losslessly as opaque fallback. - Deterministic, verifiable layout. Layout is byte-identical across processes, and
verifyMermaidreturns structured warnings in three tiers (structural, geometric, lint) plus perceptual quality metrics. - More families. Adds Timeline, Journey, Architecture, Pie, Quadrant, Gantt, Mindmap, GitGraph, Radar beyond the original Beautiful Mermaid family set; that list is generated from the same descriptor projection that drives examples and capabilities.
- Tools. An
amCLI, anagentic-mermaid-mcpCode Mode MCP server (stdio + opt-in HTTP/SSE), and a hosted MCP endpoint at/mcp. There is no REST render API. - Style + Palette rendering. Named looks and palette stacks keep appearance outside Mermaid source while preserving deterministic geometry.
See examples for the generated family list and rendered source, and About for the lineage.