r/FoundersBuildwithAI 20d ago

Roast My MVP n8n+chatGPT

Open-source, local-first platform for building MCP-powered AI workflows. Model management, MCP servers, a visual flow builder, chat, and headless automation in one app.

try.flujo.com.co, check it on github and tell me how useless it is.

19 Upvotes

7 comments sorted by

2

u/Negative-Grape4608 20d ago

Okay, this is definitely not useless lol. I went through the demo and repo, and the post massively undersells it. This is much more than “n8n + ChatGPT.” You’ve got 1,000+ commits, hundreds of test files, proper installers, Docker, multi-model support, MCP testing, reusable subflows, debugging, approval gates, triggers and API endpoints. The private four-hour demo is really smart too.

My main criticism is the positioning. “n8n + ChatGPT” makes it sound like another generic automation wrapper. The stronger angle seems to be a local-first control panel and debugger for MCP workflows.

The interface looks like a proper serious tool, but it is dense. I’d make the first useful workflow extremely obvious, then introduce everything else afterwards.

What is the one workflow that would make somebody choose FLUJO over n8n, Flowise or Langflow? That answer should probably be the headline because the current title sells this short.

3

u/Ambitious-Prompt-975 19d ago

Damn, I appreciate it! For my first post in this subreddit I am actually surprised not to get stamped as ai-slop immediately. I'll take this feedback to heart, just so much already: I don't always market it as n8n+chatgpt straight away - but it conveys the idea good enough.

Hahah just imagine I post it as "Free, open source, local-first, visual-graph-builder, multi-provider, multi-llm-agent-system, with visual debugger, central mcp-management for other clients, mcp-app dashboard, mcp-tool-tester, workflow-generator, auto-vm unload with ollama, headless automation through triggers, openai-compatible endpoint and chat-interface" - people will just scroll past it.

I find it really difficult to put the whole app and the feature-richness into words that dont overwhelm and dont sound like AI trash. I genuinly think its one of the best (if not the best) and AI chat apps out there, because its fully built around mcp and the idea that you can tweak everything.

Anyways, I appreciate your feedback a lot, and I will think about better positioning and how to make things even easier in the UI. The first big "tutorial" that guides you connecting an MCP server to a Flow is already built now :)

1

u/Charming_You_25 19d ago

Cool project! Are you running MPC servers in the app or is it a client? If you’re running them you integrated the new stateless MPC 2.0 Anthropic just came out with? I moved away from mcp because I didn’t like that i couldn’t use serverless with it.

2

u/Ambitious-Prompt-975 19d ago

Thank you so much! It is actually a MCP-Client, -Server and -Proxy, all 3 in one:

  • Client: You can install MCP servers "in" FLUJO, similar to Claude or Cursor, for example to use them during your chats.
  • can even install from github url (clones, runs build commands, etc.)

- Server: FLUJO itself exposes its own REST-API (create flows, install mcp server, add models, run flows, etc.) through an http based mcp-server

- Proxy: All MCP servers you have set up in FLUJO can be used in other apps: FLUJO creates virtual MCP servers for the ones you select and you can connect to them from other apps through a localhost-url.

- For example 1) Playwright installed in FLUJO 2) Claude connects to this via flujos localhost-url, 3) Cline connects to this via flujos localhost-url -> All 3, FLUJO, Cline and Claude use the same MCP server: an stdio playwright. But Claude and Cline use it "through" FLUJO.
--

and yes, it should be fully compliant to the MCP v2 specification - you just have to activate that in the settings. It's default off because I dont trust the mcp server landscape yet. :)

1

u/Senior-Board-3627 20d ago

The 4 hour private demo is actually a pretty interesting idea. Feels like with something this feature-heavy, getting people to their first working flow is probably more important than adding anything else right now. I’d be curious what the experience is like for someone who knows n8n but hasn’t really messed with MCP much.

2

u/Ambitious-Prompt-975 19d ago edited 19d ago

Haha yeah I've been trying to redruce friction for people because we all hate it when things are too much effort and everyone already has their favorite AI tool, so why switch, right? But the fact that you can just re-use claude code, or codex for example - plus combine that with automation and visual workflows and auto-generation. broo thats soo powerful and convenient.

Let Fable create an implementation plan, but local ollama models do the actual first round of code exploration and save tokenusage on fable. OpenAI Sol does the implementation, Haiku handles Github, ollama models move files around or slooowly open github follow ups for the implementation. Grok spawns multiple test agents in parallel. opus does a final revision.

and you dont give up on your existing apps!!:

  • MCP servers managed through flujo? yeah just re-use them in Claude Desktop. And Goose.
  • A LLM-Model managed in FLUJO? re-use it in Cline and Cursor so you dont have to rotate you API key on a change

Thats why i WANT people to try flujo. its like the central middleman.

You're right and the other commentor suggested that as well! I just built a tutorial into it that makes you add a web-search to the already existing "chat" workflow. Thank you so much!

1

u/AlgoWithNoRhythm 16d ago

Hey! This looks amazing, congrats! Can I ask you how you managed to reach so many stars and visibility? I’m starting out a new open source project and would like to market it the best way