Loading video...

Video Failed to Load

Go Home

🔮 MCP INTEGRATION NOW LIVE ON OPENSERV This is bigger than most realize. We're not just adding a feature - we're enabling a fundamentally new paradigm for agent infrastructure. Before MCP: agents trapped in walled gardens, limited by what you explicitly feed them. After MCP: agents that can access...

openservai's profile picture

OpenServ

22,539 subscribers

34,665 views • 1 year ago •via X (Twitter)

News & PoliticsScience & Technology
LIVE

Anya Rossi• Live Now

Private livecam show

11 Comments

s4mmy's profile picture
s4mmy1 year ago

you guys ship fast! only just featured SERV this morning in this MCP roundup!

Nexus 👾's profile picture
Nexus 👾1 year ago

Tired of juggling tools? Nexus makes crypto simple. Get the CMC market view, track wallets, and stay updated on news—all in one free platform. Start today and see the difference! 🚀

Infinite Liquidity🔮's profile picture
Infinite Liquidity🔮1 year ago

The journey to the top begins now for $SERV 🔥

Oliwier's profile picture
Oliwier1 year ago

👀👀

GB's profile picture
GB1 year ago

Game changing

DJ Griffith's profile picture
DJ Griffith1 year ago

Huge

Skrzypeczek 🐍🧲's profile picture
Skrzypeczek 🐍🧲1 year ago

Can’t imagine how big it will be 🔥 go go $SERV😎

Kameroongod's profile picture
Kameroongod1 year ago

$SERV

CryptoCribz's profile picture
CryptoCribz1 year ago

And so it begins: the era of groundbreaking use of AI Agents has arrived. $SERV 🌎♟️

Semp's profile picture
Semp1 year ago

Sheesh

TokenSymphony's profile picture
TokenSymphony1 year ago

🤯🤯🤯

Related Videos

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:
1:48

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 • 11 months ago

Portkey's MCP Gateway is now GA. MCP has truly exploded. Trillions of tokens flow through our infra every month. Agents can finally do things: hit databases, trigger workflows, access internal systems. But auth is fragmented. There's no access control. And once multiple agents are involved, it's impossible to know what can access what. Today we're fixing that. One line to connect any MCP server. Centralized authentication. Fine-grained access control by team, by tool, by action. Full observability on every tool call. Platform teams can finally say yes to agents without losing sleep. Already live with Fortune 50.
0:59

Portkey's MCP Gateway is now GA. MCP has truly exploded. Trillions of tokens flow through our infra every month. Agents can finally do things: hit databases, trigger workflows, access internal systems. But auth is fragmented. There's no access control. And once multiple agents are involved, it's impossible to know what can access what. Today we're fixing that. One line to connect any MCP server. Centralized authentication. Fine-grained access control by team, by tool, by action. Full observability on every tool call. Platform teams can finally say yes to agents without losing sleep. Already live with Fortune 50.

Rohit Agarwal

175,553 views • 7 months ago

Support for Agent Plugins is live in Cursor (and I made a plugin for searching X!) Agent Plugins combine Skills and MCP servers into a single package Think about them like an Ikea furniture kit: your table comes with instructions, parts, and tools. You use the instructions to understand how things work (which tools on which parts), then use the tools to assemble your furniture Agent Plugins are bundles of tools & resources that allow agents to accomplish a goal: - MCP servers: fixed context and tools - Skills: dynamic instructions, loaded progressively Plugins bundle tools and instructions so your agent is able to use tokens efficiently Many of us already use MCP servers and skills together - Agent Plugins formalize this pattern for more powerful workflows I'm excited to see where the standard takes us!
0:24

Support for Agent Plugins is live in Cursor (and I made a plugin for searching X!) Agent Plugins combine Skills and MCP servers into a single package Think about them like an Ikea furniture kit: your table comes with instructions, parts, and tools. You use the instructions to understand how things work (which tools on which parts), then use the tools to assemble your furniture Agent Plugins are bundles of tools & resources that allow agents to accomplish a goal: - MCP servers: fixed context and tools - Skills: dynamic instructions, loaded progressively Plugins bundle tools and instructions so your agent is able to use tokens efficiently Many of us already use MCP servers and skills together - Agent Plugins formalize this pattern for more powerful workflows I'm excited to see where the standard takes us!

matt palmer

39,554 views • 15 days ago

This is Repo Prompt 2.0 A fully integrated agent, that makes it seamless to use RP's powerful MCP tools, with a built-in oracle and context builder. A first class experience showcasing how much better and efficient your agents can be with good context engineering tools.
4:35

This is Repo Prompt 2.0 A fully integrated agent, that makes it seamless to use RP's powerful MCP tools, with a built-in oracle and context builder. A first class experience showcasing how much better and efficient your agents can be with good context engineering tools.

eric provencher

38,921 views • 5 months ago

wtf is MCP? Paul Klein IV, CEO of explains "Model Context Protocol" (MCP) in plain terms: "There's this new way that people are exposing tools to AI & the 'Model Context Protocol' is one of those ways that you can standardize & give your AI a set of tools to call. BrowserBase has a way to expose the browser to your agent via MCP or MCP server. More & more developers are trying to find ways to integrate more functionalities to their AI agents & BrowserBase's browsers are one of those primitive functionalities, & the MCP is just one way to integrate it into your software." Paul Klein IV From 🅱️'s GitHub: Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you’re building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need. This server provides cloud browser automation capabilities using Browserbase and Stagehand. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a cloud browser environment.
0:40

wtf is MCP? Paul Klein IV, CEO of explains "Model Context Protocol" (MCP) in plain terms: "There's this new way that people are exposing tools to AI & the 'Model Context Protocol' is one of those ways that you can standardize & give your AI a set of tools to call. BrowserBase has a way to expose the browser to your agent via MCP or MCP server. More & more developers are trying to find ways to integrate more functionalities to their AI agents & BrowserBase's browsers are one of those primitive functionalities, & the MCP is just one way to integrate it into your software." Paul Klein IV From 🅱️'s GitHub: Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you’re building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need. This server provides cloud browser automation capabilities using Browserbase and Stagehand. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a cloud browser environment.

Molly O’Shea

20,408 views • 1 year 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!
2:43

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,137 views • 1 year ago

🇸🇦🇺🇸 DAVID SACKS: MCP IS THE NEXT BIG WAVE IN AI "MCP {Model Context Protocol} is a new standard that allows agents to talk to existing SaaS applications or any kind of application, and it's really going to enable this agentic future that I think is the next big wave in AI." Source: David Sacks
0:56

🇸🇦🇺🇸 DAVID SACKS: MCP IS THE NEXT BIG WAVE IN AI "MCP {Model Context Protocol} is a new standard that allows agents to talk to existing SaaS applications or any kind of application, and it's really going to enable this agentic future that I think is the next big wave in AI." Source: David Sacks

Mario Nawfal

123,179 views • 1 year ago

Anthropic engineer just dropped a full walkthrough on building AI agents from scratch this single video is worth more than any $600 AI agents course here's what she covers: > what Agent, Environment, and Session actually mean > how to stream live events from your agent > wiring up custom tools from scratch > the server-side loop that makes agents actually work > roadmap to subagents, vaults, and memory 37 minutes that will answer every question you have about building agents the people who understand what Claude can actually do are building things everyone else thinks requires a whole team most of them aren't smarter, they just know features that most people have never heard of full breakdown on every Claude feature worth knowing in the article below
36:49

Anthropic engineer just dropped a full walkthrough on building AI agents from scratch this single video is worth more than any $600 AI agents course here's what she covers: > what Agent, Environment, and Session actually mean > how to stream live events from your agent > wiring up custom tools from scratch > the server-side loop that makes agents actually work > roadmap to subagents, vaults, and memory 37 minutes that will answer every question you have about building agents the people who understand what Claude can actually do are building things everyone else thinks requires a whole team most of them aren't smarter, they just know features that most people have never heard of full breakdown on every Claude feature worth knowing in the article below

Anatoli Kopadze

39,157 views • 2 months ago

Today we are launching Mireye (YCS26) with Y Combinator The easiest way to build agentic applications for the physical world. AI agents are starting to act in the real world, but they can't reliably understand it. Mireye is one API and MCP that connects agents to the physical world: data, enrichment, tools, and signals that power them to make decisions. One line of code to make your agents street smart.
1:47

Today we are launching Mireye (YCS26) with Y Combinator The easiest way to build agentic applications for the physical world. AI agents are starting to act in the real world, but they can't reliably understand it. Mireye is one API and MCP that connects agents to the physical world: data, enrichment, tools, and signals that power them to make decisions. One line of code to make your agents street smart.

Ansh

29,202 views • 21 days ago

Agent-in-the-browser unlocks superpowers. The magic really shines when you bring your own model, system prompts, and MCP tools into the mix. Hence, AgentBoard 🪄. Your models, keys, and settings. Integration with remote MCP servers and — this is where it gets really fun — ability to register and allow the agent to call custom ~WebMCP tools that execute in context of the page. Chrome Web Store: Code:
3:51

Agent-in-the-browser unlocks superpowers. The magic really shines when you bring your own model, system prompts, and MCP tools into the mix. Hence, AgentBoard 🪄. Your models, keys, and settings. Integration with remote MCP servers and — this is where it gets really fun — ability to register and allow the agent to call custom ~WebMCP tools that execute in context of the page. Chrome Web Store: Code:

Ilya Grigorik

22,961 views • 10 months ago

Today we're launching Amplitude MCP MCP was made for data analytics. Ask a vague question and have an AI model iteratively query Amplitude to find you insights. Amplitude MCP exposes all of Amplitude's functionality so an agent can interact with it directly. It allows you to use Amplitude without having to know anything about Amplitude's user interface or your data taxonomy. It uses the intelligence of off the shelf AI agents, including Claude, Gemini, and Cursor, to query Amplitude data you already have to find answers. It leverages all of your existing Amplitude data and how it's used to navigate through large complex behavioral datasets. You can have conversations about your product data directly inside any AI model with MCP. It can create Amplitude dashboards and notebooks with what it finds and even make recommendations. This is the best MCP use case I've ever seen. Watching an AI agent think, reason, query Amplitude, and then repeat that process iteratively is magical. See it in action:
3:08

Today we're launching Amplitude MCP MCP was made for data analytics. Ask a vague question and have an AI model iteratively query Amplitude to find you insights. Amplitude MCP exposes all of Amplitude's functionality so an agent can interact with it directly. It allows you to use Amplitude without having to know anything about Amplitude's user interface or your data taxonomy. It uses the intelligence of off the shelf AI agents, including Claude, Gemini, and Cursor, to query Amplitude data you already have to find answers. It leverages all of your existing Amplitude data and how it's used to navigate through large complex behavioral datasets. You can have conversations about your product data directly inside any AI model with MCP. It can create Amplitude dashboards and notebooks with what it finds and even make recommendations. This is the best MCP use case I've ever seen. Watching an AI agent think, reason, query Amplitude, and then repeat that process iteratively is magical. See it in action:

Spenser Skates

32,332 views • 10 months ago

Today, we're supporting MCP in Flowise! There has been a lot of discussion about MCP lately. From our perspective, MCP is nothing fancy - just tools with third-party APIs or functions, wrapped under a unified protocol that can be consumed by client LLM applications. In fact, we've had something similar for a long time with Langchain Tools. However, MCP offers two key benefits: - Its open protocol isn’t limited to specific frameworks - Client applications (like us, Cursor , @windsurf , etc) can offload the burden of maintaining and updating these tools to the official MCP creators These MCP servers (a.k.a. tools) are provided to the LLM, allowing it to decide when and how to use them. This is sometimes referred to as an "agentic" approach, as opposed to a "deterministic" approach like Zapier, where each step must be explicitly mapped out. In real-world scenarios, you might find yourself needing both approaches depending on the use case. It's still early days, and it will take time for the community to establish standards. We're excited to see where this goes!
0:46

Today, we're supporting MCP in Flowise! There has been a lot of discussion about MCP lately. From our perspective, MCP is nothing fancy - just tools with third-party APIs or functions, wrapped under a unified protocol that can be consumed by client LLM applications. In fact, we've had something similar for a long time with Langchain Tools. However, MCP offers two key benefits: - Its open protocol isn’t limited to specific frameworks - Client applications (like us, Cursor , @windsurf , etc) can offload the burden of maintaining and updating these tools to the official MCP creators These MCP servers (a.k.a. tools) are provided to the LLM, allowing it to decide when and how to use them. This is sometimes referred to as an "agentic" approach, as opposed to a "deterministic" approach like Zapier, where each step must be explicitly mapped out. In real-world scenarios, you might find yourself needing both approaches depending on the use case. It's still early days, and it will take time for the community to establish standards. We're excited to see where this goes!

FlowiseAI

27,360 views • 1 year ago

A builder wants to ship an agent that can search live data, use it instantly, and keep going without manual steps. That is why OptimAI Search now ships with x402, SDK, and MCP support. x402 makes access and payment seamless. SDK and MCP make integration straightforward for builders. And under the hood, OptimAI Search gives agents real-time access to huge volumes of public and social web data, structured into context they can actually use. Add Agent Marketplace on top, and domain knowledge becomes reusable: build specialized agents, publish them, and let others build on what you create. This is what search looks like in the agent-native internet. 💡Try it:
1:07

A builder wants to ship an agent that can search live data, use it instantly, and keep going without manual steps. That is why OptimAI Search now ships with x402, SDK, and MCP support. x402 makes access and payment seamless. SDK and MCP make integration straightforward for builders. And under the hood, OptimAI Search gives agents real-time access to huge volumes of public and social web data, structured into context they can actually use. Add Agent Marketplace on top, and domain knowledge becomes reusable: build specialized agents, publish them, and let others build on what you create. This is what search looks like in the agent-native internet. 💡Try it:

OptimAI Network

36,512 views • 3 months ago

I'm still picking my jaw off the floor with this MCP update: Postman will now automatically build an MCP server for an API. Automatically! You select your API and the requests you want to include, and Potman will generate a Zip file with everything you need. In collaboration with Postman, I recorded a video showing how I generated an MCP server for the Google Maps API. It's glorious! Also, and before I forget: You can now test any MCP server with your Postman application. They built MCP right in, so now you can: • Connect to an MCP server • List out all of the available tools • Test any of the tools This is a 10x boost for the MCP ecosystem. If you've tried the default MCP debugger, you'll understand how huge a deal it is that you can do all of that from Postman now. Go here to give this a try:
6:15

I'm still picking my jaw off the floor with this MCP update: Postman will now automatically build an MCP server for an API. Automatically! You select your API and the requests you want to include, and Potman will generate a Zip file with everything you need. In collaboration with Postman, I recorded a video showing how I generated an MCP server for the Google Maps API. It's glorious! Also, and before I forget: You can now test any MCP server with your Postman application. They built MCP right in, so now you can: • Connect to an MCP server • List out all of the available tools • Test any of the tools This is a 10x boost for the MCP ecosystem. If you've tried the default MCP debugger, you'll understand how huge a deal it is that you can do all of that from Postman now. Go here to give this a try:

Santiago

215,882 views • 1 year ago

$FET just quietly built the internet for AI agents. 3,000,000 agents. One network. One token. Here's what nobody is explaining: Every AI agent needs 3 things to be useful: An address. A way to be found. A way to get paid. Agentverse gives agents all three. Your agent becomes discoverable on ASI: One. Other agents can find it, call it, or hire it. Automatically. No human in the loop. This is agent-to-agent commerce. And every transaction settles in $FET. More agents = more activity = more demand. The infrastructure is already live. The economy is just getting started.
1:00

$FET just quietly built the internet for AI agents. 3,000,000 agents. One network. One token. Here's what nobody is explaining: Every AI agent needs 3 things to be useful: An address. A way to be found. A way to get paid. Agentverse gives agents all three. Your agent becomes discoverable on ASI: One. Other agents can find it, call it, or hire it. Automatically. No human in the loop. This is agent-to-agent commerce. And every transaction settles in $FET. More agents = more activity = more demand. The infrastructure is already live. The economy is just getting started.

2xnmore

12,894 views • 4 months ago

Here is a step-by-step introduction to building a workflow with a custom AI agent that uses MCP. I explain every component in the video: 1. Building the MCP server 2. Building the agent and an MCP client 3. Building a workflow that uses the agent The goal is simple: Generate a dialogue between two people and make one yell and the other answer with sarcasm. Kestra is sponsoring this video. They are an open-source orchestration platform (repo link below), and I used them to build the workflow that connects every component.
23:07

Here is a step-by-step introduction to building a workflow with a custom AI agent that uses MCP. I explain every component in the video: 1. Building the MCP server 2. Building the agent and an MCP client 3. Building a workflow that uses the agent The goal is simple: Generate a dialogue between two people and make one yell and the other answer with sarcasm. Kestra is sponsoring this video. They are an open-source orchestration platform (repo link below), and I used them to build the workflow that connects every component.

Santiago

51,527 views • 1 year ago

The MCP finally has proper authentication! It now supports OAuth 2.1 out of the box. That means proper authentication for AI agents and MCP tools is finally standardized. No more hacked-together API keys or custom token logic. With OAuth 2.1 + MCP, you can now: - Dynamically register clients - Issue & verify scoped JWT tokens - Track which agent acted for which user - Plug into existing IdPs (Auth0, Clerk, Firebase, etc.) I’ve been testing it with Scalekit, a lightweight OAuth layer built for MCP servers. It adds full discovery, token flow, and audit logs with minimal config. This is the missing piece for secure, multi-agent systems. Auth that actually works.
1:19

The MCP finally has proper authentication! It now supports OAuth 2.1 out of the box. That means proper authentication for AI agents and MCP tools is finally standardized. No more hacked-together API keys or custom token logic. With OAuth 2.1 + MCP, you can now: - Dynamically register clients - Issue & verify scoped JWT tokens - Track which agent acted for which user - Plug into existing IdPs (Auth0, Clerk, Firebase, etc.) I’ve been testing it with Scalekit, a lightweight OAuth layer built for MCP servers. It adds full discovery, token flow, and audit logs with minimal config. This is the missing piece for secure, multi-agent systems. Auth that actually works.

Arindam Majumder 𝕏

11,525 views • 10 months ago

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.
30:12

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.

Himanshu Kumar

228,497 views • 3 months ago

This is probably the biggest news yet in software going headless, and will bring knowledge work agents to the masses. The new ChatGPT agents have access to any of the tools and data you want to work with, with complete coding and tool use available to them. Here's an example of a custom sales assistant agent uses Box as a knowledge source for accessing enterprise content securely to answer questions and generate new content on the fly. The workflows can obviously vastly far more complex as the agent can use any of the tools within Box available via MCP and CLI. This precisely what agents will start to look like for knowledge work. You'll be able to spin them up in the foreground or background to help augment work. Big opportunity right now for headless platforms, and for all the new builders and designers of these agents in the enterprise.
1:06

This is probably the biggest news yet in software going headless, and will bring knowledge work agents to the masses. The new ChatGPT agents have access to any of the tools and data you want to work with, with complete coding and tool use available to them. Here's an example of a custom sales assistant agent uses Box as a knowledge source for accessing enterprise content securely to answer questions and generate new content on the fly. The workflows can obviously vastly far more complex as the agent can use any of the tools within Box available via MCP and CLI. This precisely what agents will start to look like for knowledge work. You'll be able to spin them up in the foreground or background to help augment work. Big opportunity right now for headless platforms, and for all the new builders and designers of these agents in the enterprise.

Aaron Levie

420,133 views • 4 months ago

In case you missed it, earlier this week we launched "MCP: Build Rich-Context AI Apps with Anthropic." Enroll now and: ✅ Explore how MCP standardizes access to tools and data for AI applications, its underlying architecture, and how it simplifies the integration of new tools and connections to external systems (e.g., GitHub repos, Google Docs, local files). ✅ Build and deploy an MCP server that provides tools, resources, and prompts, and add it to the configuration of AI applications, such as Claude Desktop, to extend them. ✅ Build an MCP-compatible application that hosts multiple MCP clients, each maintaining 1-to-1 connection to an MCP server. Join in for free:
1:09

In case you missed it, earlier this week we launched "MCP: Build Rich-Context AI Apps with Anthropic." Enroll now and: ✅ Explore how MCP standardizes access to tools and data for AI applications, its underlying architecture, and how it simplifies the integration of new tools and connections to external systems (e.g., GitHub repos, Google Docs, local files). ✅ Build and deploy an MCP server that provides tools, resources, and prompts, and add it to the configuration of AI applications, such as Claude Desktop, to extend them. ✅ Build an MCP-compatible application that hosts multiple MCP clients, each maintaining 1-to-1 connection to an MCP server. Join in for free:

DeepLearning.AI

23,829 views • 1 year ago