<div align="center">

FLUJO

Build AI workflows visually. Run them your way.

Turn your models and MCP tools into AI workflows you can chat with, automate, and call from other apps.

FLUJO is open-source and local-first: connect models, tools, and reusable subflows with drag and drop; debug every step in chat; trigger runs on schedules or events; and serve flows through OpenAI-compatible and MCP endpoints — while your keys and data stay under your control.

Visual flows · MCP-native · Multi-model · Built-in debugger · Automation

Visit flujo.com.co → · Watch the 2:28 product film → · Install FLUJO ↓ · Explore features ↓ · Try FLUJO online →

</div>

<p align="center"><em>Click the preview to see FLUJO in motion.</em></p>

⚡ Quick Install (recommended)

The installer sets up everything FLUJO needs (Git, Node.js, Python, uv), clones FLUJO, builds it, and creates a global flujo command. This is the recommended way to run FLUJO — MCP servers get all their runtimes too.

Windows installer (recommended) — click below to download the latest flujo-setup.exe:

Windows PowerShell — alternatively, press Start, type powershell, press Enter, copy & paste the command below and press Enter again:

irm https://raw.githubusercontent.com/mario-andreschak/FLUJO/main/scripts/install.ps1 | iex

Linux / macOS — paste into a terminal:

curl -fsSL https://raw.githubusercontent.com/mario-andreschak/FLUJO/main/scripts/install.sh | bash

Already have Node.js? You can also skip installation entirely and run a prebuilt FLUJO straight from npm — fastest start, but MCP servers may still need git / python / uv on your PATH (see Run via npx):

npx flujo-ai

Prefer to set it up manually? See Getting Started. To remove FLUJO later, see Uninstalling.

[!TIP] Stuck on MCP installation, the app, or anything else? Open a GitHub issue or join the Discord. I read every message and will do my best to get back to you within a day.

FLUJO is powered by the PocketFlow Framework and built with Cline, Claude Code, and a lot of love.

🌟 Key Features

🔑 Secure Environment & API Key Management

• Encrypted at rest: API keys and other secrets are encrypted in local storage, with an optional custom encryption password for extra protection
• Never sent to the browser: secrets stay server-side — the frontend only ever sees a masked placeholder, even in your own DevTools
• Global variables, bound anywhere: define a key once (e.g. openrouter_key) and bind it into any model or MCP server config instead of pasting it repeatedly
• Backup & restore your encrypted store from the Settings page

🤖 Model Management

• Multiple providers: OpenAI, Anthropic (native or OpenAI-compatible), Google Gemini, X.ai (Grok), OpenRouter, and local models via Ollama
• Claude Subscription: use your Claude Pro/Max plan directly (via the Claude Agent SDK) instead of a metered API key
• Per-model system prompts and tunable parameters, reused across any flow

🔌 MCP Server Integration

• Install from anywhere: the Marketplace tab searches the official MCP Registry and installs with one click; Spotlight curates servers verified to work well with FLUJO; or install manually from a GitHub repo / local folder
• Full MCP capability support: tools, resources, prompts, roots (workspace folders), and sampling (let a server borrow one of your models under a trust policy you control)
• Tool inspection & testing: browse and call a server's tools, resources, and prompts straight from its detail view
• FLUJO as an MCP proxy: re-expose any server you've configured in FLUJO to other MCP clients (Claude Desktop, Cursor, Cline, …) over Streamable HTTP — configure a server once, use it everywhere

Configuring a server is a guided, three-step form (define it → install & build → define how to run it) with a one-click connection test before you save:

Every connected server gets a detail view to browse and test its tools, resources, and prompts directly:

🔄 Visual Flow Builder

• Drag-and-drop orchestration: connect Start, Process (LLM), MCP, Subflow, and Finish nodes into a graph
• Branching & handoff: let a model hand off to another node/agent based on the conversation, build loops, or fan out into multiple specialists
• Subflows: call another flow as a single step, with its own isolated state — reuse a flow like a function
• Per-node tool & prompt scoping: decide exactly which tools, resources, and system-prompt fragments each node can see

Branching & handoff

Connect one node to several successors, then tell the model when to use each handoff tool from the "Agent Tools" tab of its Process Node:

Loops

Connect a node back to a previous one the same way to build a loop:

Orchestration & Subflows

Combine multiple handoffs and loops to build an orchestrator, or drop in a Subflow node to run another flow as a single, reusable step with its own isolated state:

💬 Chat Interface

• Live execution view: watch a run progress node-by-node in real time, with token usage and a context-window meter per conversation
• Visual debugger: set breakpoints, step through a run node-by-node, and inspect state before/after each step
• Human-in-the-loop tool approval: optionally require approval before any tool call executes, for any provider (including Claude Subscription's agentic tool use)
• File & audio attachments, message editing, and conversation branching

Step through a run node-by-node with the visual debugger, inspecting prep/exec state at every stop:

⏱️ Automation — Triggers

Run your flows automatically — on a schedule or when something happens — without opening the chat. FLUJO just needs to be running for triggers to fire.

• Schedule: cron-style recurring runs (with second-level precision and catch-up for missed runs)
• Webhook: trigger a flow via an authenticated HTTP call
• File watch: fire when files change under a folder
• MCP tool polling: periodically call a tool and fire on change, on new items, or let a model/checker-flow decide
• URL watch: fire when a fetched page's content changes

Run history is kept per trigger, with the full output of every run one click away:

As an example, a "watch a tool" trigger polling a WhatsApp MCP server can turn FLUJO into an autonomous auto-responder:

🔄 External Tool Integration

• OpenAI-compatible endpoint: point Cline, Roo Code, Cursor, or any OpenAI-SDK client at http://localhost:4200/v1, use any API key value, and pick a model named flow-<your-flow-name>
• FLUJO as an MCP server (proxy): point an external MCP client at http://localhost:4200/mcp-proxy/<server-name> to reuse a server you configured once in FLUJO (localhost-only in the current version)

Note: FLUJO does not expose an Ollama-compatible server endpoint — use the OpenAI-compatible provider above to consume flows from other apps. (Connecting FLUJO to a local Ollama instance as a model provider is a separate, supported feature.)

📖 Built-in API Documentation

A searchable /docs page inside the app documents every REST endpoint FLUJO exposes (chat, conversations, models, flows, MCP, planned executions, env/encryption, backups) — useful when integrating FLUJO into your own tooling.

🚀 Getting Started

Manual installation:

Prerequisites

• Node.js (v18 or higher)
• claude code (optional, if you want to use Anthropic Subscription)
• python (optional, if you want to use python-based MCP servers)
• pip (optional, if you wa