WEBVTT 00:01.720 --> 00:03.640 Hello everyone and welcome. 00:04.480 --> 00:08.440 In this video we will learn about MCP. 00:09.000 --> 00:11.040 That is model context protocol. 00:12.080 --> 00:16.120 This is the next evolution in the LM architecture. 00:17.840 --> 00:26.960 We will learn about MCP as an architecture, the communication patterns, server components, transport 00:27.000 --> 00:30.400 types and an entire end to end flow. 00:31.600 --> 00:38.920 Having said that, let's first understand key components in MCP. 00:40.520 --> 00:53.560 So here on the left hand side we have an image with AI application sitting at the core of the uh, different 00:54.200 --> 00:55.680 uh, communication patterns. 00:57.280 --> 01:01.520 The core AI system is a center of architecture. 01:02.400 --> 01:11.080 It communicates with databases, web UIs, and GitHub's as an external service. 01:13.600 --> 01:18.600 The important part here is the dotted line with MCP. 01:20.280 --> 01:31.480 It provides a standard protocol for communicating across different services, allowing Llms to discover, 01:31.520 --> 01:37.600 understand and utilize external capabilities consistently. 01:39.560 --> 01:46.480 So now let's understand the three key components from MCP. 01:49.920 --> 02:00.560 So the very first component is MCP client applications like windsurf or cursor. 02:01.280 --> 02:05.880 They all serve as an LLM facing side of the ecosystem. 02:07.600 --> 02:12.720 These handle the user interface and interactions. 02:14.200 --> 02:16.000 Then there is MCP protocol. 02:16.680 --> 02:19.960 This is the heart of the MCP. 02:20.560 --> 02:28.920 It's a standardized communication layer that enables two way connections between clients and servers. 02:30.000 --> 02:38.200 And then there is an MCP server, the component that translates external services and their capabilities 02:38.200 --> 02:41.240 into a format that client can understand. 02:43.560 --> 02:53.240 Now having introduced three main components of MCP server, let's understand how it all works together. 02:59.280 --> 03:01.480 So here is a complete architecture. 03:02.400 --> 03:11.640 The Model Context protocol creates a standardized ecosystem that enables LM to discover and utilize 03:11.640 --> 03:17.240 external capabilities consistently across different implementations. 03:18.560 --> 03:19.720 MCP client. 03:19.760 --> 03:26.800 On the left Communicates with the MCP server through MCP protocol. 03:27.440 --> 03:37.160 The server acts as a translator, converting the external service capabilities into standardized format 03:37.640 --> 03:40.240 that MCP client can work with. 03:41.840 --> 03:46.480 This is indeed a very strategic and brilliant move. 03:48.720 --> 03:49.160 Why? 03:50.400 --> 03:58.320 It's because now MCP server is responsible for providing the services. 03:59.440 --> 04:07.840 This eliminates the need for custom integrations between each LM and external services. 04:09.000 --> 04:21.360 It significantly reduces the complexity for scalability and managing the changes that a service provider 04:21.600 --> 04:22.680 would introduce. 04:25.160 --> 04:36.120 So what anthropic did is that they said, we want our lives to be more powerful and capable, but it's 04:36.120 --> 04:38.840 your job to figure out the integration. 04:40.040 --> 04:50.840 This shifts the entire service burden of building and maintaining integrations from AI companies to 04:50.880 --> 04:52.040 service providers. 04:53.880 --> 04:54.280 Now why? 04:54.280 --> 04:55.400 This is very smart. 04:56.240 --> 05:04.480 It's smart because service providers, they know their systems best, and they are the most capable 05:04.960 --> 05:11.760 of providing the integrations by making them responsible for MCP servers. 05:12.440 --> 05:20.840 Anthropic ensures that integrations stay current, functional, and without having to maintain hundreds 05:20.840 --> 05:23.080 of different API connections themselves. 05:24.880 --> 05:34.440 Having said that, let's understand how the communication works in terms of MCP architecture, and let's 05:34.440 --> 05:35.120 take a deep dive. 05:35.160 --> 05:35.520 There.