Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Voice agents + MCP ... When I watched this code walk-through from Laserdisc Librarian, I thought "wait, why didn't she edit out the LLM making those mistakes at the beginning ... oh I get it, good demo!" Vanessa shows how to use multiple MCP servers via the new `MCPClient`... show more

kwindla

14,683 subscribers

11,399 views • 1 year ago •via X (Twitter)

Science & Technology Education

Anya Rossi• Live Now

Private livecam show

3 Comments

kwindla1 year ago

MCPClient docs: @dylibso docs: Three Pipecat examples: If you're interested in voice agents and MCP, @vipyne will be hanging out with the Voice AI and Voice Agents community next month. Sign up for the course here (and get >$6,000 of free credits for a bunch of great realtime AI platforms):

Jordan Ross1 year ago

No. 3 below is actually the biggest misconception for most agency owners.

Ralph Miller1 year ago

@vipyne Why do I feel like I did when AWS came on the scene? Servers spun up but never down. When do we talk about supporting these great tools?

Related Videos

There's (still) no good way to use MCP servers outside of Claude desktop or a code editor. That's why I built my own. Here's a demo with MCP servers from alana goyal and browserbase 🅱️. Fully open source, link in replies 👇

There's (still) no good way to use MCP servers outside of Claude desktop or a code editor. That's why I built my own. Here's a demo with MCP servers from alana goyal and browserbase 🅱️. Fully open source, link in replies 👇

anirudh

39,130 views • 1 year ago

New short course: Build AI Apps with MCP Servers: Working with Box Files, built with Box and taught by Ben Kus , their CTO. Many AI applications require custom code for basic file operations. The Model Context Protocol (MCP) standardizes this by letting you offload file tasks to dedicated servers that provide tools an LLM can use directly. In this course, you'll process documents stored in a Box folder using the Box MCP server. Rather than writing custom integration code to connect to the Box API and download files, you'll design your application to use the tools provided via MCP. Skills you'll gain: - Build an LLM-powered document processing app, using the Box MCP server to access files - Design a multi-agent system using Google's Agent Development Kit (ADK), consisting of specialized agents for file operations - Coordinate the multi-agent workflow through an orchestrator that uses the Agent2Agent (A2A) protocol to connect to the agents You'll start with a local file-processing app, refactor it to work with Box's MCP server, then evolve it into a multi-agent system. Sign up here:

New short course: Build AI Apps with MCP Servers: Working with Box Files, built with Box and taught by Ben Kus , their CTO. Many AI applications require custom code for basic file operations. The Model Context Protocol (MCP) standardizes this by letting you offload file tasks to dedicated servers that provide tools an LLM can use directly. In this course, you'll process documents stored in a Box folder using the Box MCP server. Rather than writing custom integration code to connect to the Box API and download files, you'll design your application to use the tools provided via MCP. Skills you'll gain: - Build an LLM-powered document processing app, using the Box MCP server to access files - Design a multi-agent system using Google's Agent Development Kit (ADK), consisting of specialized agents for file operations - Coordinate the multi-agent workflow through an orchestrator that uses the Agent2Agent (A2A) protocol to connect to the agents You'll start with a local file-processing app, refactor it to work with Box's MCP server, then evolve it into a multi-agent system. Sign up here:

Andrew Ng

81,696 views • 10 months ago

Connecting Claude with web search is magic! Finally got the chance to play with MCP servers. I hooked up Claude Desktop with GitHub & Brave web search MCP servers for staying up to date with AI news. I also asked Claude to create a new GitHub repo and log the news there. This exceeded my expectations. Check the full video (at 2x) for the first demo. Let me know if you are interested in a full tutorial on how to set up the MCP servers.

Connecting Claude with web search is magic! Finally got the chance to play with MCP servers. I hooked up Claude Desktop with GitHub & Brave web search MCP servers for staying up to date with AI news. I also asked Claude to create a new GitHub repo and log the news there. This exceeded my expectations. Check the full video (at 2x) for the first demo. Let me know if you are interested in a full tutorial on how to set up the MCP servers.

elvis

41,804 views • 1 year ago

this is wild turns out the best part of Figma MCP is that the agents are really good at FigJam now when I plan work with the agents, I get ✨ collaborative ✨ diagrams that are easy to read, easy to share, and easy to edit

this is wild turns out the best part of Figma MCP is that the agents are really good at FigJam now when I plan work with the agents, I get ✨ collaborative ✨ diagrams that are easy to read, easy to share, and easy to edit

Amelia Wattenberger 🪷

15,251 views • 4 months ago

If your MCP server has dozens of tools, it’s probably built wrong. You need tools that are specific and clear for each use case—but you also can’t have too many. This creates an almost impossible tradeoff that most companies don’t know how to solve. That’s why I interviewed my friend Alex Rattray (Alex Rattray), the founder and CEO of Stainless. Stainless builds APIs, SDKs, and MCP servers for companies like OpenAI and Anthropic. Alex has spent years mastering how to make software talk to software, and he came on the show to share what he knows. I had him on Every 📧’s AI & I to talk about MCP and the future of the AI-native internet. We get into: • Design MCP servers to be lean and precise. Alex’s best practices for building reliable MCP servers start with keeping the toolset small, giving each tool a precise name and description, and minimizing the inputs and outputs the model has to handle. At Stainless, they also often add a JSON filter on top to strip out unnecessary data. • Make complex APIs manageable with dynamic mode. To solve the problem of how an AI figures out which tool to use in larger APIs, Stainless switches to “dynamic mode,” where the model gets only three tools: List the endpoints, pick one and learn about it, and then execute it. • MCP servers as business copilots. At Stainless, Alex uses MCP servers to connect tools like Notion and HubSpot, so he can ask questions like, “Which customers signed up last week?” The system queries multiple databases and returns a summary that would’ve otherwise taken multiple logins and searches. • Create a “brain” for your company with Claude Code. Alex built a shared company brain at Stainless by keeping Claude Code running on his system and asking it to save useful inputs—like customer feedback and SQL queries—into GitHub. Over time, this creates a curated archive his team can query easily. • The future of MCP is code execution. Instead of giving models hundreds of tools, Alex believes the most powerful setup will be a simple code execution tool and a doc search tool. The AI writes code against an API’s SDK, runs it on a server, and checks the docs when it gets stuck. This is a must-watch for anyone who wants to understand MCP—and learn how to use them as a competitive edge. Watch below! Timestamps: Introduction: 00:01:14 Why Alex likes running barefoot: 00:02:54 APIs and MCP, the connectors of the new internet: 00:05:09 Why MCP servers are hard to get right: 00:10:53 Design principles for reliable MCP servers: 00:20:07 Scaling MCP servers for large APIs: 00:23:50 Using MCP for business ops at Stainless: 00:25:14 Building a company brain with Claude Code: 00:28:12 Where MCP goes from here: 00:33:59 Alex’s take on the security model for MCP: 00:41:10

If your MCP server has dozens of tools, it’s probably built wrong. You need tools that are specific and clear for each use case—but you also can’t have too many. This creates an almost impossible tradeoff that most companies don’t know how to solve. That’s why I interviewed my friend Alex Rattray (Alex Rattray), the founder and CEO of Stainless. Stainless builds APIs, SDKs, and MCP servers for companies like OpenAI and Anthropic. Alex has spent years mastering how to make software talk to software, and he came on the show to share what he knows. I had him on Every 📧’s AI & I to talk about MCP and the future of the AI-native internet. We get into: • Design MCP servers to be lean and precise. Alex’s best practices for building reliable MCP servers start with keeping the toolset small, giving each tool a precise name and description, and minimizing the inputs and outputs the model has to handle. At Stainless, they also often add a JSON filter on top to strip out unnecessary data. • Make complex APIs manageable with dynamic mode. To solve the problem of how an AI figures out which tool to use in larger APIs, Stainless switches to “dynamic mode,” where the model gets only three tools: List the endpoints, pick one and learn about it, and then execute it. • MCP servers as business copilots. At Stainless, Alex uses MCP servers to connect tools like Notion and HubSpot, so he can ask questions like, “Which customers signed up last week?” The system queries multiple databases and returns a summary that would’ve otherwise taken multiple logins and searches. • Create a “brain” for your company with Claude Code. Alex built a shared company brain at Stainless by keeping Claude Code running on his system and asking it to save useful inputs—like customer feedback and SQL queries—into GitHub. Over time, this creates a curated archive his team can query easily. • The future of MCP is code execution. Instead of giving models hundreds of tools, Alex believes the most powerful setup will be a simple code execution tool and a doc search tool. The AI writes code against an API’s SDK, runs it on a server, and checks the docs when it gets stuck. This is a must-watch for anyone who wants to understand MCP—and learn how to use them as a competitive edge. Watch below! Timestamps: Introduction: 00:01:14 Why Alex likes running barefoot: 00:02:54 APIs and MCP, the connectors of the new internet: 00:05:09 Why MCP servers are hard to get right: 00:10:53 Design principles for reliable MCP servers: 00:20:07 Scaling MCP servers for large APIs: 00:23:50 Using MCP for business ops at Stainless: 00:25:14 Building a company brain with Claude Code: 00:28:12 Where MCP goes from here: 00:33:59 Alex’s take on the security model for MCP: 00:41:10

Dan Shipper 📧

15,645 views • 10 months ago

New course: MCP: Build Rich-Context AI Apps with Anthropic. Learn to build AI apps that access tools, data, and prompts using the Model Context Protocol in this short course, created in partnership with Anthropic Anthropic and taught by Elie Schoppik Elie Schoppik, its Head of Technical Education. Connecting AI applications to external systems that bring rich context to LLM-based applications has often meant writing custom integrations for each use case. MCP is an open protocol that standardizes how LLMs access tools, data, and prompts from external sources, and simplifies how you provide context to your LLM-based applications. For example, you can provide context via third-party tools that let your LLM make API calls to search the web, access data from local docs, retrieve code from a GitHub repo, and so on. MCP, developed by Anthropic, is based on a client-server architecture that defines the communication details between an MCP client, hosted inside the AI application, and an MCP server that exposes tools, resources, and prompt templates. The server can be a subprocess launched by the client that runs locally or an independent process running remotely. In this hands-on course, you'll learn the core architecture behind MCP. You’ll create an MCP-compatible chatbot, build and deploy an MCP server, and connect the chatbot to your MCP server and other open-source servers. Here’s what you’ll do: - Understand why MCP makes AI development less fragmented and standardizes connections between AI applications and external data sources - Learn the core components of the client-server architecture of MCP and the underlying communication mechanism - Build a chatbot with custom tools for searching academic papers, and transform it into an MCP-compatible application - Build a local MCP server that exposes tools, resources, and prompt templates using FastMCP, and test it using MCP Inspector - Create an MCP client inside your chatbot to dynamically connect to your server - Connect your chatbot to reference servers built by Anthropic’s MCP team, such as filesystem, which implements filesystem operations, and fetch, which extracts contents from the web as markdown - Configure Claude Desktop to connect to your server and others, and explore how it abstracts away the low-level logic of MCP clients - Deploy your MCP server remotely and test it with the Inspector or other MCP-compatible applications - Learn about the roadmap for future MCP development, such as multi-agent architecture, MCP registry API, server discovery, authorization, and authentication MCP is an exciting and important technology that lets you build rich-context AI applications that connect to a growing ecosystem of MCP servers, with minimal integration work. Please sign up here!

New course: MCP: Build Rich-Context AI Apps with Anthropic. Learn to build AI apps that access tools, data, and prompts using the Model Context Protocol in this short course, created in partnership with Anthropic Anthropic and taught by Elie Schoppik Elie Schoppik, its Head of Technical Education. Connecting AI applications to external systems that bring rich context to LLM-based applications has often meant writing custom integrations for each use case. MCP is an open protocol that standardizes how LLMs access tools, data, and prompts from external sources, and simplifies how you provide context to your LLM-based applications. For example, you can provide context via third-party tools that let your LLM make API calls to search the web, access data from local docs, retrieve code from a GitHub repo, and so on. MCP, developed by Anthropic, is based on a client-server architecture that defines the communication details between an MCP client, hosted inside the AI application, and an MCP server that exposes tools, resources, and prompt templates. The server can be a subprocess launched by the client that runs locally or an independent process running remotely. In this hands-on course, you'll learn the core architecture behind MCP. You’ll create an MCP-compatible chatbot, build and deploy an MCP server, and connect the chatbot to your MCP server and other open-source servers. Here’s what you’ll do: - Understand why MCP makes AI development less fragmented and standardizes connections between AI applications and external data sources - Learn the core components of the client-server architecture of MCP and the underlying communication mechanism - Build a chatbot with custom tools for searching academic papers, and transform it into an MCP-compatible application - Build a local MCP server that exposes tools, resources, and prompt templates using FastMCP, and test it using MCP Inspector - Create an MCP client inside your chatbot to dynamically connect to your server - Connect your chatbot to reference servers built by Anthropic’s MCP team, such as filesystem, which implements filesystem operations, and fetch, which extracts contents from the web as markdown - Configure Claude Desktop to connect to your server and others, and explore how it abstracts away the low-level logic of MCP clients - Deploy your MCP server remotely and test it with the Inspector or other MCP-compatible applications - Learn about the roadmap for future MCP development, such as multi-agent architecture, MCP registry API, server discovery, authorization, and authentication MCP is an exciting and important technology that lets you build rich-context AI applications that connect to a growing ecosystem of MCP servers, with minimal integration work. Please sign up here!

Andrew Ng

142,010 views • 1 year ago

You can connect your Supabase database via MCP server to Cursor! The Cursor agent can get the schema and any data from your database through the official Postgres MCP server! This helps Cursor understand your database better when it needs to modify it to add a new feature!

You can connect your Supabase database via MCP server to Cursor! The Cursor agent can get the schema and any data from your database through the official Postgres MCP server! This helps Cursor understand your database better when it needs to modify it to add a new feature!

Tyler Shukert

203,451 views • 1 year ago

this tweet misses the gold of executor! the whole point is you don't want CLI / scripts, you want API / MCP servers in this video i ask executor to configure itself and add an MCP server - it pops up a browser for me to OAuth through based on the MCP elicitation spec

this tweet misses the gold of executor! the whole point is you don't want CLI / scripts, you want API / MCP servers in this video i ask executor to configure itself and add an MCP server - it pops up a browser for me to OAuth through based on the MCP elicitation spec

Rhys

33,637 views • 4 months ago

X just made itself plug straight into AI tools with MCP servers. Your agents can now search and post on X directly. Not only read about it. Grok Build, Cursor, Claude, VS Code. All in. What you get: * X MCP; search posts, trends, bookmarks, even publish Articles * Docs MCP; API docs inside your workflow, no tab switching Setup is straightforward: * Go to create an X app * Enable OAuth 2.0; required for authentication * Add redirect URI; * Copy your CLIENT_ID and CLIENT_SECRET * Plug those into your MCP client or config * Run the setup commands; connect X MCP and Docs MCP * Log in once via browser; approve access * Verify; run grok mcp doctor xapi and grok mcp list Log in once. Done. Your workflow now includes X itself. X

X just made itself plug straight into AI tools with MCP servers. Your agents can now search and post on X directly. Not only read about it. Grok Build, Cursor, Claude, VS Code. All in. What you get: * X MCP; search posts, trends, bookmarks, even publish Articles * Docs MCP; API docs inside your workflow, no tab switching Setup is straightforward: * Go to create an X app * Enable OAuth 2.0; required for authentication * Add redirect URI; * Copy your CLIENT_ID and CLIENT_SECRET * Plug those into your MCP client or config * Run the setup commands; connect X MCP and Docs MCP * Log in once via browser; approve access * Verify; run grok mcp doctor xapi and grok mcp list Log in once. Done. Your workflow now includes X itself. X

Mario Nawfal

59,976 views • 27 days ago

MCP is mind-blowing. Here is a genius setup that will earn you a promotion with your manager. I have multiple data sources: data in S3, MySQL, and local files. Using Spice (an open-source project), I can co-locate all of that data behind a single SQL endpoint and augment it using MCP. Before, accessing data was slow, and I had to make multiple requests to get anything. After using Spice, I can query the data much faster (since it's mirrored locally), and I don't have to worry about where the data is coming from. Spice acts as an MCP server, so I can connect to it from my IDE or the Claude Desktop app and have access to all the data. But even more cool than that: Spice also acts as an MCP client, so it can connect to other MCP servers. This is where things get really interesting! Watch the video. I'm querying multiple data sources from my IDE and using the Google Maps MCP server for driving directions.

MCP is mind-blowing. Here is a genius setup that will earn you a promotion with your manager. I have multiple data sources: data in S3, MySQL, and local files. Using Spice (an open-source project), I can co-locate all of that data behind a single SQL endpoint and augment it using MCP. Before, accessing data was slow, and I had to make multiple requests to get anything. After using Spice, I can query the data much faster (since it's mirrored locally), and I don't have to worry about where the data is coming from. Spice acts as an MCP server, so I can connect to it from my IDE or the Claude Desktop app and have access to all the data. But even more cool than that: Spice also acts as an MCP client, so it can connect to other MCP servers. This is where things get really interesting! Watch the video. I'm querying multiple data sources from my IDE and using the Google Maps MCP server for driving directions.

Santiago

142,696 views • 1 year ago

This robot assistant from the NVIDIA CES Keynote on Monday is going viral. Nader Khalil🍊 explains all the hottest emerging AI trends in one demo: AI applications in 2026 will be multi-model, multi-modal, hybrid cloud/local, use open source models as well as proprietary models, control robots and embedded devices in the physical world, and have voice interfaces. (And the demo had a cute robot *and* a cute dog. Gold.) The demo was built with Pipecat AI. NVIDIA posted a really nice technical walk-through and complete code. The Reachy Mini robot from Hugging Face is open source hardware. (You can order it now, I have one!). You can run the assistant locally on your own hardware, in the cloud, or both.

This robot assistant from the NVIDIA CES Keynote on Monday is going viral. Nader Khalil🍊 explains all the hottest emerging AI trends in one demo: AI applications in 2026 will be multi-model, multi-modal, hybrid cloud/local, use open source models as well as proprietary models, control robots and embedded devices in the physical world, and have voice interfaces. (And the demo had a cute robot and a cute dog. Gold.) The demo was built with Pipecat AI. NVIDIA posted a really nice technical walk-through and complete code. The Reachy Mini robot from Hugging Face is open source hardware. (You can order it now, I have one!). You can run the assistant locally on your own hardware, in the cloud, or both.

kwindla

49,010 views • 6 months ago

Postman will conduct hands-on workshops where you will learn how to build agent-ready APIs 👉 Here's how to generate MCP servers in seconds from APIs using Postman. - Go to Postman MCP article: - Choose Create AI agents - Choose a Workspace or Collection and select your APIs. - Download and extract the zip file. - Open the file in VsCode or any other IDE. - Follow the Readme and make any necessary changes. - Finally Run Your MCP Server.

Postman will conduct hands-on workshops where you will learn how to build agent-ready APIs 👉 Here's how to generate MCP servers in seconds from APIs using Postman. - Go to Postman MCP article: - Choose Create AI agents - Choose a Workspace or Collection and select your APIs. - Download and extract the zip file. - Open the file in VsCode or any other IDE. - Follow the Readme and make any necessary changes. - Finally Run Your MCP Server.

Poonam Soni

44,320 views • 1 year ago

The Figma MCP is insanely good. First time I used it felt like AGI. Feed designs to the MCP, done. It reads frames, components, variables, layout, and generates close to pixel perfect code. I one-shotted my design in this 150 second video with Devin.

The Figma MCP is insanely good. First time I used it felt like AGI. Feed designs to the MCP, done. It reads frames, components, variables, layout, and generates close to pixel perfect code. I one-shotted my design in this 150 second video with Devin.

nader dabit

119,262 views • 5 months ago

Sharing the 4 Claude MCP servers I use the most lately. 1. TinyFish MCP lets Claude browse the live web, scrape, research, and return structured data instead of static answers. I’ve been using it to gather AI news for my newsletter, like pulling top Hacker News posts from the last few hours and summarizing them into a clean list. 2. GitHub MCP helps me review commits, trace changes, and understand repos without jumping between tools. 3. Figma MCP lets me inspect designs, check layout and spacing, and pull UI details directly into the conversation. 4. Excalidraw MCP is great for thinking visually. I use it to sketch flows and system ideas when text isn’t enough. The last few are probably familiar, but the first one is worth a look. I recorded a short video showing how it works in practice.

Sharing the 4 Claude MCP servers I use the most lately. 1. TinyFish MCP lets Claude browse the live web, scrape, research, and return structured data instead of static answers. I’ve been using it to gather AI news for my newsletter, like pulling top Hacker News posts from the last few hours and summarizing them into a clean list. 2. GitHub MCP helps me review commits, trace changes, and understand repos without jumping between tools. 3. Figma MCP lets me inspect designs, check layout and spacing, and pull UI details directly into the conversation. 4. Excalidraw MCP is great for thinking visually. I use it to sketch flows and system ideas when text isn’t enough. The last few are probably familiar, but the first one is worth a look. I recorded a short video showing how it works in practice.

Tw93

37,716 views • 4 months ago

The new Sonic-3 voice model from launched today. The big additions are increased emotional range, emotion steering, and laughter tags. For example: I wrote some quick demo code, prompting Gemini Flash to know about the emotion tags. You can hear the results in the video, and see the emotion tags in the Pipecat developer console. Code is below.

The new Sonic-3 voice model from launched today. The big additions are increased emotional range, emotion steering, and laughter tags. For example: I wrote some quick demo code, prompting Gemini Flash to know about the emotion tags. You can hear the results in the video, and see the emotion tags in the Pipecat developer console. Code is below.

kwindla

12,350 views • 9 months ago

This is why you want an execution layer share your tools, auth and approvals across all agents you use Check out me adding the Axiom MCP server, authing to it, and calling it from Claude Code and OpenCode in under a minute - all locally on my computer `npm i -g executor`

This is why you want an execution layer share your tools, auth and approvals across all agents you use Check out me adding the Axiom MCP server, authing to it, and calling it from Claude Code and OpenCode in under a minute - all locally on my computer `npm i -g executor`

Rhys

29,977 views • 4 months ago

Exploring Andrej Karpathy Nanochat through a Knowledge Graph Love how this project combines simplicity with power. Want to navigate and understand the entire repo? Check it out here: Plus, you can connect it via MCP to any AI coding assistant and work directly on the repository. Powered by Deep Graph MCP AI at Meta and Groq Inc

Exploring Andrej Karpathy Nanochat through a Knowledge Graph Love how this project combines simplicity with power. Want to navigate and understand the entire repo? Check it out here: Plus, you can connect it via MCP to any AI coding assistant and work directly on the repository. Powered by Deep Graph MCP AI at Meta and Groq Inc

Daniel San

126,642 views • 9 months ago