Cai vs Dust MCP Server Marketplace

“I set up Cai with a custom action to take a stack trace from my clipboard and open a pre-filled GitHub issue in 10 minutes. The Ollama backend means I can use a larger local model when I'm at my desk and fall back to Ministral 3B on the go. MIT license means I can fork it and add my team's internal tools.”

“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.”

“Ministral 3B is fine for basic text tasks but it stumbles on anything requiring real reasoning or domain knowledge. Most users will hit its limits quickly and need to set up Ollama anyway — which is a non-trivial setup process for non-developers. The privacy story is genuine but the capability bar is lower than what cloud alternatives offer.”

“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.”

“Cai represents a class of tools that become dramatically more useful as on-device models improve. When Bonsai-scale 1-bit models hit 8B+ quality at 131 tokens/sec locally, Cai's architecture is exactly right — a minimal, composable action layer on top of local inference. The MIT license means the community will build the plugin ecosystem.”

“I've been looking for a way to do quick AI rewrites and tone adjustments in any app — not just in a web browser — without pasting things into a chat interface. Cai works in Figma, Notion, Miro, everything. The local privacy angle matters a lot when I'm working on client content that's under NDA.”

“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.”