Agentic AI Foundation

@mlops.community

1.5K followers · usually 559 views a post

Views

3.8K

Likes

48

Comments

5

Shares

3

Selling · SaaS › AI Tool

Perplexityseen in 8 videos →

Why it worked

The video discusses a relevant and potentially controversial topic in the AI space (moving away from a specific framework to APIs), which would appeal to a niche audience interested in AI development and tools. The use of a prominent figure's statement (CEO of Perplexity) adds credibility and interest.

Summary

The speaker discusses how Perplexity is moving away from MCPs (likely a type of AI agent framework) and towards using APIs directly. They explain that MCPs were misunderstood and mis-sold, leading to unmet expectations and bloat. The speaker believes that APIs offer a more sensible and controlled approach for integrating tools.

Structure

1Introduction of Perplexity and their move away from MCPs
2Explanation of why MCPs are problematic (bloating context, cost)
3The CEO's statement about ditching MCPs
4MCPs being misunderstood and mis-sold
5The benefits of using APIs for tool integration

Product placement

Perplexity is mentioned as a company that is moving away from MCPs and towards APIs.

Original caption

Perplexity is not using MCPs?? #MCP #aiagents #AI

More from @mlops.community

Their other posts in the index, biggest breakout first.

On-screen text

Agentic AI Foundation DEBUG MODE PERPLEXITY'S CEO: WE'RE DITCHING MCP

Transcript

Perplexity, right? Which is a leader when it comes to AI like, and so forth, like the conference goes, we ditched MCP. We're not going to do that as soon as APIs. Because the CEO came out and said that. It's bloating our context. It's not giving us that we're Yeah, it's like adopting. Yeah, a lot of money, external factor. And I think MCP is not dead. For me, MCP is not dead. It is not misunderstood and potentially mis-sold. Yeah. It's been mis-sold. I like that. Yeah. It's been the expectations were not properly set. Yes. And I and maybe didn't even really know the perfect time to use that. Maybe we learned the appropriate time to use it was gone on. That's true. Maybe we just learned. Maybe now in hindsight, it seems obvious. But for external integration, not control the other side of the codebase. To me makes a lot of sense. Honestly, APIs have been so massive over the last decade. And I'm so glad is bringing the order to APIs that we once streamed off.