Ganatra: MCP Lacks Client Post-Processing for Long Context Responses
Soham Ganatra · ⚡️Composio: 10,000+ tools that evolve for Agents — Karan Vaidya and Soham Ganatra · Aug 4, 2025 · at 4:04
Soham Ganatra, co-founder of Composio, explains technical limitations observed when using the Model Context Protocol (MCP) in production.
0:00 / 0:22exact quote · 22.5s
▶ Watch the full episode on YouTube → 720p mp4 · rendered on demand · StarZero watermark
“MCP let's just say you have a tool that has really long context, a really long sort of response. Currently, if you use MCP for those kinds of tools, it ends up sort of messing up, right? Because let's say I'm trying to fetch like a hundred emails on Gmail and my sort of context overflow occurs. And I'm not able to sort of post-process the output that is coming out from MCP. I'm not able to sort of play around with it before it reaches my sort of LL.”
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 →
More from Soham Ganatra
Ganatra: Existing AI tool-calling benchmarks are not production-ready
“Tool calling has a lot of different evals. You have seen the function tool calling evals. You have multi-function, like, multi-tune tool calling evals. But, like, none of them are actual, like, production quality. Like, none of them are actually something that…”
Ganatra: 95% of Composio integrations are built and maintained by agents
“So, 95% of all our integrations are completely built using agents, maintained using agents.”
Ganatra: Server-Controlled Schemas in MCP Complicate Client-Side Customization
“Some of the other things that we have observed is like, hey, maybe I want to sort of change the tool descriptions, but like in MCP, the tool descriptions are controlled by the server itself. And so essentially for me as a developer who's sort of using an MCP, …”
Ganatra: Over 100,000 developers have built with Composio
“In terms of developers, we have, like, more than 100,000 developers who have been building on top of course and, like, trying our product out.”
Ganatra: Poor API documentation is the main source of tool-calling errors
“Is this Salesforce tool getting transformed into the right request payload so that it is hitting the right endpoint in Salesforce, right? And that is like the major source of error today, because a lot of documentations are not great. A lot of like ad cases ar…”