FLUJO is still an early preview!

Install everything (Git, Node.js, Python, uv), clone FLUJO, build it, and optionally start it with a single PowerShell command:

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

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

For anything that you struggle with (MCP Installation, Application Issues, Usability Issues, Feedback): PLEASE LET ME KNOW! -> Create a Github Issue or write on Discord (https://discord.gg/KPyrjTSSat) and I will look into it! Maybe a response will take a day, but I will try to get back to each and every one of you.

FLUJO animated Short #1 - "A sad song about MCP"

FLUJO is an open-source platform that bridges the gap between workflow orchestration, Model-Context-Protocol (MCP), and AI tool integration. It provides a unified interface for managing AI models, MCP servers, and complex workflows - all locally and open-source.

FLUJO is powered by the PocketFlowFramework and built with CLine and a lot of LOVE.

• Secure Storage: Store environment variables and API keys with encryption
• Global Access: Use your stored keys across the entire application
• Centralized Management: Keep all your credentials in one secure place

• Multiple Models: Configure and use different AI models simultaneously
• Pre-defined Prompts: Create custom system instructions for each model
• Provider Flexibility: Connect to various API providers (OpenAI, Anthropic, etc.)
• Local Models: Integrate with Ollama for local model execution

• Easy Installation: Install MCP servers from GitHub or local filesystem
• Server Management: Comprehensive interface for managing MCP servers
• Tool Inspection: View and manage available tools from MCP servers
• Environment Binding: Connect server environment variables to global storage

• Visual Flow Builder: Create and design complex workflows
• Model Integration: Connect different models in your workflow
• Tool Management: Allow or restrict specific tools for each model
• Prompt Design: Configure system prompts at multiple levels (Model, Flow, Node)

• Flow Interaction: Interact with your flows through a chat interface
• Message Management: Edit or disable messages or split conversations to reduce context size
• File Attachments: Attach documents or audio for LLM processing (really bad atm, because for this you should use mcp!)
• Transcription: Process audio inputs with automatic transcription (really bad atm, see roadmap)

• OpenAI Compatible Endpoint: Integrate with tools like Cline or Roo Code. In the client, choose the OpenAI Compatible provider, set the Base URL to http://localhost:4200/v1 (note: /v1, not /v1/models), put any value as the API key, and pick a model named flow-<your-flow-name> (the list comes from /v1/models).
• FLUJO as an MCP server (proxy): Re-expose any configured MCP server to external MCP clients (Claude Desktop, Cursor, Cline, …) so you set a server up once in FLUJO and use it everywhere. Toggle "Expose to external apps" on the server's card, then add a Streamable-HTTP MCP server in your client pointing at http://localhost:4200/mcp-proxy/<server-name>. (Localhost-only in the current version.)
• Seamless Connection: Use FLUJO as a backend for other AI applications

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

• Node.js (v18 or higher)
• npm or yarn

1. Clone the repository:

   git clone https://github.com/mario-andreschak/FLUJO.git
   cd FLUJO

2. Install dependencies:

   npm install
   # or
   yarn install

3. Start the development server:

   npm run dev
   # or
   yarn dev

4. Open your browser and navigate to:

   http://localhost:4200
   

5. FLUJO feels and works best if you run it compiled:

   npm run build
   npm start

On a fresh Windows machine you can install everything (Git, Node.js, Python, uv), clone FLUJO, build it, and optionally start it with a single PowerShell command:

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

By default FLUJO is installed into %LOCALAPPDATA%\FLUJO. To customise the install without the interactive prompt, set environment variables first, e.g.:

$env:FLUJO_DIR = "D:\Apps\FLUJO"; $env:FLUJO_START = "1"; irm https://raw.githubusercontent.com/mario-andreschak/FLUJO/main/scripts/install.ps1 | iex

See scripts/install.ps1 for all options.

To remove FLUJO, run the uninstaller:

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

or, from inside your install folder:

powershell -ExecutionPolicy Bypass -File scripts\uninstall.ps1

It asks, per prerequisite (Git, Node.js, Python, uv), whether to remove it — defaulting to yes for ones FLUJO installed and no for ones that were already on your system — then removes the flujo command and the FLUJO folder.

⚠️ This permanently deletes your data. All flows, encrypted API keys, MCP server configs and chat history live in <install>\db\ and are removed with the folder. Use FLUJO's built-in backup/export first if you want to keep them.

Installs created before this feature have no manifest; the uninstaller then defaults every prerequisite to keep (it can't tell which FLUJO installed). Re-running the installer once writes the manifest for future uninstalls. See scripts/uninstall.ps1 for details.

1. Navigate to Settings
2. Save your API Keys globally to secure them

1. Navigate to the Models page
2. Click "Add Model" to create a new model configuration
3. Configure your model with name, provider, API key, and system prompt
4. Save your configuration

1. Go to the MCP page
2. Click "Add Server" to install a new MCP server
3. Choose from GitHub repository or local filesystem
4. Configure server settings and environment variables
5. Start and manage your server

1. Got to the MCP Page
2. Click "Add Server" to install a new MCP server
3. Select "Local Server"
4. Enter a Server Name, enter "/" as Server Root Path
5. Leave Build Command and Install Command empty
6. Enter "npx" as Run Command
7. Add 1. Argument "mcp-remote"
8. Add 2. Argument "(your MCP SSE-Url here)"

1. Go to the MCP page
2. Click "Add Server" to install a new MCP server
3. Go to the "Reference Servers" Tab
4. (First time executing:) Click "Refresh" and waaaaaaait.
5. Click a server of your choice, wait for the screen to change, click "Save" / "Update Server" at the bottom.

1. Visit the Flows page
2. Click "Create Flow" to start a new workflow
3. Add processing nodes and connect them
4. Configure each node with models and tools
5. Save your flow

1. Connect one MCP node to multiple subsequent ones
2. Define the branching in the prompt, using the handoff-tools on the "Agent Tools" tab

1. Same as branching, but connect back to a previous node

1. Same as loops but with multiple ones

1. Go to the Chat page
2. Select a flow to interact with
3. Start chatting with your configured workflow

FLUJO provides comprehensive support for the Model Context Protocol (MCP), allowing you to:

• Install and manage MCP servers
• Inspect server tools
• Connect MCP servers to your workflows
• Reference tools directly in prompts
• Bind environment variables to your global encrypted storage

FLUJO is licensed under the MIT License.

Here's a roadmap of upcoming features and improvements:

• Real-time Voice Feature: Adding support for Whisper.js or OpenWhisper to enable real-time voice capabilities.
• Visual Debugger: Introducing a visual tool to help debug and troubleshoot more effectively.
• MCP Roots Support: Implementing Checkpoints and Restore features within MCP Roots for better control and recovery options.
• MCP Prompts: Enabling users to build custom prompts that fully leverage the capabilities of the MCP server.
• MCP Proxying STDIO<>SSE: Likely utilizing SuperGateway to proxy standard input/output with Server-Sent Events for enhanced communication: Use MCP Servers managed in FLUJo in any other MCP client.
• Enhanced Integrations: Improving compatibility and functionality with tools like Windsurf, Cursor, and Cline.
• Advanced Orchestration: Adding agent-driven orchestration, batch processing, and incorporating features inspired by Pocketflow.
• Online Template Repository: Creating a platform for sharing models, flows, or complete "packages," making it easy to distribute FLUJO flows to others.
• Edge Device Optimization: Enhancing performance and usability for edge devices.

Contributions are welcome! Feel free to open issues or submit pull requests.

1. Fork the repository
2. Create your feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add some amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

• GitHub: mario-andreschak
• LinkedIn: https://www.linkedin.com/in/mario-andreschak-674033299/

• You can add ~FLUJO=HTML, ~FLUJO=MARKDOWN, ~FLUJO=JSON, ~FLUJO=TEXT in your message to format the response, this will give varying results in different tools where you integrate FLUJO.
• You can add ~FLUJOEXPAND=1 or ~FLUJODEBUG=1 somewhere in your message to show more details
• in config/features.ts you can change the Logging-level for the whole application
• in config/features.ts you can enable SSE support which is currently disabled by default

FLUJO - Empowering your AI workflows with open-source orchestration.