Model Context Protocol creates value by enabling user-driven extensible integrations
Soham Ganatra · He quit his job, went all-in on AI agents—then grew to 100K users & a $30M Series A in a year. | ... · PMF Show · Sep 10, 2025 · at 47:49
Soham Ganatra, co-founder of AI integration platform Composio, explains how the Model Context Protocol (MCP) differs from native developer-built application integrations.
“And so, MCP enables the second kind of integrations, which is like you could turn any sort of smart software into an extensible thing so that as a user, you could say, hey, I want my specific software like cursor to connect with Jira, right? Because Jira is what I care about. Or maybe Calendar to Cursor, because that's maybe what I care about, right? And so MCPs are great that way, because like, if every software becomes kind of like an MCP client, or like, maybe, let's say, good softwares like that you are using, maybe they become MCP client. You have this advantage of connecting that client to a server, which could be like by Notion, and you might say, hey, my, this software now connects to Notion, right? Because that's the integration I care about. So, so that, that's my take on it, which is like, it creates a lot of value by making every software into an extensible thing that like other, like users could decide what they want to connect it with.”
quote is from the automated transcript, cleaned for reading: filler sounds and stutters are removed, nothing is rephrased. names can be misheard (the analysis reads context, assessments check outside sources). how →