Uploaded November 2025 | Updated September 2026, 4 hours ago

---

Postman’s Head of API Client, Dustin Schau, shares how Postman evolved from “REST client” to a multi‑protocol platform (HTTP, gRPC, GraphQL, AI, MCP) with Flows, Agent Mode, testing, and automation. He discusses changing perceptions, reusing streaming patterns, and how to prototype and validate MCP servers with Postman’s generator, client, and manual debug workflows.

CHAPTERS:
0:04 - Intro: Postman and the API Client team
0:21 - Conference panel and live demo highlights
1:28 - From REST client to much more (11 years of Postman)
1:52 - Supporting 8 protocols incl. HTTP, gRPC, GraphQL, MCP
2:25 - Send/see/save works across all protocols
3:19 - Flows and Agent Mode in practice
3:56 - The challenge: change the “just a REST client” perception
4:43 - Reusing streaming patterns across protocols
5:01 - “Build it and they will come” isn’t real
6:32 - Tests inside Postman: scripting for quality
7:02 - Automation: Collection Runner, Monitors, CI/CLI
7:55 - How to experiment with MCP on Postman
8:42 - MCP server generator and Agent Mode integration
10:31 - Your MCP is only as good as your APIs
11:54 - Use case‑oriented tools; keep tool sets small