WEBVTT 00:00:00.000 --> 00:00:01.560 You know, if you look back at tech history, it's 00:00:01.560 --> 00:00:04.820 often a story of tangled cables. For decades, 00:00:05.019 --> 00:00:07.360 the back of a PC, it was just a nightmare, right? 00:00:07.620 --> 00:00:10.800 Serial ports, parallel PS2, every single device 00:00:10.800 --> 00:00:13.580 needed its own special plug, its own driver. 00:00:13.919 --> 00:00:16.219 And that system, well, it just didn't scale. 00:00:16.320 --> 00:00:18.239 Then USB came along, the universal standard, 00:00:18.440 --> 00:00:20.379 and it fixed that chaos. Suddenly, there was 00:00:20.379 --> 00:00:23.350 one common plug that just worked. Unified hardware 00:00:23.350 --> 00:00:26.429 integration, like overnight. Now, AI is kind 00:00:26.429 --> 00:00:28.449 of hitting that same wall, that integration wall. 00:00:28.530 --> 00:00:30.530 To connect to the real world, it really needs 00:00:30.530 --> 00:00:33.049 a universal standard. And the Model Context Protocol, 00:00:33.329 --> 00:00:36.810 MCP, it's really emerging as that USB moment 00:00:36.810 --> 00:00:40.740 for AI. Welcome to the Deep Dive. Yeah, so today 00:00:40.740 --> 00:00:43.240 a listener shared this fantastic guide on MCP 00:00:43.240 --> 00:00:45.420 and their mission, well, it's crystal clear. 00:00:45.539 --> 00:00:47.619 They need to get why this protocol is being talked 00:00:47.619 --> 00:00:50.259 about as like the single most important infrastructure 00:00:50.259 --> 00:00:52.780 shift since ChachiPT first landed. That's big. 00:00:52.920 --> 00:00:54.380 Right, and here's where it gets really interesting. 00:00:54.479 --> 00:00:56.359 We're going to quickly define what MCP actually 00:00:56.359 --> 00:01:00.280 is. And we'll break down its pretty simple but 00:01:00.280 --> 00:01:02.079 really crucial architecture with the developers 00:01:02.079 --> 00:01:05.280 called HCS. And then we'll dig into the real 00:01:05.280 --> 00:01:07.819 power. These three capabilities baked inside 00:01:07.819 --> 00:01:10.079 every server. We'll use TRP to remember them. 00:01:10.180 --> 00:01:12.599 Exactly. We're basically charting the path from, 00:01:12.620 --> 00:01:15.959 you know, total integration chaos to genuine 00:01:15.959 --> 00:01:18.819 plug -and -play AI capability. It's all about 00:01:18.819 --> 00:01:22.200 connecting AI smoothly to the actual messy real 00:01:22.200 --> 00:01:25.140 world of data and tools, but in a standardized 00:01:25.140 --> 00:01:27.519 way. Let's dive in. Okay, so think about before 00:01:27.519 --> 00:01:30.780 this standard. Segment one. What is MCP? If you 00:01:30.780 --> 00:01:33.680 wanted your AI agent to talk to something outside 00:01:33.680 --> 00:01:35.540 itself, like booking a flight or maybe updating 00:01:35.540 --> 00:01:37.560 a database, check your calendar. You had to build 00:01:37.560 --> 00:01:40.040 a totally custom integration for every single 00:01:40.040 --> 00:01:41.900 tool. Oh, yeah. And that custom code, it was 00:01:41.900 --> 00:01:45.579 slow. It was complex. And critically, every time 00:01:45.579 --> 00:01:48.180 that external tool updated its API, its connection 00:01:48.180 --> 00:01:51.120 points, your integration broke. It was just completely 00:01:51.120 --> 00:01:53.019 unsustainable, especially for an ecosystem moving 00:01:53.019 --> 00:01:56.060 this fast. That's the exact pain point MCP tackles. 00:01:56.140 --> 00:01:59.299 It steps in as this open standard. Anthropic 00:01:59.299 --> 00:02:02.040 created it, open sourced it. The formal goal, 00:02:02.200 --> 00:02:05.099 if you read the spec, is enabling secure two 00:02:05.099 --> 00:02:07.780 -way connections between any data source and 00:02:07.780 --> 00:02:11.180 any AI power tool. Fundamentally, it's a common 00:02:11.180 --> 00:02:13.659 language for AIs and tools to talk to each other. 00:02:14.110 --> 00:02:16.629 So the analogy holds up. If USB got rid of those 00:02:16.629 --> 00:02:19.710 clunky old PS2 ports, MCP is getting rid of the 00:02:19.710 --> 00:02:22.009 chaos of dealing with every tool's completely 00:02:22.009 --> 00:02:24.969 unique API. You stop worrying about custom authentication, 00:02:25.370 --> 00:02:28.590 weird data formats, or the specific command structure 00:02:28.590 --> 00:02:31.030 you have to use for that one tool. And standardization 00:02:31.030 --> 00:02:33.330 brings instant scalability. This is really the 00:02:33.330 --> 00:02:35.949 key insight here. Developers now write an MCP 00:02:35.949 --> 00:02:39.090 server once for a tool. Let's say it's a specialized 00:02:39.090 --> 00:02:41.509 sales CRM, right? And then any compatible AI 00:02:41.509 --> 00:02:43.759 application out there can just use it. Instantly. 00:02:43.819 --> 00:02:45.840 Yeah. And that shift in thinking, it's already 00:02:45.840 --> 00:02:47.960 shown huge results. Within just a few months 00:02:47.960 --> 00:02:50.039 of MCP going public, the community built and 00:02:50.039 --> 00:02:53.759 shared over 20 ,000 pre -built MCP servers. 20 00:02:53.759 --> 00:02:56.379 ,000. That's explosive growth. It's the classic 00:02:56.379 --> 00:02:58.300 network effect, right? Once you have the standard, 00:02:58.379 --> 00:03:01.139 it just unlocks innovation because the complexity 00:03:01.139 --> 00:03:03.500 of writing all those custom APIs just vanishes. 00:03:03.500 --> 00:03:06.120 Right. That was the main barrier before. Just 00:03:06.120 --> 00:03:08.340 the sheer time and cost of custom integration 00:03:08.340 --> 00:03:10.879 for every little thing. So what was that main 00:03:10.879 --> 00:03:14.819 pain point before MCP really standardized AI 00:03:14.819 --> 00:03:19.819 integration? Simply put, the time. the cost and 00:03:19.819 --> 00:03:22.219 the headache of writing custom code for every 00:03:22.219 --> 00:03:25.659 single external tools api okay segment two actually 00:03:25.659 --> 00:03:27.699 using these mcp servers which you said is the 00:03:27.699 --> 00:03:29.620 easy part yeah this is where it gets really nice 00:03:29.620 --> 00:03:32.500 for the user or the developer using it the beauty 00:03:32.500 --> 00:03:35.500 is just the simplicity it's plug and play leveraging 00:03:35.500 --> 00:03:38.180 servers that already exist takes almost no technical 00:03:38.180 --> 00:03:40.520 effort on your part And these marketplaces for 00:03:40.520 --> 00:03:42.639 servers are already pretty big, covering everything 00:03:42.639 --> 00:03:45.039 from like real -time financial data, AlphaVantage 00:03:45.039 --> 00:03:47.180 is a popular one, to productivity tools like 00:03:47.180 --> 00:03:49.879 Google Workspace, Notion, and even developer 00:03:49.879 --> 00:03:52.520 platforms like GitHub or connecting to databases 00:03:52.520 --> 00:03:54.939 like PostgreSQL. Yeah, tons of options. Okay, 00:03:54.979 --> 00:03:56.919 let's walk through an example. Say you want your 00:03:56.919 --> 00:03:59.840 AI assistant to pull historical stock market 00:03:59.840 --> 00:04:03.000 data, and you want to use that pre -built AlphaVantage 00:04:03.000 --> 00:04:05.560 MCP server. Right, so you don't need to write 00:04:05.560 --> 00:04:08.539 code. First step, you just find the server in 00:04:08.539 --> 00:04:11.120 a directory or marketplace. It's usually listed 00:04:11.120 --> 00:04:13.180 with a configuration snippet, which is basically 00:04:13.180 --> 00:04:15.819 just a URL, a web address pointing to that capability. 00:04:16.139 --> 00:04:18.939 Okay, so I find the URL. Yeah. Then what? You 00:04:18.939 --> 00:04:21.660 take that snippet, copy it. And you paste it 00:04:21.660 --> 00:04:24.180 into your AI applications developer config file. 00:04:24.279 --> 00:04:26.180 Maybe that's in cloud desktop or, you know, a 00:04:26.180 --> 00:04:28.199 custom app you're building. Paste it in. Got 00:04:28.199 --> 00:04:29.839 it. And that's pretty much it. You then just 00:04:29.839 --> 00:04:32.759 prompt the AI like normal. You might say, plot 00:04:32.759 --> 00:04:35.100 the coffee stock market prices for the past 10 00:04:35.100 --> 00:04:39.620 years. And the AI using the MCP client handles 00:04:39.620 --> 00:04:41.639 the rest of the authorization talk, sending the 00:04:41.639 --> 00:04:44.000 request, getting the data back. You didn't write 00:04:44.000 --> 00:04:46.459 a line of code for the connection itself. Wow. 00:04:46.579 --> 00:04:48.740 That's a zero code setup. That feels transformative. 00:04:49.079 --> 00:04:50.860 And I didn't even need. to go sign up for an 00:04:50.860 --> 00:04:53.980 AlphaVantage API key myself or read their docs. 00:04:54.180 --> 00:04:57.379 Yep. The person who built the MCP server handled 00:04:57.379 --> 00:05:00.120 all that abstraction for you. That's the value. 00:05:00.339 --> 00:05:02.720 That's huge. Yeah. And because it's a standard 00:05:02.720 --> 00:05:06.540 protocol, that same server, say one for Google 00:05:06.540 --> 00:05:08.839 Calendar, I could use it in Cloud Desktop, but 00:05:08.839 --> 00:05:11.240 also maybe hook it into an automation tool like 00:05:11.240 --> 00:05:15.240 NANN or a totally custom app. Exactly. True. 00:05:15.819 --> 00:05:17.740 Host portability. Use the capability wherever 00:05:17.740 --> 00:05:20.139 MCP is supported. Okay. That does bring up a 00:05:20.139 --> 00:05:22.560 key question, though. Security. How does MCP 00:05:22.560 --> 00:05:24.839 handle security when you're connecting to something 00:05:24.839 --> 00:05:27.899 really private, like, say, your Gmail? Good question. 00:05:27.980 --> 00:05:31.939 It ensures security by making the AI ask for 00:05:31.939 --> 00:05:34.199 explicit user permission. That happens during 00:05:34.199 --> 00:05:36.360 the setup phase and then potentially, again, 00:05:36.579 --> 00:05:38.660 when the tool is actually used. You're always 00:05:38.660 --> 00:05:41.060 in control. Got it. User permission is key. All 00:05:41.060 --> 00:05:44.000 right. Segment three. The architecture. HCS and 00:05:44.000 --> 00:05:47.009 TRP. Right. So to really appreciate the elegance 00:05:47.009 --> 00:05:48.709 here, we need to quickly understand the three 00:05:48.709 --> 00:05:51.029 main parts. We call this the HCS architecture, 00:05:51.370 --> 00:05:54.629 host, client, server. Okay. So the host H, that's 00:05:54.629 --> 00:05:56.449 my AI application, the thing I'm actually talking 00:05:56.449 --> 00:05:58.449 to, like the chat window. Exactly. That's the 00:05:58.449 --> 00:06:02.629 user -facing bit. Then the client C. This is 00:06:02.629 --> 00:06:04.910 specialized software that lives inside the host. 00:06:05.110 --> 00:06:08.430 Think of it like a dedicated translator or maybe 00:06:08.430 --> 00:06:11.730 a network card just for MCP. It speaks the MCP 00:06:11.730 --> 00:06:14.149 language fluently. It handles all the technical 00:06:14.149 --> 00:06:16.410 communication stuff, the transport protocol, 00:06:16.509 --> 00:06:18.310 so the host application doesn't need to worry 00:06:18.310 --> 00:06:20.889 about those low -level details. Ah, okay. So 00:06:20.889 --> 00:06:23.110 the client handles the MCP -specific talking. 00:06:23.230 --> 00:06:25.920 And then the server, S... is the actual capability 00:06:25.920 --> 00:06:28.279 provider, like that Alpha Vantage server we talked 00:06:28.279 --> 00:06:30.420 about. Precisely. It's the standardized gateway 00:06:30.420 --> 00:06:32.819 that exposes the underlying tool's functionality. 00:06:33.339 --> 00:06:35.800 Okay, HCS makes sense. But you said what's really 00:06:35.800 --> 00:06:38.740 valuable is what's inside the server. TRP. Yeah, 00:06:38.800 --> 00:06:41.779 TRP. Tools, resources, and prompt templates. 00:06:41.839 --> 00:06:44.300 This is where the magic happens. So tools, these 00:06:44.300 --> 00:06:46.399 are the active functions, operations that actually 00:06:46.399 --> 00:06:48.160 do things. They can change the state of external 00:06:48.160 --> 00:06:50.480 systems, you know, send message in Gmail, execute 00:06:50.480 --> 00:06:53.519 a database, delete file. If it performs an action, 00:06:53.699 --> 00:06:56.420 it's likely a tool. Okay, active functions. Tools 00:06:56.420 --> 00:06:59.399 do things. What about resources? Resources. These 00:06:59.399 --> 00:07:01.680 are different. They provide efficient, read -only 00:07:01.680 --> 00:07:05.139 data access. Hmm, read -only. So like getting 00:07:05.139 --> 00:07:07.259 information without changing anything. Exactly. 00:07:07.480 --> 00:07:10.699 And the key word is efficient. Think about getting 00:07:10.699 --> 00:07:13.480 historical weather logs or maybe the structure, 00:07:13.579 --> 00:07:16.899 the schema of a database or just log files. Instead 00:07:16.899 --> 00:07:19.720 of the AI having to call a tool, say, 30 times 00:07:19.720 --> 00:07:23.220 to get 30 days of data. Which could be slow and 00:07:23.220 --> 00:07:25.600 may be expensive. Right. It just reads one resource 00:07:25.600 --> 00:07:28.720 once. Imagine resources like prepackaged data 00:07:28.720 --> 00:07:31.279 files or records the AI can just grab and consume 00:07:31.279 --> 00:07:33.959 quickly. Makes analyzing large amounts of data 00:07:33.959 --> 00:07:36.699 way faster and cheaper. That's a really useful 00:07:36.699 --> 00:07:39.379 distinction. Okay, tools do things. Resources 00:07:39.379 --> 00:07:42.540 provide bulk, read -only data. What's the P? 00:07:42.990 --> 00:07:45.769 P is for prompt templates. And these are fascinating. 00:07:45.910 --> 00:07:47.569 They're essentially structured blueprints, right? 00:07:47.649 --> 00:07:49.250 They're crafted by the person who built the server. 00:07:49.410 --> 00:07:52.589 And they're designed to guide the AI or even 00:07:52.589 --> 00:07:55.790 the user via the AI on the best way to interact 00:07:55.790 --> 00:07:57.990 with the server's capabilities. So they help 00:07:57.990 --> 00:08:00.430 make better prompts. Kind of, yeah. They ensure 00:08:00.430 --> 00:08:03.089 the AI constructs a perfectly structured, optimized 00:08:03.089 --> 00:08:05.970 request. You know, I still wrestle with prompt 00:08:05.970 --> 00:08:08.069 drift myself sometimes, trying to get just the 00:08:08.069 --> 00:08:10.930 right phrasing for complex tasks. So I really 00:08:10.930 --> 00:08:13.069 appreciate that these templates can handle that 00:08:13.069 --> 00:08:16.350 sophisticated structure. They can turn a user's 00:08:16.350 --> 00:08:19.029 maybe kind of vague request into an expert level, 00:08:19.110 --> 00:08:22.430 super optimized instruction that the AI can execute 00:08:22.430 --> 00:08:26.120 perfectly. Solves the fuzzy prompt problem. That's 00:08:26.120 --> 00:08:28.699 clever. So putting it all together, a database 00:08:28.699 --> 00:08:31.600 server like for SQLite could offer the whole 00:08:31.600 --> 00:08:34.659 TRP set. Absolutely. It could have tools for 00:08:34.659 --> 00:08:36.840 inserting or updating data. It could have resources 00:08:36.840 --> 00:08:38.879 for efficiently accessing the database schema 00:08:38.879 --> 00:08:41.539 or maybe query history logs. And it could have 00:08:41.539 --> 00:08:43.539 prompt templates designed to help you analyze 00:08:43.539 --> 00:08:45.639 the data effectively. It's a complete package. 00:08:45.899 --> 00:08:48.100 Okay. So just to nail it down, when would an 00:08:48.100 --> 00:08:50.460 AI specifically choose a resource instead of 00:08:50.460 --> 00:08:52.779 just using a tool? Resources are the go -to for 00:08:52.779 --> 00:08:55.620 efficient bulk read -only access. Think log files, 00:08:55.820 --> 00:08:58.000 historical records, schemas, existing data you 00:08:58.000 --> 00:09:00.659 need to analyze, not change. Mid -roll sponsor 00:09:00.659 --> 00:09:03.039 read placeholder. All right, we're back. Segment 00:09:03.039 --> 00:09:06.100 four, communication, building, and the future 00:09:06.100 --> 00:09:09.539 of MCP. Okay, so the actual communication flow 00:09:09.539 --> 00:09:12.889 between the client. in the host and the server 00:09:12.889 --> 00:09:14.610 is pretty straightforward there are basically 00:09:14.610 --> 00:09:17.990 three phases initialization that's the handshake 00:09:17.990 --> 00:09:19.990 where they introduce themselves check compatibility 00:09:19.990 --> 00:09:23.629 exchange lists of capabilities then message exchange 00:09:23.629 --> 00:09:25.909 that's the main part the requests and responses 00:09:25.909 --> 00:09:28.470 going back and forth and finally termination 00:09:28.470 --> 00:09:31.509 just a clean graceful ending to the conversation 00:09:31.509 --> 00:09:33.929 simple enough and how do those messages actually 00:09:33.929 --> 00:09:36.500 travel The transport methods. Right, the transport 00:09:36.500 --> 00:09:39.500 layer. If you're running the MCP server locally, 00:09:39.659 --> 00:09:41.500 like on the same machine as the host application, 00:09:41.899 --> 00:09:44.840 it typically uses standard input -output stinsted 00:09:44.840 --> 00:09:47.340 out, which is incredibly fast and secure because 00:09:47.340 --> 00:09:49.679 nothing leaves the machine. But limited, obviously. 00:09:49.980 --> 00:09:52.139 Yeah, limited to that one machine. For remote 00:09:52.139 --> 00:09:54.440 servers, which is more common for shared capabilities, 00:09:54.860 --> 00:09:58.940 we use HTTP -based transport. And within HTTP, 00:09:59.259 --> 00:10:02.279 streamable HTTP tends to be preferred. The big 00:10:02.279 --> 00:10:04.120 advantage there is that it's inherently stateless. 00:10:04.139 --> 00:10:06.220 The server doesn't need to remember the context 00:10:06.220 --> 00:10:09.039 from the previous request. Ah, which makes it 00:10:09.039 --> 00:10:11.840 easier to scale. Exactly. Much easier to scale 00:10:11.840 --> 00:10:14.340 horizontally across lots of server instances, 00:10:14.779 --> 00:10:17.740 handle more load. Even though you can build stateful 00:10:17.740 --> 00:10:20.840 apps on it, stateless is often simpler for scaling 00:10:20.840 --> 00:10:23.899 basic capabilities. Makes sense. Now, what if 00:10:23.899 --> 00:10:26.720 you, the listener, want to contribute? How do 00:10:26.720 --> 00:10:28.809 you actually build these servers? Well... It's 00:10:28.809 --> 00:10:32.009 becoming more accessible for quick, simple integrations, 00:10:32.009 --> 00:10:34.169 especially for existing tools. You can often 00:10:34.169 --> 00:10:37.610 use no code platforms. Tools like NAN, for example, 00:10:37.750 --> 00:10:40.169 are adding MCP support, letting you graphically 00:10:40.169 --> 00:10:43.029 build a server to wrap a tool. OK, so no code 00:10:43.029 --> 00:10:46.169 for simple stuff, but for the full power. Right. 00:10:46.269 --> 00:10:48.190 If you want to unlock the full potential, especially 00:10:48.190 --> 00:10:50.450 defining those custom resources and sophisticated. 00:10:51.129 --> 00:10:52.889 prompt templates we talked about. You'll need 00:10:52.889 --> 00:10:54.409 to roll up your sleeves and use the official 00:10:54.409 --> 00:10:57.029 code -based software development kits, the SDKs. 00:10:57.169 --> 00:10:59.830 Python is a common one. That code approach is 00:10:59.830 --> 00:11:01.190 really necessary if you're building something 00:11:01.190 --> 00:11:03.590 for production, for wider distribution, or something 00:11:03.590 --> 00:11:06.669 complex. This whole shift, it really feels like 00:11:06.669 --> 00:11:09.110 fundamental infrastructure work. Like this isn't 00:11:09.110 --> 00:11:11.590 just another app feature. It's like HTTP for 00:11:11.590 --> 00:11:14.570 the web or SMTP for email. It's creating that 00:11:14.570 --> 00:11:17.799 stable foundation. for ai to connect everywhere 00:11:17.799 --> 00:11:20.279 it really is and what's just fascinating maybe 00:11:20.279 --> 00:11:23.019 even a bit mind -blowing is the sheer scale of 00:11:23.019 --> 00:11:26.320 opportunity the standardization creates the ecosystem 00:11:26.320 --> 00:11:29.179 is growing exponentially right and the shift 00:11:29.179 --> 00:11:32.120 unlocks massive monetization potential for developers 00:11:33.049 --> 00:11:36.210 Whoa. I mean, just imagine scaling a really specialized 00:11:36.210 --> 00:11:39.590 premium MCP server, maybe one that provides, 00:11:39.789 --> 00:11:42.389 I don't know, expert level regulatory compliance 00:11:42.389 --> 00:11:45.610 checks for finance. Imagine scaling that to potentially 00:11:45.610 --> 00:11:48.730 reach like a billion queries across every single 00:11:48.730 --> 00:11:51.149 compatible AI application in the world. Yeah, 00:11:51.210 --> 00:11:52.970 that completely changes the business model for 00:11:52.970 --> 00:11:55.330 AI capabilities. The connection problem is solved, 00:11:55.450 --> 00:11:57.789 basically. Pretty much. Developers build a valuable 00:11:57.789 --> 00:12:00.230 capability into a server once, embedding their 00:12:00.230 --> 00:12:02.600 unique knowledge or data access. And they can 00:12:02.600 --> 00:12:05.519 sell it or offer premium tiers to any AI host 00:12:05.519 --> 00:12:08.179 application on the planet that speaks MCP. So 00:12:08.179 --> 00:12:10.720 what's the core business opportunity MCP standardization 00:12:10.720 --> 00:12:14.700 creates? Build once, sell everywhere. Specialized 00:12:14.700 --> 00:12:17.100 capabilities delivered as a distributed, standardized 00:12:17.100 --> 00:12:19.679 service. Okay, let's zoom out for a final recap. 00:12:19.919 --> 00:12:23.399 Big idea. MCP is positioning itself as the universal 00:12:23.399 --> 00:12:27.139 standard for AI integration. the USB for AI. 00:12:27.379 --> 00:12:30.500 It brings order to the chaos of custom APIs using 00:12:30.500 --> 00:12:33.840 that host client server model, the HCS. And critically, 00:12:34.120 --> 00:12:36.299 through the server, it gives AI applications 00:12:36.299 --> 00:12:39.840 three powerful new types of capabilities. TRP, 00:12:39.940 --> 00:12:42.840 tools for taking action, resources for efficiently 00:12:42.840 --> 00:12:45.299 grabbing read -only data, and prompt templates 00:12:45.299 --> 00:12:48.509 for ensuring expert -level interactions. It solves 00:12:48.509 --> 00:12:50.830 that structure problem. And a whole focus shifts, 00:12:51.009 --> 00:12:53.250 doesn't it? We've moved past constantly worrying 00:12:53.250 --> 00:12:55.470 about how to build custom connections for every 00:12:55.470 --> 00:12:58.090 single API. The focus now is entirely on what? 00:12:58.190 --> 00:13:00.629 What valuable capabilities can you actually build 00:13:00.629 --> 00:13:03.789 and offer inside an MCP server? Exactly. So for 00:13:03.789 --> 00:13:05.309 you listening, if you're just starting out with 00:13:05.309 --> 00:13:08.169 this, the easiest step is to explore the marketplaces. 00:13:08.389 --> 00:13:11.490 Find existing MCP servers, plug some pre -built 00:13:11.490 --> 00:13:13.470 tools into your favorite AI application today 00:13:13.470 --> 00:13:15.769 and see how it works. Right. And if you're maybe 00:13:15.769 --> 00:13:17.850 a bit more intermediate, try building a simple 00:13:17.850 --> 00:13:19.870 server yourself, maybe using one of those no 00:13:19.870 --> 00:13:22.450 -code tools like N8n. Just get a feel for the 00:13:22.450 --> 00:13:24.629 HCS architecture, how the pieces fit together, 00:13:24.750 --> 00:13:27.850 hands -on. Yeah. And if you're advanced or want 00:13:27.850 --> 00:13:30.350 to get there, dive deep. Use the code -based 00:13:30.350 --> 00:13:33.669 SDKs like the Python 1. master the full potential 00:13:33.669 --> 00:13:37.110 of TRP tools, resources, and templates. Think 00:13:37.110 --> 00:13:39.549 about what unique value you could build and start 00:13:39.549 --> 00:13:41.990 developing for this huge standardized market 00:13:41.990 --> 00:13:44.289 that's emerging. Okay, so here's a final thought 00:13:44.289 --> 00:13:46.289 to leave you with. Considering this incredible 00:13:46.289 --> 00:13:49.009 power of standardization that MCP offers, what 00:13:49.009 --> 00:13:52.070 currently isolated, maybe niche tool or complex 00:13:52.070 --> 00:13:55.190 data set exists in your professional life? Something 00:13:55.190 --> 00:13:57.929 that could be transformed into a valuable, maybe 00:13:57.929 --> 00:14:01.009 even premium MCP resource or tool, making it 00:14:01.009 --> 00:14:03.690 instantly available to potentially every AI agent 00:14:03.690 --> 00:14:06.009 out there. That's the real unlock, the advantage 00:14:06.009 --> 00:14:08.230 you've hopefully grasped today. What could you 00:14:08.230 --> 00:14:09.950 standardize and share? OTRO Music.