The Creator of FastMCP Explains the Future of MCP

In this episode, we're joined by Jeremiah Lowin, Founder & CEO at Prefect and the creator of FastMCP, to explore how one of the most influential projects in the MCP ecosystem came to be - and where the protocol is heading next.We discuss the accidental origin of FastMCP, why Anthropic adopted it into the official SDK, what developers are getting wrong about MCP, and why Chris believes the biggest opportunity for AI agents isn't customer-facing applications, but internal enterprise systems. We also dive into MCP Apps, developer experience, protocol design, AI tooling, Python, and why building great abstractions is often more valuable than exposing more configuration.Along the way, we explore the rapid growth of the MCP ecosystem, how FastMCP became the default way many developers build MCP servers, why "too much magic" can actually hurt developer experience, and what the next generation of AI-powered applications will look like as agents move beyond simple tool calling into rich, interactive experiences.Prefect: https://www.prefect.ioJeremiah Lowin: https://www.linkedin.com/in/jlowinDemetrios: https://www.linkedin.com/in/dpbrinkmTimestamps:00:00 Lost My Entire Talk00:47 The Story Behind FastMCP02:08 Anthropic Adopted FastMCP02:34 When MCP Took Off04:10 FastMCP vs The Official SDK05:43 Is MCP Actually Dead?06:42 What Everyone Gets Wrong About MCP08:11 MCP's Biggest Use Case10:25 Building Internal AI Systems12:00 Why FastMCP Exploded13:29 Making Complex Software Simple15:10 Can Software Be Too Magical?20:11 MCP Apps Explained23:42 Why Python Needed MCP Apps27:54 The Future of AI Interfaces34:18 AI Should Generate UIs40:11 AI Deleted My Presentation43:30 The AI Assistant We Actually Need48:00 Personal AI vs SaaS52:28 The Future of AI Agents55:06 Final Thoughts

In this episode, we're joined by Stephen O'Grady, Co-Founder and Principal Analyst at RedMonk, to explore one of the biggest shifts happening in software engineering: AI is making code dramatically cheaper to produce, but everything downstream is becoming the new bottleneck.We discuss why SaaS isn't dead despite the hype, the explosive rise of MCP, why AI agents are overwhelming developer infrastructure, and what happens when every engineer suddenly has dozens of AI developers working alongside them. Stephen explains how package managers, code reviews, security, governance, and enterprise systems are all struggling to keep pace with AI-generated software.Along the way, we dive into AI coding tools, MCP adoption, developer productivity, infrastructure scaling, enterprise software, open source, package repositories, governance, and why the hardest problems in software may no longer be writing code—but managing everything that comes after.RedMonk: https://redmonk.comStephen O'Grady: https://www.linkedin.com/in/sogradyDemetrios: https://www.linkedin.com/in/dpbrinkm

In this episode, we're joined by Matt DeBergalis, CTO and Co-Founder of Apollo GraphQL, to explore what happens when AI agents start interacting with enterprise systems that were never designed for them.We dive into the collision between APIs, MCP, GraphQL, and agentic AI, and why traditional assumptions about trust, permissions, and security are breaking down. Matt argues that AI agents should be treated as untrusted actors by default, and explains why giving agents access to enterprise data creates entirely new challenges around governance, access control, and risk management.Along the way, we discuss semantic APIs, enterprise data silos, citizen developers, agent permissions, security boundaries, and how GraphQL and MCP can work together to make enterprise systems more accessible to both humans and AI. The conversation also explores why companies are racing to deploy agents despite the risks, and what the future of enterprise software might look like when AI becomes the primary consumer of APIs.Apollo GraphQL: https://www.apollographql.comMatt DeBergalis: https://www.linkedin.com/in/debergalisAlex Salkever: https://www.linkedin.com/in/alexsalkeverTimestamps:[00:00] AI, APIs, and Trust[01:16] MCP API Lessons[06:16] GraphQL and MCP Integration[12:55] API Security for MCP[16:10] Linux Kernel Security Concerns[19:09] API Design and Controls[21:52] Trust in Autonomous Systems[25:06] MCP GraphQL Wish List[27:13] API Access Patterns[28:44] GraphQL API Perspective

Matt DeBergalis, CTO and Co-Founder of Apollo GraphQL

In this episode of Agentic Conversations, we're joined by Shaun Smith, software engineer, open source advocate, and contributor at Hugging Face, to explore how AI coding has changed almost overnight.We dive into reinforcement learning, MCP (Model Context Protocol), Fast Agent, Claude Code, open source AI, and why today's language models have become so capable that many traditional software libraries are becoming "liquefied." Shaun explains how reinforcement learning unlocked long-running autonomous agents, why ideas are becoming more valuable than code, and how developers should think about building software in an era where AI can generate entire applications.Along the way, we discuss Hugging Face's MCP server, Fast Agent, AI-powered developer tools, multimodal applications, MCP Apps, context windows, coding assistants, Rust, Python, TypeScript, open-weight models, software architecture, and what the future of programming looks like when humans increasingly focus on design instead of implementation.Shaun Smith: https://www.linkedin.com/in/smithshaunDemetrios: https://www.linkedin.com/in/dpbrinkmHugging Face: https://huggingface.co⏱️ Timestamps[00:00] Introduction[01:56] The State of Open Source AI[05:18] Reinforcement Learning Changed Everything[07:50] Fast Agent Explained[10:18] Fast Agent as an MCP Reference Platform[12:20] Building Smarter AI Tools at Hugging Face[15:17] Natural Language Search Instead of APIs[17:46] Why MCP Apps Matter[20:06] The Evolution of MCP Apps[23:05] Building AI-Native User Interfaces[26:12] Context Is the New Programming Language[28:00] The End of Code Libraries[29:50] Why Developers Aren't Writing Code[31:25] AI Changes Software Engineering[33:05] The Future of Open Source AI[35:43] Claude Skills That Save Hours[38:02] Training Models with AI[39:05] Building Your Own AI Tools[40:50] MCP for Consumers, Enterprises, and Developers[43:42] Why Shell Access Makes Agents Smarter[45:18] Secure Agent Workflows[46:08] The Future of AI Interfaces[47:02] Outro#HuggingFace #MCP #OpenSourceAI

In this episode, we're joined by Ben Morss, Developer Advocate at DeepL, who spent months traveling across North America and Europe teaching developers about MCP, building MCP servers, and helping teams understand how AI agents actually use tools.We dive into the biggest misconceptions around MCP, why so many developers still misunderstand how it works, and what Ben learned after giving talks and workshops in 10 cities across four countries. Along the way, we explore MCP server design, tool calling, security concerns, translation workflows, developer education, and how DeepL is using MCP to bring high-quality language translation into AI-powered applications.DeepL: https://www.deepl.comBen Morss: https://www.linkedin.com/in/ben-morss-ph-d-15bab15/Alex Salkever: https://www.linkedin.com/in/alexsalkeverTimestamps:[00:00] AI and API Integration[00:41] DeepL at DevSummit[01:19] MCP Roadshow Origins[03:47] MCP Hackathon Insights[07:52] Security in Model Protocols[10:25] AI Expert vs Noob Queries[16:08] DeepL vs Frontier LLMs[18:16] MCP vs REST API[21:39] MCP Servers and DeepL

In this episode, we're joined by Cornelia Davis, Developer Advocate at Temporal and a longtime software architect who has spent decades helping shape modern cloud-native systems.We explore how programming has evolved from assembly language to cloud-native architectures, and why AI is forcing us to rethink software development once again. Cornelia argues that natural language is becoming a new programming abstraction, while durable execution may be the missing layer that makes AI agents reliable in production.The conversation dives into probabilistic software, long-running AI agents, MCP tasks, human-in-the-loop workflows, durable timers, distributed systems, and why developers may no longer need to think about infrastructure the way they once did.Cornelia Davis: https://www.linkedin.com/in/corneliadavisDemetrios: https://www.linkedin.com/in/dpbrinkmTemporal: https://temporal.ioTimestamps[00:00] AI Programming Abstractions[00:52] Abstraction Evolution in Programming[04:05] Text to SQL Evolution[10:08] Compensations for Natural Language[12:13] Durable MCP in AI[18:34] Streaming Session Explanation[21:31] Batch Processes with Tasks[29:29] Complexity Relocation in Systems[33:10] Complexity Relocation in Dev[36:36] Programming Model Shifts

Denny Lee is PM Director, Startups & Ecosystem at Databricks, a longtime Apache Spark, MLflow, and Delta Lake contributor — and one of the people behind Omnigent, the open-source meta-harness Databricks just released under Apache 2.0. He joins Demetrios to explain why the industry is moving from models to harnesses to meta-harnesses, why token spend is replaying the CapEx-to-OpEx shift all over again, and why he's using debating AI agents to plan a matcha farm in Taiwan.In this episode:🍵 Agents as research partners — Denny uses dueling agents to scout matcha-growing regions in Taiwan, down to soil pH, elevation, and processing infrastructure🥊 Why agents should debate each other — letting two models argue surfaces the questions you didn't know to ask🔱 Forking conversations — the missing UX pattern: branch a session, keep the shared context, explore two threads in parallel🧠 The meta-harness layer — how Omnigent sits above Claude Code, Codex, Pi, and custom agents so models and harnesses become hot-swappable parts👥 The two-pizza rule for agents — military span-of-control logic says you can manage 5–7 agents before you lose the thread💸 Tokenomics is the new DevOps — the CapEx→OpEx playbook repeats: give developers spend visibility, keep central governance for the rest🛡️ Policies, budgets, and guardrails — enforcing cost caps and approval rules at the harness layer instead of inside prompts🤖 Auto model selection — why classic machine learning (not another LLM) may be the right way to route tasks to cheap vs. frontier models✍️ "Created by" vs. "assisted by" — the open source accountability debate: whoever submits the code owns the code🗄️ Databases are back — agents need cheap, stateful memory, which is why Postgres, Lakebase, and serverless databases are having a momentIf you're building with coding agents, managing AI spend, or trying to keep up with the harness arms race, this one's for you.Links & Resources:Omnigent (open source): https://www.databricks.com/blog/introducing-omnigent-meta-harness-combine-control-and-share-your-agentsOmnigent GitHub: https://github.com/databricks/omnigentDenny Lee on LinkedIn: https://www.linkedin.com/in/dennygleeDenny's blog: https://dennyglee.comTokenomics Foundation announcement: https://www.finops.org/insights/finops-x-2026-day-1-keynote/Timestamps: [00:00] SOA to LLMOps Transition[01:06] Agentic Research Workflow[10:45] Agent Debate for Execution[13:53] Agentic Footnote Concept[24:41] Harnesses in Agent Systems[32:43] Harnessing Multi-Layered Agents[38:06] Token Spending Awareness[41:01] Token Spend Efficiency[43:53] Model Selection Frustration[51:06] Meta Harness in AI[53:15] Harness Layers Model[57:17] Wrap up#Tokenomics #AIAgents #Omnigent

Qdrant Roundtable episode: The Current State of Agentic RetrievalJoin the Community: https://go.mlops.community/YTJoinInGet the newsletter: https://go.mlops.community/YTNewsletterMLOps GPU Guide: https://go.mlops.community/gpuguideBig shout-out to Qdrant for the collaboration!// AbstractAI agents are only as good as the information they can find, retrieve, and remember. In this community roundtable with the Qdrant team, we explored the latest advances in agentic memory, vector search, retrieval systems, and production AI architectures.As AI agents move beyond simple chatbots into systems that can reason across large amounts of information, retrieval is becoming one of the most important layers in the AI stack. The discussion covered the real-world challenges of building agents that remember what matters, forget what doesn't, and consistently retrieve the right context at the right time.If you're building AI agents, RAG systems, or production AI applications, this conversation offers practical insights into where retrieval is headed and what it takes to build reliable, scalable agentic systems.// BioEwa SzyszkaEwa is a Developer Relations professional based in San Francisco with a background in Computer Science and Hardware Engineering, passionate about bridging the gap between technology and the developer community. She holds a BSc in Computer Science and an MSc in Electronics, bringing a strong blend of deep technical foundations and communication skills to her work.Dylan CouzonDylan is based in New York City, and he helps developers build better AI applications. He is passionate about AI, programming, open source, and robotics, and enjoys sharing what he’s building and learning along the way.Neil KanungoNeil is an experienced professional with expertise in data science, developer relations, and product growth. Currently serving as the Head of Developer Relations at Qdrant, Neil previously held the position of VP of Product Led Growth & Developer Relations at KX, where significant increases in product registration and user activation were achieved. At TIBCO, Neil managed a team focused on enhancing the adoption of TIBCO Spotfire through various initiatives, including tutorial videos and live webinars. With a strong technical background, Neil has developed innovative solutions in analytics, machine learning, and data visualization across multiple roles, including Engineering Data Analyst and Asset Integrity Engineer at Enterprise Products. Neil holds a Bachelor of Science in Radiation Physics from The University of Texas at Austin, a Master of Science in Mechanical Engineering from Texas Tech University, and is pursuing a Master in Applied Data Science from the University of Michigan.Evgeniya SukhodolskayaDeveloper Relations at Qdrant with 8 years of IT experience across software engineering, machine learning, and technical management, and 4 years in Developer Relations. Holds a Master’s in Machine Learning, Data Analytics, and Data Engineering. Passionate about NLP, data-centric AI, and the role of vector search in advancing AI technologies.Andrei CristeaAndrei is a Berlin-based Developer Relations Engineer at Qdrant, a prominent open-source vector database. With a Master’s degree in Artificial Intelligence from TU Munich, his expertise bridges AI, data infrastructure, and knowledge engineering.Hosted by Demetrios// Related LinksWebsite: https://qdrant.tech/~~~~~~~~ ✌️Connect With Us ✌️ ~~~~~~~Catch all episodes, blogs, newsletters, and more: https://go.mlops.community/TYExploreJoin our Slack community [https://go.mlops.community/slack]Follow us on X/Twitter [@mlopscommunity](https://x.com/mlopscommunity) or [LinkedIn](https://go.mlops.community/linkedin)] Sign up for the next meetup: [https://go.mlops.community/register]MLOps Swag/Merch: [https://shop.mlops.community/]

Kingsley Madikaegbu is the founder of HealID, a startup building agentic AI on top of the Model Context Protocol (MCP) for one of the most heavily regulated environments there is: healthcare.Recorded at MCP Dev Summit North America in New York, Kingsley sits down with Alex Salkever of the Agentic AI Foundation to break down how you give patients, doctors, caregivers, and family members each their own agent over the same medical record — without breaching HIPAA, leaking PHI, or letting an agent quietly go off the rails. In this conversation:🏗️ The four-layer architecture — Dumb data at the bottom, then access permissions, then MCP, then reasoning agents on top. Why logic never touches the data layer.🔐 MCP vs REST — Why enforcing per-role compliance in a REST API meant encoding permissions everywhere, and how MCP collapses that mess.🪪 HIPAA, auditability & traceability — Proving a specific person (not a snooping agent) accessed a record, with a full audit trail that regulators actually accept.🎟️ The nightclub-bouncer analogy — How MCP reorganizes the entire "club" per guest instead of just checking a VIP list.⌚ Wearables & real-world data — Turning an Apple Watch arrhythmia signal into a triaged, severity-scored workflow with doctors in the loop.🧭 Deterministic vs model-driven — Why anything clinical or regulatory stays binary, and the agent-as-coach (not decision-maker) pattern for patients.🛑 Keeping agents on the leash — Tool restriction, behavioral metadata, and drift/anomaly detection so an agent can't reinterpret its own job.⚡ The instant kill switch — Revoke permission, and the agent returns a hard 404, never partial data.⚖️ The liability question — When an agent follows a designed workflow and something goes wrong, who's responsible: patient, host, or provider? The industry hasn't decided.📋 Kingsley's MCP wishlist — Built-in traceability (OTEL-style spans), native time-bound enforcement, and guardrails against agent-to-agent data leakage.If you're building agentic systems for healthcare, finance, legal, or any regulated industry where "the agent did it" isn't a good enough answer — this one's for you.Links & Resources🔗 HealID — https://gethealid.com/🔗 Kingsley Madikaegbu — https://www.linkedin.com/in/kmadikaegbu🔗 Alex Salkever / Agentic AI Foundation — linkedin.com/in/alexsalkever🔗 MCP Dev Summit North America — https://events.linuxfoundation.org/mcp-dev-summit-north-america/Timestamps:[00:00] Intro[00:13] AI Agent Liability[01:10] MCP in Healthcare AI[06:30] MCP vs REST Architecture[11:29] Healthcare Integration Challenges[18:29] Non-compliant Patient Challenges[24:13] Deterministic vs Model-Driven Workflows[28:08] AI in Healthcare Conversations[34:38] Agent-to-agent workflows in healthcare[38:02] Future MCP security