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.

MCP sucking is a harness problem, not an MCP problem MCP unlocks behavior that is fundamentally impossible to get via CLI or APIs Bad auth, too much context usage, all get solved with an execution layer - your agent writes code to progressively discover and call tools

Rhys

58,916 subscribers

376,723 views • 5 months ago •via X (Twitter)

Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Executor v1.2.1 is now out, with full Google Discover API support Google Workspace, Search Console, and 70+ other Google APIs all supported Connects to any agent via MCP, only adds 1k tokens to context thanks to code mode, keeps you in the loop through MCP elicitation

Executor v1.2.1 is now out, with full Google Discover API support Google Workspace, Search Console, and 70+ other Google APIs all supported Connects to any agent via MCP, only adds 1k tokens to context thanks to code mode, keeps you in the loop through MCP elicitation

Rhys

32,970 views • 5 months ago

How to connect Agent Wallet to your AI agent. → MCP: add our MCP server to Claude, sign in with District Pass. → CLI: install the fdx CLI, sign up or log in via email OTP, run in Claude Code. Now your AI agent doesn't just talk. It pays, swaps, and earns. Get Started →

How to connect Agent Wallet to your AI agent. → MCP: add our MCP server to Claude, sign in with District Pass. → CLI: install the fdx CLI, sign up or log in via email OTP, run in Claude Code. Now your AI agent doesn't just talk. It pays, swaps, and earns. Get Started →

Finance District

18,268 views • 2 months ago

Make Claude Code 10x more powerful! Code Context is an MCP plugin that brings semantic code search to Claude Code, Gemini CLI, or any AI coding agent. Full codebase indexing means richer context and better code generation. 100% open-source.

Make Claude Code 10x more powerful! Code Context is an MCP plugin that brings semantic code search to Claude Code, Gemini CLI, or any AI coding agent. Full codebase indexing means richer context and better code generation. 100% open-source.

Akshay 🚀

137,038 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!

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

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:

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

The exchange layer for AI agents is here. Agent Trade Kit gives developers 80+ tools via MCP or CLI to build, test, and deploy directly on OKX Exchange. From market data to trade execution, it taps into the full OKX product suite.

The exchange layer for AI agents is here. Agent Trade Kit gives developers 80+ tools via MCP or CLI to build, test, and deploy directly on OKX Exchange. From market data to trade execution, it taps into the full OKX product suite.

OKX

32,477 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.

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

A Crash Course on Building AI Agents! Here's what it covers: - What is an AI agent - Connecting agents to tools - Overview of MCP - Replacing tools with MCP servers - Setting up observability and tracing All with 100% open-source tools!

A Crash Course on Building AI Agents! Here's what it covers: - What is an AI agent - Connecting agents to tools - Overview of MCP - Replacing tools with MCP servers - Setting up observability and tracing All with 100% open-source tools!

Akshay 🚀

115,943 views • 1 year 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

30,013 views • 5 months ago

Internet Identity is getting an MCP server. We sat down with Arshavir Ter-Gabrielyan to understand what it is and why it matters. He starts with the problem: an AI agent runs in a cloud sandbox. No access to your device. No safe way to hold your keys. The MCP server is the answer. Keys stay in a trusted execution environment, and the agent asks permission to act in each app. Full conversation below.

Internet Identity is getting an MCP server. We sat down with Arshavir Ter-Gabrielyan to understand what it is and why it matters. He starts with the problem: an AI agent runs in a cloud sandbox. No access to your device. No safe way to hold your keys. The MCP server is the answer. Keys stay in a trusted execution environment, and the agent asks permission to act in each app. Full conversation below.

DFINITY Foundation

32,109 views • 1 month ago

who needs an MCP when you can just let your agent call the API get your agent connected to google search console with

who needs an MCP when you can just let your agent call the API get your agent connected to google search console with

Rhys

93,542 views • 1 month ago

Move over, Playwright? Meet MCP-Chrome by Hangwin — an open-source AI agent tool that can fully control your Chrome browser: cross-tab context, session auth, history & more. In this video, AJ @ Augment Code: - Sets up MCP-Chrome & connects it to Auggie CLI - Gives the agent a multi-step task across Reddit & X - Generates a full report in a web app Perfect for automated testing, research & dev workflows. What’s your favorite underrated MCP tool right now?

Move over, Playwright? Meet MCP-Chrome by Hangwin — an open-source AI agent tool that can fully control your Chrome browser: cross-tab context, session auth, history & more. In this video, AJ @ Augment Code: - Sets up MCP-Chrome & connects it to Auggie CLI - Gives the agent a multi-step task across Reddit & X - Generates a full report in a web app Perfect for automated testing, research & dev workflows. What’s your favorite underrated MCP tool right now?

Augment Code

49,325 views • 1 year 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 • 1 month 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!

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 • 12 days ago

🔮 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 10K+ tools, interact with your existing systems, and truly operate in your digital world. Think about this: -Every integration used to require custom code -Every data source needed specific formatting -Every agent had to be built for specific tools MCP eliminates all of that. One standard to connect any agent to any tool. This isn't just convenience - it's the unlock that makes agents actually useful in the real world. OpenServ + MCP = AI teams that can genuinely get things done, not just talk about doing them. This is the breakthrough that turns agents from toys into tools.

🔮 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 10K+ tools, interact with your existing systems, and truly operate in your digital world. Think about this: -Every integration used to require custom code -Every data source needed specific formatting -Every agent had to be built for specific tools MCP eliminates all of that. One standard to connect any agent to any tool. This isn't just convenience - it's the unlock that makes agents actually useful in the real world. OpenServ + MCP = AI teams that can genuinely get things done, not just talk about doing them. This is the breakthrough that turns agents from toys into tools.

OpenServ

34,665 views • 1 year ago

.General Analysis' MCP Guard is the first runtime firewall designed to secure every MCP tool call against prompt injection attacks. It's a free, open-source tool designed to validate, restrict, and log every MCP tool call. MCP Guard sits between your agents and MCP servers, screening all inputs and outputs, blocking known jailbreak patterns and obfuscated payloads before execution.

.General Analysis' MCP Guard is the first runtime firewall designed to secure every MCP tool call against prompt injection attacks. It's a free, open-source tool designed to validate, restrict, and log every MCP tool call. MCP Guard sits between your agents and MCP servers, screening all inputs and outputs, blocking known jailbreak patterns and obfuscated payloads before execution.

Y Combinator

16,730 views • 1 year 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.

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

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