WEBVTT 00:00.120 --> 00:02.440 Okay, so I hope you're in a good frame of mind. 00:02.480 --> 00:08.200 We're going to go through our different technicalities, each of our three slides with three different 00:08.200 --> 00:09.400 concepts to get across. 00:09.400 --> 00:15.320 And this is the first slide, the first technicality I want to go through with you in that there are 00:15.320 --> 00:24.440 three parts of MCP, three pieces of the puzzle and they are called the MCP host, the MCP client, 00:24.440 --> 00:26.360 and the MCP server. 00:26.880 --> 00:30.320 Let's go back the MCP host client and server. 00:30.560 --> 00:31.280 What are they? 00:31.760 --> 00:32.680 Let me explain. 00:32.720 --> 00:40.560 The MCP host is the overall environment where your agents are running the overall software product that's 00:40.560 --> 00:44.640 controlling your agent environment, which might be Claude. 00:44.640 --> 00:49.800 If you're using Claude, either Claude on your desktop or using Claude through anthropic, the website. 00:49.800 --> 00:53.000 But that is like an AI product that you might be using. 00:53.040 --> 00:58.000 You might be using an AI application that might be like a, like some some software SaaS product that 00:58.000 --> 00:59.610 you're paying for, that you're using. 01:00.050 --> 01:06.370 Or it might be n810, you might have an n810 workflow, and that would be considered an MCP host. 01:06.410 --> 01:15.170 It is like an AI environment which is running an MCP client is something within that host. 01:15.170 --> 01:20.730 It's a small component of software that runs within that host, and there are potentially many of them. 01:20.730 --> 01:26.250 There's one of them for each of the tools that you want to run, or each of the sets of tools that you 01:26.250 --> 01:32.970 want to run from the third party, or to be specific, there is one for each of the MCP servers that 01:32.970 --> 01:35.850 you are running and an MCP server. 01:35.850 --> 01:37.450 That is the business. 01:37.450 --> 01:39.490 That is where it all happens. 01:39.490 --> 01:47.530 An MCP server is a particular group of tools offered by somebody under one kind of umbrella term that 01:47.530 --> 01:55.130 is set to to carry out some, some functionality for an LLM that is described in language by the author 01:55.130 --> 01:56.850 of that MCP server. 01:56.850 --> 02:04.590 So the MCP server could be someone like say, fire crawl, fire crawl that we that we worked on before. 02:04.630 --> 02:06.910 Fire crawl allows you to to search the internet. 02:06.950 --> 02:08.790 Fire crawl has a few tools. 02:08.790 --> 02:14.790 They could package them up, put some English to describe how they work, turn that into an MCP server, 02:15.070 --> 02:23.110 and then something like N810 could have an MCP client in there that connects to an MCP server that runs 02:23.110 --> 02:29.550 the fire crawl tools, and you can do the same thing for many other kinds of tools. 02:29.870 --> 02:36.230 So that is the definition of the three different pieces of the puzzle the host, the MCP client, the 02:36.230 --> 02:37.510 MCP server. 02:37.830 --> 02:38.790 That's what they are. 02:38.990 --> 02:39.590 Okay. 02:39.630 --> 02:42.790 Technicality two is really quite a technicality. 02:42.790 --> 02:43.830 So forgive me. 02:43.830 --> 02:48.070 If you're not interested in this, then just put me on two x zoom through this. 02:48.430 --> 02:54.550 There are different ways that MCP clients and MCP servers can talk to each other, different ways that 02:54.550 --> 02:55.590 they can connect. 02:55.590 --> 03:01.880 And that matters because some MCP servers are only available with some types of connection, and these 03:01.880 --> 03:04.560 things are called the transport mechanism. 03:04.600 --> 03:07.280 Sounds very high tech transport mechanism. 03:07.280 --> 03:08.720 And there are three of them. 03:08.720 --> 03:13.480 And the first of them is sometimes called stdio, sometimes called studio. 03:13.840 --> 03:16.760 It stands for standard input output. 03:16.800 --> 03:18.280 It's the simplest one. 03:18.280 --> 03:23.560 It's when the MCP server runs on the same computer as the MCP host. 03:23.600 --> 03:28.200 It runs on your computer, and the way the client talks to the server is what's called standard input 03:28.240 --> 03:31.880 output, which is one of the simplest ways that things can communicate. 03:31.880 --> 03:35.040 And so that is the first way and it's the simplest. 03:35.520 --> 03:42.080 The second one is called SC and it's a legacy approach which is no longer used. 03:42.240 --> 03:42.480 Sorry. 03:42.520 --> 03:43.360 It's deprecated. 03:43.360 --> 03:44.400 It is still used. 03:44.440 --> 03:49.600 I shouldn't say it's no longer used because it is it's no longer recommended for new build outs, but 03:49.600 --> 03:51.840 it is very much still a thing. 03:52.040 --> 03:56.450 And the third one is the replacement for se Streamable http. 03:56.610 --> 04:00.090 It is the updated version and numbers two and three. 04:00.130 --> 04:06.290 Those two techniques can happen with the MCP server running somewhere completely different to the MCP 04:06.330 --> 04:07.010 client. 04:07.010 --> 04:13.530 That is like a remote connection, whereas number one only works if it's running on the same computer. 04:13.530 --> 04:16.090 And that's the big difference between one, two and three. 04:16.290 --> 04:18.610 And that's really all you need to know about it. 04:18.650 --> 04:22.970 That one runs locally and that two and three run remotely. 04:22.970 --> 04:24.770 And that three is the new one. 04:25.050 --> 04:27.610 And that's that's that's pretty much it. 04:27.650 --> 04:30.090 With one other little fact that we're going to get to. 04:30.130 --> 04:33.610 And now for the third slide, which is more practical, which is about. 04:33.610 --> 04:34.250 All right. 04:34.490 --> 04:34.890 Okay. 04:34.930 --> 04:37.170 So now I've told you all this fancy lingo. 04:37.530 --> 04:41.930 How about how do we actually use MCP within N810. 04:41.930 --> 04:44.050 And there are three different ways. 04:44.370 --> 04:53.230 And the first way is that you can have an MCP client tool attached to your agent. 04:53.230 --> 05:00.390 So we know we have these AI agent cluster nodes, and that one of the things that come off them is tools. 05:00.390 --> 05:03.710 And we know that we can put in different tools in there. 05:03.710 --> 05:10.310 And so it should be no surprise to say, hey, you know, one of these tools can be an MCP client, 05:10.710 --> 05:16.990 and that means it's going to connect to someone else's MCP server, which is going to give us access 05:16.990 --> 05:18.390 to someone else's tools. 05:18.390 --> 05:19.630 And so that's cool. 05:19.630 --> 05:21.790 That is that is one way we can use it. 05:21.790 --> 05:23.470 And that is the most common way. 05:23.470 --> 05:25.830 And that is the that is the great way. 05:25.990 --> 05:34.070 That is the way that allows you to use other people's tools within an A10 through an MCP client, by 05:34.070 --> 05:35.670 having that as your tool. 05:35.830 --> 05:38.190 So hopefully looking at that image makes sense to you. 05:38.190 --> 05:39.870 It's like, okay, I get it now. 05:39.950 --> 05:45.510 That picture we saw before that is the MCP client inside Nan as the MCP host. 05:45.990 --> 05:46.590 All right. 05:46.590 --> 05:49.870 That's the first way and the most important way by far. 05:50.550 --> 06:00.360 The second way is that you can say, hey, my whole my whole workflow can itself be an MCP server. 06:00.560 --> 06:07.520 Somebody else's MCP client can talk to me and I can provide tools to them. 06:08.080 --> 06:08.400 Right. 06:08.440 --> 06:12.440 It's like the flip side, you can write tools that other people reuse. 06:12.680 --> 06:13.080 Okay. 06:13.120 --> 06:14.200 And how do you do that? 06:14.240 --> 06:19.960 Well, there is a special kind of trigger called an MCP server trigger. 06:20.160 --> 06:22.400 It's saying you want to be an MCP server. 06:22.440 --> 06:23.040 All right. 06:23.080 --> 06:25.080 I you can I can have a trigger. 06:25.080 --> 06:27.840 And it only has one thing that you have to attach to it. 06:27.840 --> 06:32.840 And that is the tools the tools that you are offering as this MCP server. 06:32.840 --> 06:34.160 And so you can put some tools in there. 06:34.160 --> 06:39.200 And in this screenshot I put in one that's just an HTTP request, that generic HTTP request that we're 06:39.200 --> 06:43.760 then going to offer up as tools to as an MCP server that way. 06:43.760 --> 06:50.620 And that would then become an MCP server that other people could attach to with an MCP client in MCP 06:50.660 --> 06:51.180 host. 06:51.180 --> 06:54.620 So that's the second way that you can use Nan. 06:54.780 --> 06:57.340 Not nearly as common as the first way. 06:57.460 --> 06:58.620 And there's a third way. 06:58.740 --> 07:01.460 And the third way is just like an extension of the second way. 07:01.500 --> 07:02.820 So no need to worry. 07:03.060 --> 07:09.220 It is just saying there's also a cool setting that allows you to kind of apply this, this approach 07:09.220 --> 07:15.860 globally, across your workflows or to a subset of your workflows and say, hey, I want I want to be 07:15.900 --> 07:24.420 able to give the outside world access to any of my workflows and treat them as MCP servers so that I 07:24.420 --> 07:29.580 could go to Claude and just talk to Claude and have Claude run any of my workflows. 07:29.580 --> 07:33.820 And that's like a setting, a global setting that's on the settings page in. 07:33.860 --> 07:35.060 I don't think we're going to use that. 07:35.060 --> 07:37.380 We're going to we're going to build the first thing for sure. 07:37.580 --> 07:41.340 And I think once we're going to do the second one as well, just to show you what it's like. 07:41.540 --> 07:46.100 And this third one is the same kind of thing for, for for everything if you wanted it. 07:46.380 --> 07:46.740 Okay. 07:46.780 --> 07:52.950 So those are the three ways to use MCP with n and n, keeping in mind that that first one is the most 07:52.950 --> 07:53.630 important one. 07:53.630 --> 08:00.590 And now at this point, you might be thinking to yourself, hang on a minute, this this MCP client 08:00.630 --> 08:02.110 tool at the top there. 08:02.230 --> 08:08.910 Just explain to me how is that any different to the other tools that we've already put there? 08:08.910 --> 08:11.390 We've put a bunch of different tools there. 08:11.630 --> 08:14.510 What's the difference between those tools? 08:14.510 --> 08:19.790 And using an MCP client tool that connects to an MCP server? 08:20.270 --> 08:21.990 And that's an excellent question. 08:21.990 --> 08:24.270 And and you're absolutely right to be confused about that. 08:24.270 --> 08:32.030 And I wish to clarify here it is the where you have a tools node that you can add in. 08:32.670 --> 08:39.590 That means that the team at Nh10 have built a custom node specifically for that tool. 08:39.590 --> 08:44.110 They've described it for your AI agent, they've put in the language. 08:44.110 --> 08:47.880 They've they've built this tool and made it so you can click and add it in. 08:47.880 --> 08:52.480 And sometimes there's also community nodes, which means people in the community have written them and 08:52.480 --> 08:54.360 they've done the same thing and they've packaged it up. 08:54.360 --> 08:56.960 And that is all part of what you get with N810. 08:57.000 --> 09:03.000 You get all of these tools that come out of the box that people have written, and that's great. 09:03.200 --> 09:06.960 And that is what you should always choose as your first preference. 09:07.080 --> 09:13.240 If someone has made a baked tool that you can just drop in here and use in Nw10, that's always going 09:13.280 --> 09:14.080 to be best. 09:14.120 --> 09:15.480 That's the thing to use. 09:15.840 --> 09:22.000 The time that you use MCP client is if you want some other set of tools, a set of tools that someone 09:22.000 --> 09:29.240 else has written where nobody has packaged it for N810 you don't have a node available before MCP, 09:29.280 --> 09:30.320 you are out of luck. 09:30.360 --> 09:31.160 That was it. 09:31.200 --> 09:33.600 Or you'd have to write code for it or something like that. 09:33.600 --> 09:38.840 Before MCP, you didn't have a way to get around it if there wasn't a node there. 09:39.000 --> 09:47.180 With MCP now you can just drop it in to N810 as an MCP client and then connect MCP server. 09:47.180 --> 09:52.900 And you can do something very similar in all of NS competitors and any other product like this, because 09:52.900 --> 09:54.100 it's a standard. 09:54.100 --> 09:56.980 So everyone is doing it the same way for MCP. 09:57.220 --> 10:02.180 Whereas before you might have to make an n node and you might have to do something different for other 10:02.180 --> 10:06.980 products that you wanted, like Zapier, you might need some other kind of thing in there if you wanted 10:06.980 --> 10:08.700 your tools to be exposed there. 10:08.820 --> 10:11.540 But because of MCP, there's one way of doing it. 10:11.540 --> 10:17.380 And then anything that supports dropping an MCP client in there, you can use it right away. 10:17.620 --> 10:19.180 So that's the key distinction. 10:19.180 --> 10:22.620 I'm sorry to ramble away about it, but I do hope that's clear in your mind. 10:22.820 --> 10:26.100 First and foremost, use any tools. 10:26.100 --> 10:31.660 They are the ones that have been specifically packaged for you, but if they don't exist, then as a 10:31.660 --> 10:38.140 fallback, if you find an MCP server that has the functionality you need, you can just use an MCP client 10:38.140 --> 10:42.220 here as like your generic connector to any MCP server. 10:42.340 --> 10:43.340 That's the idea.