Letting AI Interface with your App with MCP
summary
Claim: a standard Model Context Protocol lets assistants call services so one assistant can handle arbitrary web tasks. Demo builds live an MCP server and shows three servers (journaling, locationator, weather) plus OAuth 2.1 authentication, dynamic tool approval, JSON-to-markdown rendering and client-side dynamic UI cards. Clients remain immature, plugin ecosystems stay fragmented, and the surprising bit is that the protocol already supports authenticated actions, multimodal context and service-driven UI formatting.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:24What Jarvis can do that we can't yet
- 4:34Integration challenges
- 6:43Evolution of LLMs and tool calling
- 10:58MCP integration solution
- 13:05Live MCP demo
- 17:39Natural user interaction
- 19:04Resources & closing
related talks
37mLetting AI Interface with Your App with MCPs
45mModel Context Protocol (MCP): The future of user interactions?
33mThe Model Context Protocol: Connecting AI to Everything
52mUnlocking AI Interoperability: A Deep Dive into the Model Context Protocol
30mComposable AI: Building Next-Gen AI Agents with MCP
29mEmpowering Your Product with Agentic AI
20mLetting AI Interface with Your App with MCPs
35mMCP in Action: Real-World Use Cases & Design Patterns