Lindy AI MCP Server Marketplace vs Perplexity Comet

“The primitive here is a hosted MCP client that resolves server discovery and auth so you don't have to — that's legitimately useful friction removal. But the DX bet is that no-code is the right layer for agent integrations, and that's exactly where I get off. MCP is a protocol designed so developers can compose tools programmatically; putting a marketplace UI on top of it doesn't make agents more capable, it makes the configuration surface bigger and the debuggability worse. The moment-of-truth test: when your agent misbehaves at step 4 of a 6-step workflow, how do you trace which MCP server returned bad data? If the answer is 'check our logs dashboard,' I'm reaching for the raw SDK every time.”

“The category is no-code agent integration, and the direct competitors are Zapier's AI actions, Make's AI modules, and n8n's MCP nodes — all of which have larger connector libraries, more mature error handling, and existing user bases who already paid for the platform. Lindy's specific bet is that MCP standardization collapses the integration layer enough that being early to a marketplace wins, but MCP adoption among enterprise SaaS vendors is still thin enough that '150 servers' likely means 100 wrappers around the same REST APIs everyone already has. What kills this in 12 months: Anthropic ships native MCP tooling inside Claude.ai for Teams, and Lindy's marketplace becomes a curiosity for the 40 people who were using it.”

“Comet is competing directly with Arc's Browse, Google's Project Jarvis, and Anthropic's computer-use demos — except those shipped broadly and Comet is invite-only for a Q3 2026 general rollout. The specific failure scenario is obvious: any task requiring login state management, CAPTCHAs, or multi-domain auth handoffs falls apart immediately, and Perplexity hasn't shown evidence of solving those problems at scale. My prediction for what kills this in 12 months: Google ships Gemini-native browser automation in Chrome, erasing Comet's differentiation with zero distribution disadvantage. To earn a ship, Comet needs to demo booking a multi-leg international flight with seat selection, payment, and confirmation — live, unscripted, first try.”

“The thesis is falsifiable: by 2027, MCP becomes the TCP/IP of agent-to-tool communication, and whoever controls discovery and credentialing for that layer controls enterprise agent adoption. The dependency that has to hold is that MCP doesn't fragment into vendor-specific dialects the way REST+OAuth did — and that's a genuine risk, not a vibe. The second-order effect that nobody is talking about: if MCP server marketplaces win, SaaS vendors stop building native AI features and start publishing MCP servers instead, which quietly shifts the AI integration budget from the SaaS vendor to the orchestration layer. Lindy is early on this trend line — MCP standardization is six months old — and being early here means the catalog quality is thin, but the positional bet is real infrastructure thinking, not trend-chasing.”

“The thesis here is falsifiable and specific: by 2028, the browser is not a viewport but an execution environment, and the team that controls the AI-browser layer controls the intent graph of the web. Comet is betting on this at the infrastructure level — not bolting agents onto a tab, but rebuilding the browser around the agent primitive. The second-order effect that matters most is what this does to web analytics and SEO: if agents complete tasks without humans seeing pages, the entire attention economy built on pageviews collapses. Comet is riding the computer-use trend line and is roughly on time — OpenAI Operator launched earlier, but browser-native execution versus API-layer automation is a real architectural distinction worth watching. The dependency that has to hold: agentic task completion rates must cross ~85% reliability before mainstream users tolerate it.”

“The buyer is a mid-market ops or RevOps lead who wants automations without an engineering ticket — that's a real budget and a real buyer, but Zapier already owns that person's credit card and their trust. Lindy's moat argument would have to be 'MCP-native from the start gives us better agent quality than bolted-on competitors,' but that's a technical claim dressed as a business moat, and technical leads evaporate when the better-funded player catches up. The pricing structure also doesn't scale with value delivered — flat monthly tiers for agent workflows mean your heaviest users are your worst unit economics, and 'contact sales' for business plans from a product this early signals they haven't figured out what enterprise customers actually need from this yet.”

“The buyer here is the $20/mo Perplexity Pro subscriber, which means Comet is a retention feature masquerading as a product launch — there's no incremental revenue attached to it unless Perplexity spins it into a higher tier. The moat question is brutal: Comet's agentic capability sits on top of browser automation infrastructure that Google, Microsoft, and OpenAI are all building simultaneously, and none of them need to charge $20/mo to distribute it. The specific business problem is that Perplexity is spending engineering capital on a browser at exactly the moment when its search revenue model remains unproven — this is a distraction bet that only makes sense if it dramatically increases Pro retention or unlocks enterprise contracts. What would need to change: a dedicated Comet tier at $40-50/mo with verifiable task-completion SLAs and an enterprise sales motion.”

“The job-to-be-done is sharp: complete a web task I would otherwise do manually across 4-8 browser tabs. That's a real, recurring job with measurable time cost, and Comet is one of the first products to attempt it at the browser layer rather than the script or extension layer. The onboarding concern is real though — invite-only access means the vast majority of Pro subscribers can't evaluate whether this replaces their current workflow, making it impossible to call this a complete product today. The opinion baked into Comet is correct: the browser should understand goals, not just URLs. The gap between what's shipped and what's needed is a public availability date that isn't six months away, and documented task success rates so users can set realistic expectations before switching.”