Getting Started

Release Notes

What actually shipped, across the three things you might have installed: the platform itself, the fimaflow CLI, and the MCP server.

The web platform deploys continuously, so it's tracked here by date rather than a version number. The CLI is a real npm package and follows semantic versioning; the MCP server is a capability of the platform (no separate install), tracked here by date like the platform itself.

Fimaflow CLI

September 18, 2026

v0.1.0 — initial public release

  • • Published to npm and pnpm (npm install -g fimaflow), and as a standalone binary for macOS, Linux and Windows — no Bun/Node required for the binary install.
  • • fimaflow login — browser-based authorization (same flow as gh auth login), or --token for CI.
  • • Workflows: list/run/logs --follow with a live progress bar, export to any supported framework.
  • • Projects, workspaces and templates: full list/create/import/publish coverage.
  • • fimaflow tui — a full-screen interactive dashboard.
bash
❯ npm install -g fimaflow
❯ fimaflow login

Full reference: CLI docs.

MCP Server

Lets an AI assistant (Claude, Cursor, etc.) inspect — and, where you allow it, run — your workflows directly. Live at mcp.fimaflow.com, no separate install.

September 12, 2026

run_workflow & get_execution_logs

  • • run_workflow — the first tool with a real side effect: trigger an execution from a connected assistant, gated behind an explicit "Allow this connection to run workflows" permission you grant per connection.
  • • get_execution_logs — the node-by-node trace of a run, including the exact error on a failing node, so an assistant can actually debug what it just ran.

September 11, 2026

Initial release — 5 read-only tools

  • • list_workflows, get_workflow, list_executions, analyze_workflow, about_fimaflow.
  • • Every connection is scoped to a single project or workspace — never your whole account — and revoking it takes effect on the next request.

Full reference: MCP Server docs.

Platform

September 16, 2026

Security audit

  • • Platform-wide review across all services — fixes verified live in production, not just merged (credential rotation, request hardening, upload validation).

September 12, 2026

Builder reliability

  • • Database tab: delete, insert and the SQL console are reliable again, and column/table management (rename, duplicate, delete, export) is new.
  • • Manual "Run" now resolves environment variables correctly instead of executing with blank secrets.
  • • A node run with required configuration left empty shows a warning instead of a misleading green "success" — across roughly 35 node types.

September 11, 2026

Node catalog

  • • Every node's configuration is now validated against a real schema — 85 node types.

September 6–18, 2026

Documentation accuracy pass

  • • Removed instructions and screenshots for a desktop app and installer that haven't shipped yet, rather than leave them live and misleading.
  • • CLI and MCP docs rewritten to match what's actually built and verified in production.

What's next

Things actively planned, not a wishlist:

  • • MCP: patch_workflow — letting a connected assistant propose an edit to a workflow, not just inspect and run it. The largest piece of the MCP roadmap; still early.
  • • CLI: GitHub publish/restore from the terminal, and a fully local execution mode.
  • • Platform: continued translation coverage across the builder, and ongoing security hardening.

Feedback

Found a bug, or have an idea? Reach the Fimaflow team directly — real reports shape what gets built next.

Next steps

CLI

Install fimaflow and see the full command reference.

MCP Server

Connect an AI assistant to your projects.

Framework Export

Learn about supported backend frameworks.

    Release Notes — Fimaflow | Fimaflow