Fluxygram
OfficialThis server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
<script type="module" src="https://cdn.jsdelivr.net/npm/fluxygram@0.3"></script>
<fluxy-gram src="order.flux.json"></fluxy-gram>{
"type": "flow",
"title": "How an order gets processed",
"nodes": [
{ "id": "start", "label": "Order received", "kind": "start", "icon": "cart" },
{ "id": "stock", "label": "In stock?", "kind": "decision" },
{ "id": "pay", "label": "Charge", "icon": "card" },
{ "id": "done", "label": "Delivered", "kind": "end", "accent": true }
],
"edges": [
{ "from": "start", "to": "stock" },
{ "from": "stock", "to": "pay", "label": "yes" },
{ "from": "pay", "to": "done" }
]
}That's a complete diagram. With no steps, it uses the default motion of its type; add steps to tell your own story.
Diagram types
Type | Explains | Default motion |
| steps, decisions, pipelines, user journeys | the path builds column by column; a particle runs along each new edge |
| systems, layers, services | layers appear bottom-up, then requests travel between services |
| history, roadmaps, releases | the camera moves from milestone to milestone |
| hierarchies, org charts, categories | grows from the root, level by level |
| loops, feedback, anything that repeats | each stage appears around the ring; at the end it all loops |
| API calls, logins, protocols | participants appear, then each message crosses between lifelines |
| ideas around a topic, plans, syllabi | the central idea first, then one branch at a time |
You can switch a diagram's type at any time without losing its nodes and connections.
Related MCP server: @excalimate/mcp-server
Telling the story
Each step says what changes:
Field | What it does |
| Elements that appear or disappear |
| A particle travels along these connections |
| These nodes stand out, everything else dims |
| The camera moves in on a node or group |
|
|
| The sentence under the diagram |
| Seconds this step stays on screen |
| Speaker notes, only visible to the presenter |
motion sets the style for the whole diagram, or per block and connection: how things enter (fade, scale, draw, slide), how they travel (particle, pulse, dash, packets), the speed, and whether the camera follows the action. At the end, the camera pulls back to show the whole picture.
Full documentation at docs.fluxygram.app: every field, every type with live examples, the component API and guides. Also: SKILL.md (format and storytelling rules) and the JSON Schema.
Editor and presentation mode
fluxygram.app/play is a canvas editor that runs entirely in your browser:
Drag blocks from the palette, drag from a block's dot to connect it, and edit everything in the side panel (or in the JSON tab, with live validation).
Build the story step by step: captions, states, timing and speaker notes.
Open or drop a
.flux.json, download it, share a link (the diagram is compressed into the URL, no server involved) or export a single self-contained HTML file.Present opens the diagram full screen for your audience. Press N for a second window with your notes, the next step and a timer.
Dragging a block pins it (x, y in the JSON); everything else keeps its automatic layout.
Live status (tracker mode)
The same diagram can also show where a real process is right now: an order, a delivery, a support ticket, a job application. Your app sets the current stage; done stages turn green, the current one shows its status, and every change animates.
<fluxy-gram src="order.flux.json" mode="tracker" stage="shipped"></fluxy-gram>tracker.setStage('delivered', 'success'); // status: pending | success | warning | errorFor branches that join or processes that loop back, pass history (the stages it went through). Try the live examples in the gallery and read the tracker guide: connecting it to your data, translations, ideas.
Install
npm install @fluxygram/elementimport '@fluxygram/element'; // registers <fluxy-gram>Package | What it is |
The | |
Format, validation, layout and motion. No DOM | |
Single-file build for | |
| |
Astro and Starlight integration | |
Docusaurus plugin | |
MCP server for AI agents (also hosted at |
Docs sites (Docusaurus, Astro, Starlight, VitePress, Next.js MDX) and Obsidian: see integrations.
The component picks English or Spanish from the page or browser language (the lang attribute wins when set).
For agents
The skill in skills/fluxygram teaches an agent the format, how to pick the diagram type and how to write good steps, plus a recipe for diagramming a whole codebase.
Claude Code
/plugin marketplace add Fluxygram/fluxygram
/plugin install fluxygram@fluxygramCursor, Windsurf, Codex, Copilot and other coding agents: save the skill in your project and point the agent at it.
MCP server (Claude, Cursor, VS Code, Windsurf, any MCP client): connect https://fluxygram.app/mcp, or run npx -y @fluxygram/mcp. The agent can then validate its diagrams and give you a link to watch them. Setup.
curl -o FLUXYGRAM.md https://fluxygram.app/skill.mdChatGPT, Gemini, Claude.ai: the website has a "Copy prompt" button for each one that includes the whole skill; paste the answer in the editor.
Contributing
Questions, ideas and diagrams go to Discussions; bugs and concrete requests to issues. Read CONTRIBUTING.md to set up the project and open a pull request. Contributors sign the CLA once, on their first PR. Security problems: SECURITY.md.
pnpm install
pnpm dev # site, editor and presentation mode on http://localhost:5173
pnpm typecheckPath | What it is |
| Format, validation, layout and motion. No framework, no DOM |
|
|
| Single-file build for CDNs |
| Landing, editor, viewer and presentation mode (Vite), deployed on Cloudflare Workers |
| Documentation at docs.fluxygram.app (Astro Starlight), in English and Spanish |
| Agent skill and examples, also a Claude Code plugin ( |
License
packages/*,skills/fluxygramanddocs: MIT. Use, embed and ship them anywhere.site(landing, editor, presentation mode): FSL-1.1-ALv2. Free to read, modify and self-host for your own use; not to offer as a competing commercial service. Every release becomes Apache 2.0 after two years.
Details in LICENSE.md.
Español
Diagramas que se explican solos. Describes cualquier cosa en un JSON y Fluxygram la dibuja y la cuenta paso a paso, con movimiento que ayuda a entender.
Siete tipos de diagrama:
flow(procesos y decisiones),architecture(sistemas por capas),timeline(historia y roadmaps),tree(jerarquías),cycle(ciclos),sequence(quién le habla a quién, en orden) ymindmap(ideas alrededor de un tema). Cada uno se mueve a su manera, y se puede cambiar de tipo sin perder el contenido.Pasos opcionales: sin ellos, el diagrama usa el movimiento de su tipo. Con ellos decides qué aparece, por dónde viaja la partícula, qué se resalta, a dónde va la cámara, los estados (éxito, error, advertencia, en progreso) en bloques y conexiones, el texto de cada paso y su duración.
Editor visual en fluxygram.app/play: arrastras bloques, los conectas, armas la historia paso a paso y compartes un link, descargas el JSON o exportas un HTML. Todo pasa en tu navegador.
Modo presentación: el diagrama a pantalla completa para tu público y, con la tecla N, una segunda ventana con tus notas, el siguiente paso y un cronómetro.
Estado en vivo (modo seguimiento): el mismo diagrama muestra en qué etapa va un proceso real (un pedido, un domicilio, un ticket, una postulación). Tu aplicación cambia
stagey el diagrama se anima: lo cumplido en verde, la etapa actual con su estado. Pruébalo en la galería y lee la guía.Para agentes: la carpeta
skills/fluxygramle enseña a cualquier agente a escribir diagramas. En Claude Code se instala con/plugin marketplace add Fluxygram/fluxygramy/plugin install fluxygram@fluxygram; para ChatGPT, Gemini o Claude.ai, el sitio tiene un botón "Copiar prompt".Documentación completa en docs.fluxygram.app/es, con ejemplos en vivo de cada tipo.
Paquetes en npm:
@fluxygram/element(el componente),@fluxygram/core(el formato) yfluxygram(un solo archivo para usar desde un CDN).El sitio y el componente se muestran en inglés o español según el idioma del navegador.
Contribuir
Las preguntas e ideas van en Discussions y los errores en issues, en inglés o español. La guía está en CONTRIBUTING.md; en tu primer pull request firmas el CLA una sola vez.
Licencia
packages/*,skills/fluxygramydocs: MIT. Se pueden usar, incrustar y distribuir en cualquier parte.site(landing, editor, modo presentación): FSL-1.1-ALv2. Libre para leer, modificar e instalar para uso propio; no para ofrecerlo como un servicio comercial que compita. Cada versión pasa a Apache 2.0 a los dos años.
Detalles en LICENSE.md.
Available Tools
4 toolsget_exampleGet an example diagramARead-onlyInspect
Returns a complete example diagram to learn from or adapt. Without a name, lists the available examples (recipes, software architecture, OAuth login, order process, timelines, live order trackers and more).
Inputs: lang, name.
get_guideFluxygram format guideARead-onlyInspect
How to write a Fluxygram diagram: the seven diagram types and when to use each, nodes, edges, steps with captions, motion, live status (tracker mode), icons and the storytelling rules. Call it before writing your first diagram.
Inputs: no named parameters.
validate_diagramValidate a diagramARead-onlyInspect
Checks a Fluxygram diagram with the same validator the viewer uses. Returns "valid" with a short summary, or every problem with its path so you can fix it. Always validate before sharing.
Inputs: diagram (required), lang.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct phase of the workflow: learning (get_guide, get_example), validating, and sharing. The only mild overlap is between get_guide and get_example, since both are 'learn the format' helpers, but the descriptions clearly separate syntax rules from concrete examples.
All four tools use a clean snake_case verb_noun pattern (get_*, share_*, validate_*) with predictable get/get/share/validate semantics.
Four tools is on the lean side, but the server's scope is narrow (write, validate, and share a link-embedded diagram) and each tool earns its place. No filler or duplicate tools.
The core lifecycle is covered: learn the format, see an example, validate with the viewer's own validator, and produce a view/editor/present link. Minor gaps exist — no tool to decode or inspect an existing share link, and no export to image/file, but agents can work around both.
Maintenance
Related MCP Connectors
Create and edit architecture diagrams from your AI agent; get an SVG and a live editable canvas.
Turn a flow written as text into a step-through diagram you can share, present or embed.
Create, read and live-edit visual boards, Kanban plans, Gantt timelines and diagrams with AI agents.
Create, edit and organize hand-drawn diagrams (flowcharts, ER, architecture) from any AI agent.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to create visual, interactive interfaces with diagrams, structured input forms, and persistent state management instead of text-only responses.7-
- AlicenseNot gradedqualityAmaintenanceTurn Excalidraw diagrams into keyframe animations. AI-powered creation via MCP, E2E encrypted sharing, export to MP4/WebM/GIF/SVG.6 npm101MIT
- AlicenseNot gradedqualityBmaintenanceLet AI agents create interactive visualizations that render live inside your chat — no code required.3BSD 3-Clause
- AlicenseNot gradedqualityCmaintenanceAgent-driven animated diagram renderer that turns API/flow descriptions into animated MP4s or Instagram-style carousels, designed to be driven by an AI agent over MCP.29 npm5MIT