Why Smartsheet Built an MCP Instead of Just Another API

When Smartsheet decided to go all-in on MCP, it wasn't a default choice — it was a deliberate engineering philosophy. Bring the knowledge to where AI natively wants to work, and be surgical about how data gets used.

In this clip, Shelly Kramer digs into the decision with Drew Garner, SVP of Engineering at Smartsheet — and the architecture is more interesting than it might sound at first.

Smartsheet launched with 36 tools, built to evolve with client and industry-specific differentiation over time. But what Drew's most excited about is what comes bundled with those tools: custom UI, prompt cookbooks, and client-specific knowledge that ships alongside the toolset. Quick iteration cycles. Tailor-fit experiences. Unique workflows delivered fast.

And yes — AI agents can discover and use Smartsheet capabilities without being pre-programmed to do it.

Drew also maps out a fascinating creator flywheel: agents start by reading and exploring — getting to know your sheets, portfolios, and workflows. Then they move to creating. Then transforming existing data into something entirely new. Read → Create → Transform. It's a progression that mirrors how humans actually learn a new tool.

The MCP isn't just a technical choice. It's a bet on how AI and enterprise software grow together. 👇

#MCP #Smartsheet #EnterpriseAI #AIAgents #DigitalTransformation #AIStrategy #GenAI #AIEngineering #FutureOfWork #EnterpriseTech

Видео Why Smartsheet Built an MCP Instead of Just Another API канала Kramer&Co