AI tool comparison
Dust MCP Server Marketplace vs Rowboat
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Productivity
Dust MCP Server Marketplace
No-code MCP connectors for enterprise AI agents, 30+ tools ready to go
75%
Panel ship
—
Community
Free
Entry
Dust launched a curated MCP Server Marketplace inside its enterprise AI platform, enabling teams to install pre-built connectors for Notion, HubSpot, Jira, and 30+ other tools into their AI agents without writing code. It sits on top of the Model Context Protocol standard, letting non-technical teams wire up data sources and actions to AI agents through a point-and-click interface. The marketplace is open-source, meaning the connector definitions are inspectable and community-extensible.
Productivity
Rowboat
Local-first AI coworker with persistent knowledge graph, no cloud lock-in
75%
Panel ship
—
Community
Free
Entry
Rowboat is a local-first, open-source AI coworker that connects to your email and meeting notes, builds a persistent Obsidian-compatible knowledge graph from them, and uses that context to draft documents, meeting briefs, slide decks, and emails. It works with local models via Ollama or LM Studio, or with hosted APIs, and supports MCP for connecting external tools. The design philosophy is deliberately anti-cloud: all data stays in plain text Markdown files you can read, grep, and version-control. The knowledge graph is transparent — you can open it in Obsidian and see exactly what the AI knows about you. No black-box embeddings in a proprietary vector store, no "trust us with your emails" data agreements. Rowboat implements what Karpathy described as a "long-term memory coworker" — an AI that compounds value over time because it actually knows your history, your projects, and your terminology. TypeScript codebase, Apache 2.0 license, surging on GitHub trending this week.
Reviewer scorecard
“The primitive here is clear: a curated registry of MCP server definitions that resolve the connector-authoring problem for teams who want agents but don't want to write glue code. The DX bet is that open-sourcing the marketplace layer gives builders trust and extensibility without forking the whole platform — that's the right call. Where I get cautious is the hosted dependency: you're not running these MCP servers independently, you're installing them into Dust's runtime, so the composability story only works if Dust stays in the stack. The open-source angle earns the ship, but the runtime coupling is a real constraint worth naming before you commit.”
“Plain-text persistence + MCP + local model support is the right architecture. It'll survive AI winters and API deprecations. The Obsidian compatibility alone is a killer feature for the PKM crowd that already lives in that ecosystem.”
“The direct competitor is every workflow automation platform — Zapier, Make, and now native agent tooling from Salesforce and HubSpot themselves — and Dust's answer is 'we support MCP and they don't yet.' That's a six-month moat at best. The scenario where this breaks is the mid-market enterprise team that gets 80% of this from a Microsoft Copilot Studio connector pack their IT department already owns. What kills this in 12 months: HubSpot and Notion ship their own MCP servers directly, the connector advantage evaporates, and Dust is left competing on agent quality alone against better-funded platforms. To earn a ship, Dust needs to demonstrate that the agent reasoning layer is differentiated enough to survive the connector commoditization that's already underway.”
“The 'knowledge graph from email' promise is where these tools historically fall apart — noisy inboxes produce noisy graphs. And 'local-first' often means 'labor-intensive setup.' The abstraction is right but execution on messy real-world data is hard. Watch the 1-month reviews.”
“The buyer is a department head or CTO at a 200-500 person company who has already bought into the AI agent premise but can't justify an eng sprint to build Notion-to-Jira connectors — this is a real check-writer with a real pain. The moat question is where it gets complicated: open-sourcing the marketplace is a community play, not a defensibility play, and if the connectors are the reason people show up, making them free and forkable undermines the expansion revenue story. The specific business decision that earns the ship is the enterprise pricing model — if Dust is charging on seats or agent runs rather than connector count, the open marketplace actually drives stickiness into a paid runtime, which is a legitimate wedge. That arithmetic needs to hold or this is a very expensive developer relations program.”
“The job-to-be-done is unambiguous: connect an enterprise AI agent to the tools the team already uses, without involving an engineer. That's a single, complete sentence, which is a good sign. Onboarding presumably goes: browse marketplace, click install on Notion connector, authenticate via OAuth, agent now has read/write access to Notion — if that's genuinely under two minutes, this is a strong product decision. The completeness gap is agent quality: the marketplace solves the connection problem but if the underlying agent reasoning is weak, users are still babysitting outputs and the connector convenience doesn't matter. The product has a real opinion — MCP as the standard, curated over open-ended — and that's the right call for enterprise buyers who don't want to evaluate 400 community connectors.”
“Personal knowledge infrastructure that you own is becoming the moat in AI-augmented work. Rowboat's transparent, portable approach builds durable value. In two years the question won't be which AI assistant you use, but which knowledge graph underlies it.”
“Drafting meeting briefs and decks from accumulated context is the workflow I've wanted for years. The Obsidian integration means my notes and my AI context stay in sync naturally — no separate import/export dance.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.