https://roboco.io/en/tags/mcp/ Recent content in Mcp on ROBOCO Hugo en-us Mon, 04 May 2026 11:30:00 +0900 https://roboco.io/en/posts/ruflo-claude-code-multi-agent-orchestration/ Mon, 04 May 2026 11:30:00 +0900 https://roboco.io/en/posts/ruflo-claude-code-multi-agent-orchestration/ <blockquote> <p>How to design Claude Code workflows that learn from a team&rsquo;s insights, not just a single project.</p> </blockquote> <figure><img src="https://roboco.io/posts/images/Dohyun.png"><figcaption> <h4>Dohyun Jung - Principal Consultant, ROBOCO</h4> </figcaption> </figure> <hr> <p>Use Claude Code for a month and the limits become clear. Context disappears along with the session, and breaking work apart and putting it back together is ultimately a human job. The bigger problem surfaces the moment you have multiple projects and multiple developers. The testing strategy learned on project A, the refactoring pattern discovered by developer B, the architectural judgment validated in repository C — none of it flows well between them. <code>ruvnet/ruflo</code> (formerly Claude Flow) targets exactly this gap. As of May 4, 2026, it has 39.4k stars and 4.5k forks on GitHub, with v3.6.27 as the latest release.<sup id="fnref:1"><a href="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup><sup id="fnref:2"><a href="#fn:2" class="footnote-ref" role="doc-noteref">2</a></sup> Ruflo aims to be an orchestration layer on top of Claude Code that adds roughly 100 specialized agents, HNSW vector memory, a plugin system, and Zero-Trust federation. This post lays out what Ruflo actually solves and what it does not, particularly from the standpoint of <strong>how to organically reuse the insights that multiple projects and multiple developers acquire</strong>.</p> https://roboco.io/en/posts/is-mcp-necessary-for-vibecoding/ Tue, 01 Apr 2025 10:28:00 +0900 https://roboco.io/en/posts/is-mcp-necessary-for-vibecoding/ <figure><img src="https://roboco.io/posts/images/Dohyun.png"><figcaption> <h4>Dohyun Jung - Principal Consultant, ROBOCO</h4> </figcaption> </figure> <p>Look around the developer community these days and you will run into plenty of talk about MCP, the Model Context Protocol. The argument goes that if we want AI to work more intelligently and more flexibly, we need an interface like MCP. And honestly, I have been watching this technical trend with real interest. Part of me looks forward to where it goes, and part of me wonders: does MCP actually have to be there right now?</p>