• MCP — The Model Context Protocol — an open standard that lets any AI assistant plug into any tool or data source without custom integration code.
• context window — The maximum amount of text a model can consider at once — its working memory for the current conversation or task.
• AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.

MCP apps let a tool result reach the user as a real clickable interface instead of the agent retyping data back and forth, and Prefab gives Python-only teams a way to generate that UI without touching JavaScript or React directly.

• 0:00MCP apps, and bypassing the agent
• 3:20Shipping UIs to an audience of Python engineers
• 4:45Constraining the problem to tables, forms, charts
• 5:43Composing a front end rather than building one
• 6:37The DSL, and the JSON in the middle
• 8:54Docs rendered in the thing they document
• 10:13Interactive tools, and a chart beside a table
• 12:56Full apps and the expensive copy paste problem
• 15:15Generative UI, and Python beating JSON on the wire

• videoThe Design-Code Roundtrip That Isn't — Jonathan Gordon, ReWeaver AI
• videoDesign at the Speed of Adjectives — Paul Bakaus, Renaissance Geek, Inc.
• videoTraining Taste — Thais Castello Branco, Taste Labs
• videoMousepower: agents that can’t be measured, can’t be managed. — Maximillian Piras, Yutori

• videoBuilding the Engine While Flying the Plane: Launching the Figma MCP Server — Jesse Lumarie, FigmaAI Engineer
• videoMCP Apps: Extending the Frontier — Ido Salomon & Liad YosefAI Engineer
• videoMCP Apps: Give the Model Data, Give the User a UI — Dustin Mihalik, IndeedAI Engineer

Checking sign-in…

Loading comments…