Stenobird

Episode

Notion’s Token Town: 5 Rebuilds, 100+ Tools, MCP vs CLIs and the Software Factory Future — Simon Last & Sarah Sachs of Notion

Podcast
Latent Space: The AI Engineer Podcast
Published
Apr 15, 2026
Duration seconds
4637
Processing state
processed
Canonical source
https://www.latent.space/p/notion
Audio
https://api.substack.com/feed/podcast/194195821/10f31b379fbf657fd80757e3b4244e4f.mp3
JSON
/v1/public/podcasts/latent-space-ai-engineer/episodes/notion-s-token-town-5-rebuilds-100-tools-mcp-vs-clis-and-the-software-factory-future-simon-last-sarah-sachs-of-notion
Markdown
/podcast/latent-space-ai-engineer/notion-s-token-town-5-rebuilds-100-tools-mcp-vs-clis-and-the-software-factory-future-simon-last-sarah-sachs-of-notion.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/latent-space-ai-engineer/episodes/notion-s-token-town-5-rebuilds-100-tools-mcp-vs-clis-and-the-software-factory-future-simon-last-sarah-sachs-of-notion/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/latent-space-ai-engineer/notion-s-token-town-5-rebuilds-100-tools-mcp-vs-clis-and-the-software-factory-future-simon-last-sarah-sachs-of-notion.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

Notion engineers reveal why they rebuilt their AI agent architecture five times to move beyond simple model wrapping. The discussion explores the transition from basic tool-calling to a robust 'Agent Lab' capable of complex, autonomous workflows.

Topics

  • AI Agents
  • Model Context Protocol
  • Software Engineering
  • Product Development
  • Notion AI
  • LLM Tool Calling
  • Agentic Workflows
  • Enterprise AI

Highlights

  • Main idea: The 'Agent Lab' thesis focuses on building product systems around frontier capabilities rather than just wrapping LLMs
  • Failure mode: Early agent attempts failed due to lack of tool-calling standards, short context windows, and excessive complexity exposed to the model
  • Practical takeaway: Using MCP (Model Context Protocol) provides a superior, tightly permissioned security model compared to the murkier risks of CLIs
  • Engineering insight: Effective AI product development requires 'Model Behavior Engineers' to focus on high-quality evals and data-driven refinement
  • Future vision: The shift toward 'software factories' where agents autonomously spec, code, test, and maintain entire codebases

Chapters

  1. 1:00 The Iterative Path to Production: How Notion manages the tension between shipping stable alpha features and simultaneously developing the next generation of AI tools.
  2. 6:50 The Agent Lab Thesis: A deep dive into why Notion's approach to AI is about building a system for collaboration rather than just a chatbot interface.
  3. 12:50 High-Velocity Engineering Culture: How Notion organizes engineering teams to handle the rapid, daily shifts in direction inherent in the AI era.
  4. 24:20 The Rise of Model Behavior Engineers: Discussing the evolution of specialized roles focused on evaluating model outputs and managing complex tool-calling logic.
  5. 36:00 MCP vs. CLIs: The Security Frontier: Comparing the utility of the Model Context Protocol for lightweight agents against the power and risks of terminal-based environments.
  6. 59:15 Agentic Pricing and Workflows: Exploring the economic and technical challenges of charging for token usage in a world of varying model capabilities.
  7. 1:10:45 Meeting Notes as Data Capture: How Notion views meeting transcription as the foundational data layer for future autonomous agentic workflows.