If your MCP server has dozens of tools, it’s probably built wrong.You need tools that are specific and clear for each use case—but you also can’t have too many. This creates an almost impossible tradeoff that most companies don’t know how to solve.That’s why we interviewed Alex Rattray, the founder and CEO of Stainless. Stainless builds APIs, SDKs, and MCP servers for companies like OpenAI and Anthropic. Alex has spent years mastering how to make software talk to software, and he came on the show to share what he knows. We get into MCP and the future of the AI-native internet.If you found this episode interesting, please like, subscribe, comment, and share. Want even more?Sign up for Every to unlock our ultimate guide to prompting ChatGPT here: https://every.ck.page/ultimate-guide-to-prompting-chatgpt. It’s usually only for paying subscribers, but you can get it here for free.To hear more from Dan Shipper:Subscribe to Every: https://every.to/subscribeFollow him on X: https://twitter.com/danshipperReady to build a site that looks hand-coded—without hiring a developer? Launch your site for free at Framer.com, and use code DAN to get your first month of Pro on the house.Timestamps:00:00:00 - Start00:01:14 - Introduction00:02:54 - Why Alex likes running barefoot00:05:09 - APIs and MCP, the connectors of the new internet00:10:53 - Why MCP servers are hard to get right00:20:07 - Design principles for reliable MCP servers00:23:50 - Scaling MCP servers for large APIs00:25:14 - Using MCP for business ops at Stainless00:28:12 - Building a company brain with Claude Code00:33:59 - Where MCP goes from here00:41:10 - Alex’s take on the security model for MCPLinks to resources mentioned in the episode:Alex Rattray: Alex Rattray (@RattrayAlex), Alex Rattray Stainless: https://www.stainless.com/

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related