Freeflowchart

io.github.northwindappsPublished by GitHub account northwindappsv0.1.1Updated Nov 8, 2026

Render text-based flowcharts (FlowScript) to PNG/PDF with layout feedback, offline.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Renders text-based FlowScript flowcharts to PNG or PDF offline, returning the image and node layout data so an assistant can check the result.

What you can do
  • Render a FlowScript flowchart to PNG or PDF
  • Return PNG output as an image for visual checking, or save either format to a file via output_path
  • Return a JSON layout listing every node with its box coordinates and size in CSS pixels from the image top-left
When to use it
Useful when an assistant needs to turn a text-described flowchart into a viewable diagram, or when you want diagram output plus machine-readable node positions for layout checks, without network access.
Requirements
Runs as a local stdio process installed from the npm package freeflowchart, so a Node.js runtime is needed. No authentication, environment variables or headers are declared.
Before you install
Rendering with output_path writes files to disk at the path given, so point it at a location you intend to use. No credentials, payments or third-party data transfer are indicated.

Installation

In SourceWeft

  1. Open Freeflowchart in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

1

render_flowchart

Render flowchart

Render a FlowScript flowchart to PNG or PDF. PNG output is returned as an image so you can check the result; PDF is saved to a file. Pass output_path to save either format to disk. The result also includes a JSON layout: every node with its box (x, y, width, height in CSS px from the image top-left; multiply by scale for image pixels), the script line it came from, the edges, and detected issues ("overlap", "edge_crosses_node") with the script lines involved. Use the issues to revise the script and render again. # FlowScript language reference FlowScript is a line-based text format that renders to a left-to-right flowchart. ## Rules - **One statement per line.** Indentation and blank lines are ignored; indent only for readability. - A line is either a **keyword line** or a **process line** (any other text becomes a box). - Keywords are lowercase and must be the **first word** on the line. - **Gotcha:** a process label must not start with a keyword word. `none of the above` is read as the `none` keyword followed by a box labelled `of the above`. Reword it (`No match`) or capitalize it (`None of the above`), since keywords are case-sensitive. - Every `if`/`if2` needs a `then … endthen` block and a closing `endif`. `if` may also have one `else … endelse` block between `endthen` and `endif`. ## Keywords | Line | Renders | |---|---| | `<text>` | Process box labelled `<text>` | | `<text> (<url>)` | Process box with `<url>` shown in its footer | | `<text> <- file(<name>)` | Process box with a document node `<name>` above it, connected down to it | | `if <question>` | Decision diamond. Use with `then`/`endthen`, optional `else`/`endelse`, then `endif` | | `if2 <question>` | Decision diamond with no `else`; the "no" path continues to the next node after `endif` | | `then` / `endthen` | Start / end the "yes" branch (drawn downward) | | `else` / `endelse` | Start / end the "no" branch | | `endif` | Close the if block; the flow continues to the right | | `endflow`

Parametersscaleformatscriptrequiredoutput_pathinclude_layout

Version history

1
  1. v0.1.1LatestNov 8, 2026

Score

65% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.