Skip to main content

Changelog

Recently shipped.

The notable changes we’ve rolled out, newest first. More lands here as we head toward launch.

  1. Developer platform

    MCP server 0.13.0: folders, renames, safer concurrent edits

    The MCP server picks up three tools agents were missing, plus a concurrency guard that turns a silent lost update into a clean, retryable error. 18 tools in total now, hardened by a 37-finding audit fixed in this release.

    • Three new tools: list_folders, create_folder, and rename_diagram, so an agent can organize diagrams the way the CLI and web app already could.
    • An expectedUpdatedAt concurrency guard: pass back the revision token from a read, and a stale edit aborts with a clean 409 instead of silently overwriting someone else's change.
    • Tool annotations, server instructions, and structured output (outputSchema) so MCP clients can show richer previews of what each tool does; a stored login token is now also bound to the origin it was issued for.
    • Published as @excaliwow/mcp@0.13.0 and @excaliwow/cli@0.4.0.

    Read the MCP docs

  2. Icons

    Curated icon library

    Diagrams generated through the DSL, MCP, or CLI can now carry real icons instead of plain boxes — a curated catalog of 26 server-side icons (database, server, cloud, queue, cache, kubernetes, lock, and more) that render as crisp line art.

    • The diagram DSL grew an icon field: set a node's icon to "icon-<name>" and Excaliwow lays out the glyph above the label as one selectable group.
    • MCP's list_icons tool and the CLI's excaliwow icons [--category <c>] command both list the catalog (id, label, category, size) so an agent or script can pick a valid id before using it.
    • Published as @excaliwow/mcp@0.12.0 and @excaliwow/cli@0.3.0.

    Read the DSL reference

  3. Rendering

    Faithful rendering by default

    Renders from the REST API, CLI, and MCP server now default to the same exporter the editor uses on canvas — hand-drawn strokes, real fonts, and embedded images — instead of the old lightweight approximation.

    • A dedicated render service runs the editor's own exporter headlessly, so a diagram you script looks the same as one you export by hand.
    • Any faithful-render failure falls back gracefully to the fast preview — you always get a 200, never a 5xx, with a note flagging the degraded quality.
    • Opt into the previous cheap path explicitly with ?quality=fast on the API or --fidelity fast on the CLI when speed matters more than looks.

    Read the API docs

  4. Collaboration

    Workspaces & members

    Every diagram you make now lives in a workspace you can share as a whole. Invite people by email from Settings → Workspace and they get access to everything at once, instead of one diagram at a time.

    • Invite members as an Editor — who can edit every diagram — or a Viewer, who can open and follow along live.
    • Members find your diagrams in a new Shared view, kept apart from their own library.
    • You stay the owner: deleting, starring, moving, publishing, and folder management remain yours, and members never see your Trash.

    Read the guide

  5. Developer platform

    REST API, CLI & MCP server

    Excaliwow is now scriptable. A public REST API drives the same diagrams you edit in the browser, with first-class command-line and AI-agent clients.

    • @excaliwow/cli and @excaliwow/mcp are published to npm (Apache-2.0).
    • Authenticate with personal access tokens, scoped per capability — read, write, publish, delete.
    • A full set of developer docs covers the API, CLI, MCP server, and diagram DSL.

    Browse the docs