Perplexity just said the quiet part out loud
At Perplexity's developer conference, CTO Denis Yarats said the company is moving away from MCP internally and prefers APIs and CLIs instead. That line spread fast because Perplexity is not some random outsider taking shots at the protocol. It has an official MCP server in its docs, plus one-click install flows for Cursor, VS Code, and Claude Desktop.
The original post from Morgan Linton, quoting Yarats with a conference photo, is here: https://x.com/morganlinton/status/2031795683897077965. Aakash Gupta added the broader market read here: https://x.com/aakashgupta/status/2031950037031510161. KryptonAI piled on with the contradiction in plain English here: https://x.com/KryptonAi/status/2032012006375453127.
If you run a small business and have been hearing vendors pitch MCP as the future of AI integration, this matters. One of the protocol's most visible early adopters just told developers that when the work is real, they trust older tools.
Why this is a bigger deal than one conference quote
MCP was introduced by Anthropic in late 2024 as a universal way for AI agents to connect to tools, apps, and data sources. The sales pitch was clean: one standard instead of every vendor building their own custom connection layer. That sounds great on a whiteboard.
The problem is that standards do not win because the idea is elegant. They win when they are boring, durable, and safe enough for businesses to bet on.
Right now, MCP does not look like that. Critics have pointed to a spec that has not materially moved since November 2025, a thin security story, and transport choices that get messy outside of toy demos. Aakash Gupta's thread points to research from Knostic claiming zero authentication across roughly 2,000 MCP servers they reviewed. If that finding holds up, it is not a minor footnote. It is a giant red flag for any company with customer data, payroll records, or internal documents in the loop.
Then there is stdio. It is simple for local experiments. In production, it can turn into glue-code pain fast. Teams end up fighting process management, reliability, and deployment edge cases instead of shipping value.
That is the backdrop for Yarats' comment. Perplexity is telling developers, in effect, that the nice demo layer is not the same thing as a production stack.
Why APIs and CLIs are winning the grown-up argument
This is not sexy, but it is the truth: APIs and CLIs already solved a lot of the hard business problems.
REST APIs come with battle-tested patterns for authentication, versioning, rate limits, auditability, and error handling. Enterprise buyers know how to review them. Procurement teams know how to ask questions about them. Compliance teams know where to look. Your developer can swap one API provider for another without rewriting their mental model from scratch.
CLIs have a similar advantage inside operations-heavy teams. They are scriptable, inspectable, and predictable. If something breaks, your technical person can usually trace it.
That matters even more in Perplexity's case because this is not a tiny startup making theory-first bets. The company is targeting $656 million in ARR by the end of 2026, according to the accounts discussing the conference remarks, and its APIs already reach hundreds of millions of Samsung devices and six of the Magnificent 7. A company operating at that scale does not casually pick the less reliable integration path for internal use.
What small business owners should do now
My take is simple: do not build your AI roadmap around MCP today.
That does not mean MCP is dead. It may still become a useful standard over time. A lot of good ideas look rough before they get good. But if you are a small business, your job is not to finance the protocol's adolescence.
What should you do instead?
- Ask vendors whether their core integration works over a normal API, not just MCP
- Favor products with clear auth, logging, and permission controls
- Treat CLI support as a plus if your team automates anything internally
- Keep MCP experiments in a sandbox, not in the middle of finance, customer support, or operations
- If a vendor says “we support MCP,” ask what their non-MCP fallback is
That last question is the killer one. If the fallback is missing, you are not buying flexibility. You are buying dependency on a layer that even some of its loudest supporters are stepping away from in practice.
The real lesson behind the Perplexity contradiction
Perplexity can believe two things at once: MCP is useful for developers to experiment with, and APIs plus CLIs are still the better foundation for serious systems.
That is not hypocrisy so much as market reality. Lots of companies support emerging standards at the edge while keeping their core business on infrastructure they trust.
For SMBs, the lesson is clear. Separate demo-friendly from business-ready. If your agency, e-commerce shop, law firm, or home services company is trying to automate work with AI, you want integrations that survive audits, staff turnover, vendor changes, and the occasional bad day.
Today, APIs and CLIs clear that bar. MCP does not. Maybe it gets there later. For now, the smart move is to let larger players absorb the uncertainty while you build on the stuff that already works.