 |
VOOZH | about |
|
VOOZH | about |
We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.
Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.
Follow TNS on your favorite social media networks.
Become a TNS follower on LinkedIn.
Check out the latest featured and trending stories while you wait for your first TNS newsletter.
At the recent MCP Summit in New York City, The New Stack sat down with AWS’s Luca Chang, who works on the Bedrock team and is an MCP Specification Maintainer to boot.
MCP has quickly become the industry standard for connecting AI models and agents to tools and data, making it a critical component of the broader artificial intelligence stack. Chang explained how developers are choosing what to improve in MCP, how Amazon decided what to contribute to the open-source tool, and who is paying whose token budgets!
When TNS sat down with Chang, the developer was fresh out of a pre-conference MCP maintainer meeting. How does the MCP developer pool decide what to build next for the protocol? By bringing together a diverse set of priorities and perspectives, and hashing out what needs to be added. Don’t worry that the model will yield groupthink. According to Chang, the MCP maintainer cohort is sufficiently broad that there were too many topics to fit into the group’s recent meeting.
Not that making choices is easy. Chang explained that maintainers’ work includes weighing problems that need to be solved against smaller MCP changes that could unlock capabilities that are “really creative and interesting.” (Your edge case will face real competition for bandwidth.)
This is where corporations can play a role in building out open-source projects. Amazon’s major contributions to MCP (Tasks, Elicitations) arose from the AWS team mapping its cloud products to the protocol and finding that it came up short. So, it helped improve MCP’s ability to interact with cloud computing platforms.
At AWS, Chang explained, “we don’t exactly look to make contributions [to MCP] as quickly as possible […] the contributions sort of fall out of our customer use cases […] once we explore a use case and see that there is [a] gap in the protocol itself. That’s when we say, ‘oh, there might be something here that we can give back to the community.’”
For more on where Chang sees the most market demand for MCP servers, and why he doesn’t want agent-specific MCP servers, check out this latest episode of The New Stack podcast.
