WEBVTT 00:00.440 --> 00:04.160 In this tutorial we are going to learn something super exciting. 00:04.440 --> 00:10.000 The Model Context Protocol or MCP, which is a hot topic in the AI space right now. 00:10.520 --> 00:14.160 And in short, it can be a game changer for building AI agents. 00:14.760 --> 00:18.880 I'm going to briefly explain what it is and why it's important. 00:19.280 --> 00:24.960 Then we'll jump into an A-10 where I will show you how to actually use it in workflows. 00:25.440 --> 00:29.800 It might sound complicated, but trust me, it's actually pretty straightforward. 00:29.800 --> 00:34.640 And once you will see it in action, you will quickly understand why it's so important. 00:34.760 --> 00:40.480 According to anthropic, the company behind cloud, one of the best large language models on the market 00:40.480 --> 00:47.640 right now, MCP was launched in November last year but only recently started to gain real traction. 00:47.960 --> 00:55.880 So basically, MCP is a standardized way for large language models like cloud or ChatGPT to connect 00:56.360 --> 01:03.140 seamlessly to all your favorite apps and services like Gmail, CRM, Ms. Calendar's databases, rack 01:03.140 --> 01:04.300 agents, and more. 01:05.100 --> 01:13.180 And MCP gives LMS access to tools and data and lets them choose what to use based on the context of 01:13.180 --> 01:13.980 your prompt. 01:14.500 --> 01:24.380 As the name model context protocol suggests, a great analogy is this MCP is an open protocol that standardizes 01:24.580 --> 01:27.340 how applications provide context to the LMS. 01:27.780 --> 01:32.620 So think of MCP like a USB-C port for AI applications. 01:33.100 --> 01:40.820 Just as USB-C provides a standardized way to connect your devices to different accessories, MCP provides 01:41.140 --> 01:46.140 a standardized way to connect a modulus to different data sources and tools. 01:47.180 --> 01:54.620 This diagram shows how MCP acts as the layer between your agent and everything it needs to work with, 01:54.900 --> 01:57.340 like tools, data, and user input. 01:57.620 --> 02:02.120 So on the left you've got tools like search, search, GitHub. 02:02.720 --> 02:06.160 So this can be triggered automatically by the agent in the middle. 02:06.760 --> 02:14.240 There are resources like PDFs or user profiles which provide context and on the right prompts they let 02:14.240 --> 02:19.520 users guide the agent with templates like summarize or check compliance. 02:20.000 --> 02:23.800 So all of this is processed by your LLM or agent. 02:24.280 --> 02:32.440 And the MCP layer sits just benefit making sure the agent connects to everything properly and consistently. 02:33.040 --> 02:40.560 So then finally the agent can take action using APIs and microservices, databases or team tools all 02:40.560 --> 02:43.040 through this one unified interface. 02:43.200 --> 02:50.680 So instead of building custom code for every integration, MCP acts as a universal translator for your 02:50.880 --> 02:51.520 agents. 02:51.800 --> 02:54.880 Now let's dive in and see how you can use it with N810. 02:54.920 --> 03:00.880 Recently, at the beginning of April, the N810 team released native MCP nodes, which means we now 03:00.880 --> 03:05.250 have dedicated had built in support for working with MCP. 03:05.850 --> 03:14.410 Before that, the only way to use MCP in N810 was to self-host N810 and manually add the MCP server 03:14.770 --> 03:16.530 as a community node from GitHub. 03:16.970 --> 03:19.810 So it worked, but it was definitely more technical. 03:19.850 --> 03:26.770 Now it's much easier and I will show you step by step how to get started using this new native node 03:26.770 --> 03:27.690 in your workflows. 03:27.770 --> 03:33.810 So yes, in this tutorial I'm going to walk you through step by step how to set up the MCP server in 03:33.850 --> 03:42.050 N810 and what it can do, and how you can connect to it from tools like cloud, desktop app, or even 03:42.330 --> 03:45.690 another workflow using the MCP client node. 03:45.730 --> 03:55.210 The MCP server trigger listens for incoming requests from tools like cloud Gmail to send emails, Google 03:55.210 --> 03:58.330 Calendar to create events, or calculator. 03:58.650 --> 04:00.290 Just a simple example tool. 04:00.570 --> 04:05.950 So these are all tools our agent can access and control. 04:05.950 --> 04:07.350 Now on the other side. 04:07.470 --> 04:09.110 You got the MCP client. 04:09.110 --> 04:14.270 So in this setup, the agent starts when a chat message is received. 04:14.630 --> 04:19.270 So for example, a user saying add a meeting to my calendar. 04:19.270 --> 04:21.750 So you can ask the agent to do that for us. 04:22.230 --> 04:26.030 And then it passes the request to the agent host. 04:26.710 --> 04:34.350 And the MCP client node here gives the agent access to all the tools available on the server side. 04:34.590 --> 04:36.190 So all those tools. 04:36.590 --> 04:42.870 It also remembers what tools are allowed and manages how the agent communicates with them. 04:42.870 --> 04:49.110 So the server side handles the tools and the client side is where your LLM is. 04:49.150 --> 04:51.030 And we call that the host. 04:51.350 --> 05:00.030 So in our example here the agent is a host because it connects to the MCP server to call the tools. 05:01.110 --> 05:08.290 So we'll also be using the cloud desktop app as another host, and I will show you just how cool that 05:08.290 --> 05:09.490 setup is in action. 05:10.850 --> 05:15.650 Now let me give you a quick look at what this setup can actually do. 05:17.090 --> 05:22.450 So again, on the left side of my workflow I've got the MCP server. 05:23.490 --> 05:25.610 It has access to a few tools. 05:26.250 --> 05:30.050 Now let's say I jump into the cloud desktop app. 05:32.450 --> 05:35.730 Which acts as a as a host in this case. 05:36.410 --> 05:40.890 In our second example, the A agent acts as a host. 05:41.730 --> 05:47.170 But for this demo we are using the cloud desktop app. 05:47.570 --> 05:56.650 So when it connects to my MCP server through this node, it instantly sees all the tools I've given 05:56.650 --> 05:57.450 access to. 05:58.650 --> 06:10.710 So now in the cloud desktop app I can ask it something like send email to Damien at n810 demos at gmail.com. 06:10.750 --> 06:13.230 That his agents course is amazing. 06:13.550 --> 06:20.390 Use gmail tool and when I press and when I press this button to start this task. 06:23.310 --> 06:25.990 You can see that cloud processes the requests. 06:29.390 --> 06:38.550 And I'm going to give it permission to to do this task for me and use the Gmail tool we added in our 06:38.590 --> 06:41.030 N810 setup to allow for this chat. 06:46.790 --> 06:52.910 Here you can see how the setup uses the Gmail tool to send the email. 06:55.070 --> 06:59.470 The email has been successfully sent to Damien at n810 demos at gmail.com. 06:59.470 --> 07:03.750 Which with the subject your agents is amazing. 07:03.990 --> 07:09.450 Now let's jump into my gmail inbox and check if I got the email. 07:15.330 --> 07:16.250 Let's refresh it. 07:21.490 --> 07:23.170 And as you can see, I got an email. 07:24.610 --> 07:27.050 The subject agents course is amazing. 07:27.090 --> 07:30.410 Hi Damien, I wanted to let you know that your agent's course is amazing. 07:30.650 --> 07:33.690 The content has been incredibly helpful and informative. 07:33.810 --> 07:36.370 Thank you for creating such valuable resources. 07:36.410 --> 07:37.290 Best regards. 07:38.010 --> 07:39.970 So it works. 07:39.970 --> 07:42.250 And now what actually happened here? 07:42.290 --> 07:44.410 Let's go back to setup. 07:46.970 --> 07:51.050 So so MCP stands for Model Context Protocol. 07:51.290 --> 07:53.370 So think of it as a bridge. 07:53.490 --> 07:55.650 So you set up a central server. 07:55.690 --> 08:02.130 So in our example the MCP server with tools and workflows you want to share. 08:02.610 --> 08:05.590 So then from outside other apps. 08:05.590 --> 08:14.510 In our example, we are using the cloud desktop app, or agents can connect through the MCP client node 08:14.510 --> 08:16.590 and instantly use these tools. 08:16.590 --> 08:20.550 So no need to manually add every tool to every agent. 08:20.710 --> 08:26.590 And it's super efficient, especially if you are managing a lot of workflows or building AI systems. 08:26.590 --> 08:32.710 So again, we connected the cloud desktop app to our MCP server trigger and large language model. 08:33.630 --> 08:40.310 So cloud in that case is able to use these tools to perform specific actions. 08:40.310 --> 08:43.150 And we wanted it to send an email to myself. 08:43.150 --> 08:45.830 But this example is just for the sake of this tutorial. 08:45.950 --> 08:52.030 So it's very simple, but you can add a lot of more tools to this setup and give it more complex tasks 08:52.030 --> 08:52.470 to do. 08:52.510 --> 08:54.790 All right, now let's build this together from scratch. 08:54.790 --> 09:02.950 So first go into a new workflow and let's rename it to the MCP 09:06.840 --> 09:09.880 And now we are going to add the first node. 09:09.880 --> 09:11.120 So at first step. 09:12.600 --> 09:14.520 And now search for MCP. 09:17.000 --> 09:19.040 And we are looking for this node. 09:19.040 --> 09:25.120 So MCP server trigger which expose anytime tools as an MCP server endpoint. 09:26.160 --> 09:27.040 So click on it. 09:28.000 --> 09:31.640 Now make sure to switch over to the production URL. 09:31.800 --> 09:32.960 This is very important. 09:33.240 --> 09:41.960 Give it a simple path like MCP and click authentication off for now unless you need it later. 09:43.000 --> 09:45.040 Now we are going to attach some tools. 09:47.640 --> 09:50.480 So you can add things like calculator. 09:57.400 --> 09:58.240 Nodes email. 09:58.680 --> 10:04.080 So add tool search for Gmail email tool. 10:05.700 --> 10:08.060 Now make sure your Gmail account is connected. 10:09.900 --> 10:11.500 Leave it as set automatically. 10:11.980 --> 10:14.740 The resource as a message operation send. 10:14.780 --> 10:16.660 We want because we want to send a message. 10:18.900 --> 10:23.940 Now we want to define this parameter automatically, so click on it. 10:26.140 --> 10:27.500 The same for the subject. 10:28.620 --> 10:34.740 We want to leave image type as HTML and we want let the model define this parameter as well. 10:36.860 --> 10:43.060 Now we want to add option append and attribution and switch it off. 10:44.100 --> 10:44.940 All right great. 10:50.140 --> 10:59.140 Now let's use the Cloud Desktop app as our MCP host to connect to this MCP server. 10:59.180 --> 11:04.140 Trigger to be able to use these tools as I showed you in the example. 11:04.620 --> 11:08.200 So now you need to download the cloud desktop app now. 11:08.200 --> 11:11.480 In order to download the cloud desktop app. 11:11.680 --> 11:14.560 Go to Google Type Cloud desktop download. 11:15.240 --> 11:16.440 Click on the first link. 11:16.480 --> 11:18.120 Now choose your operating system. 11:18.680 --> 11:19.560 Windows or Mac. 11:19.840 --> 11:21.320 It will download the file for you. 11:21.320 --> 11:22.680 Just wait a few minutes. 11:22.800 --> 11:25.840 All right, now let's click on that image to install the application. 11:26.200 --> 11:27.160 Let's just finish. 11:27.880 --> 11:32.440 Now once you install the cloud desktop app this is how it's going to look like. 11:33.360 --> 11:38.480 Now very important step is to go to the settings A help. 11:39.880 --> 11:42.400 And here you have to enable the developer mode. 11:43.120 --> 11:45.120 It doesn't show up because I already done it. 11:45.120 --> 11:45.560 So. 11:46.520 --> 11:49.560 So please make sure to enable the developer tools. 11:50.160 --> 11:54.080 Once you do that go to File Settings. 11:56.240 --> 11:57.280 Click on developer. 11:59.320 --> 12:05.800 Edit configure and it will automatically show you this file. 12:06.220 --> 12:06.940 Open it. 12:10.340 --> 12:12.380 And for you, this file will be empty. 12:13.300 --> 12:18.740 I'm going to leave this code snippet in the resources, so you can just simply copy and paste it here. 12:19.580 --> 12:25.620 If you don't have any source code editor on your system, because for me, it opened the file automatically 12:25.620 --> 12:26.980 in Visual Studio Code. 12:27.340 --> 12:36.660 Simply go to Google and search for Sublime Text and install it, and it will automatically open the 12:36.660 --> 12:39.460 file for you in the sublime text. 12:40.460 --> 12:41.740 Now here is something important. 12:41.780 --> 12:44.900 The team recently changed their MVP configuration format. 12:45.140 --> 12:50.620 So they moved from using Super Getaway to a new MVP remote approach. 12:50.980 --> 12:52.780 So the old format used to look like. 12:53.100 --> 12:53.860 Let me show you. 12:56.820 --> 12:57.740 Got it right here. 12:57.940 --> 12:59.740 So the old format used to look like this. 13:00.620 --> 13:02.660 Now with Super getaway and webhook URLs. 13:02.660 --> 13:06.860 But now it uses MVP remote with proper authentication tokens. 13:07.640 --> 13:08.920 And it look it looks like this. 13:09.920 --> 13:12.040 So this new format is more secure and readable. 13:12.320 --> 13:17.440 Now what this means and this is really important, if you are using a cloud version, you still need 13:17.440 --> 13:21.680 to use the old connection because if you check the URL from your MCP trigger node. 13:24.680 --> 13:30.600 You will notice that at the end there is SSE, which means it's using server sent events. 13:30.760 --> 13:37.040 So you need the old super gateway configuration, but you need to install Node.js, npm and NP packages 13:37.040 --> 13:45.280 because as you can see in both connections, they use the NP command and NP runs the super gateway package 13:45.320 --> 13:48.120 in the old format and the MCP remote package in the new format. 13:48.520 --> 13:53.920 So if you are using the self-hosted version or the latest N810 setup, then you can use the new MCP 13:53.920 --> 13:54.640 remote format. 13:54.920 --> 13:59.840 You should already have Node.js installed since it's required to run N810 by using the wrong format, 14:00.160 --> 14:06.400 you will not be able to connect N810 to Cloud Desktop app, and I'm going to provide detailed instructions 14:06.400 --> 14:10.530 on how to install NodeJS, NPM and NP in the resources section of this lesson. 14:11.170 --> 14:17.970 So to clarify, if you are using any cloud paid version in order to connect your instance to Cloud desktop 14:18.010 --> 14:21.410 app, you need to use the alt code snippet. 14:21.410 --> 14:24.370 But you have to install NodeJS and required packages. 14:25.010 --> 14:27.690 But if you are self-hosting then you can use this new connection. 14:31.770 --> 14:34.130 You can find this configuration in the official documentation. 14:34.490 --> 14:38.650 I'm going to include the correct code for both scenarios and all the links in the resources section 14:38.650 --> 14:40.370 of this lesson, so you can easily use it. 14:40.690 --> 14:49.810 Now, in order to connect your Cloud desktop app as a host to our server, we need to go back to N810. 14:50.650 --> 14:52.730 Open the MCP server trigger node. 14:54.970 --> 14:57.850 Make sure to switch over to production URL. 14:58.970 --> 14:59.850 Copy it. 15:00.650 --> 15:04.410 Go to the code snippet and paste it right here. 15:08.550 --> 15:10.070 Also make sure to save it. 15:13.070 --> 15:14.030 Okay, great. 15:14.070 --> 15:18.510 Now, when you go to the cloud to desktop app, you will see. 15:19.590 --> 15:20.510 Let's open it. 15:25.590 --> 15:28.390 And as you can see, we don't have access to any tools yet. 15:28.790 --> 15:32.150 This is because we didn't make. 15:32.670 --> 15:33.550 Oh yeah. 15:33.590 --> 15:36.030 Could it not attach the MCP server in ten. 15:36.350 --> 15:40.670 So which means our MCP and A10 server is disconnected. 15:40.990 --> 15:45.710 And in order to connect it properly, we need to make our workflow active. 15:45.710 --> 15:47.310 So this is very important step. 15:47.430 --> 15:49.710 So make sure to make your workflow active. 15:51.670 --> 15:52.590 Alright great. 15:52.630 --> 15:53.310 Confirm. 15:54.350 --> 15:58.510 And now let's go back to the cloud desktop app. 15:59.710 --> 16:08.650 And now as you can see we successfully connected our desktop app to the workflow because two MCP tools 16:08.650 --> 16:15.770 are available now, so cloud can use tools provided by specialized servers using Model Context Protocol. 16:16.330 --> 16:22.050 And now we have access to Calculator and Gmail, the tools we have added to our MPC server node. 16:23.370 --> 16:25.050 We have a Gmail and calculator. 16:25.090 --> 16:26.090 Now let's test it. 16:26.490 --> 16:30.090 For example, let's ask close to us. 16:33.130 --> 16:38.650 Multiply 48 by 186. 16:40.690 --> 16:45.330 Use calculator tool and click submit. 16:47.170 --> 16:51.530 It's gonna use that tool from our workflow. 16:52.450 --> 16:55.810 Now we have to give it permission to use external integration. 16:56.170 --> 16:58.130 So calculator from N810 workflow. 16:59.010 --> 17:02.850 As you can see we have an input here for this chart. 17:07.770 --> 17:09.070 We receive the results. 17:09.070 --> 17:14.110 And now to confirm, when you go to the Na ten and we go to executions. 17:18.190 --> 17:20.550 And the last execution succeeds. 17:21.950 --> 17:23.510 Let's wait a moment. 17:24.710 --> 17:32.990 As you can see, code from our desktop app connected to this MCP server trigger and and made the calculation 17:32.990 --> 17:35.070 for us using the calculator tool. 17:35.110 --> 17:36.670 Now let's go back to the editor. 17:37.510 --> 17:37.790 Alright. 17:37.790 --> 17:38.270 Perfect. 17:38.310 --> 17:46.710 Now, instead of using the cloud desktop app as a host to connect to our MCP server, let's build the 17:46.710 --> 17:53.270 second part of the workflow and use a agent as a host to connect to our MCP server. 17:53.510 --> 17:54.870 To use these tools. 17:54.870 --> 17:57.950 So let's build this agent host from scratch. 17:58.110 --> 17:59.830 So let's go back to our workflow. 18:03.830 --> 18:05.830 Let's add a agent. 18:11.490 --> 18:12.730 Now let's add a trigger. 18:14.690 --> 18:15.610 So in chat. 18:22.570 --> 18:23.850 Let's connect these two nodes. 18:26.010 --> 18:27.290 Now let's add the chat model. 18:27.650 --> 18:32.930 So the brain for our agent just simply. 18:35.090 --> 18:35.570 ChatGPT. 18:35.610 --> 18:40.930 For now as a tool we are going to use MCP client. 18:40.930 --> 18:46.610 So our MCP client will be able to connect to the MCP server and use these tools. 18:50.130 --> 18:58.850 So simply search for MCP MCP client tool to connect tools from an MCP server. 19:01.530 --> 19:02.370 Alright great. 19:02.730 --> 19:06.930 And here we have to paste the same webhook we are using in the previous example. 19:08.050 --> 19:09.690 So go to MCP server trigger. 19:09.690 --> 19:11.790 Sugar production. 19:11.790 --> 19:12.750 Production URL. 19:15.630 --> 19:16.510 Copy it. 19:19.990 --> 19:22.910 And paste it as an endpoint here to this field. 19:24.430 --> 19:24.950 Great. 19:25.830 --> 19:26.750 Now let's save it. 19:28.910 --> 19:31.630 And now when I go to the open chart. 19:33.870 --> 19:39.390 And give our agent so Gpt4 mini. 19:42.390 --> 19:48.070 The same task we give to cloud through the cloud desktop app. 19:48.910 --> 19:54.910 So send email to demon, etc. and click submit. 19:56.990 --> 19:58.150 It's gonna use. 20:00.910 --> 20:02.030 The same email tool. 20:05.910 --> 20:09.310 Let's see the output I'm going to expand it. 20:10.280 --> 20:11.200 Human input. 20:11.240 --> 20:12.360 Send email to Damien. 20:12.560 --> 20:13.280 Output. 20:16.400 --> 20:19.440 In JSON so we can see the code. 20:19.720 --> 20:23.560 Now let's go to execution to make sure it's successfully executed the task. 20:29.080 --> 20:29.680 All right. 20:30.200 --> 20:31.720 Let's open the last execution. 20:33.480 --> 20:41.240 As you can see, MCP client MCP client was able to use Gmail tool to MCP server. 20:43.440 --> 20:44.520 Let's go back to editor. 20:45.560 --> 20:45.880 All right. 20:45.880 --> 20:46.320 Perfect. 20:46.320 --> 20:47.640 Let's go back to the editor. 20:49.480 --> 20:55.280 Now you don't need a cloud subscription to use the MCP connection through the cloud desktop app. 20:55.640 --> 21:01.360 However, keep in mind that if you are using the free plan, the quantity of queries you can send to 21:01.400 --> 21:03.280 Anthropic's models may be limited. 21:03.400 --> 21:09.040 So depending on what you are building, you might eventually want to upgrade for higher usage limits 21:09.040 --> 21:10.200 and more flexibility. 21:10.200 --> 21:11.140 Ability overall. 21:11.180 --> 21:17.820 MCP opens up a whole new world of possibilities for building more powerful, connected agents. 21:17.820 --> 21:27.540 It acts like a universal bridge between your agents and the tools or data they need, allowing multiple 21:27.580 --> 21:36.580 agents to access the same MCP server workflows for each one without needing to configure tools or recreate 21:36.580 --> 21:38.460 workflows for each one separately. 21:38.460 --> 21:45.420 So using MCP can save you a lot of time, make your setup much more efficient, and help you scale your 21:45.420 --> 21:46.740 AI systems faster. 21:47.300 --> 21:54.420 Now that you understand the concept and setup, you can start using MCP to make your agents smarter, 21:54.580 --> 21:58.140 faster, and more useful for real world applications. 21:59.020 --> 22:06.140 And please note this is a very new concept, and I personally believe that MCP will become a key part 22:06.180 --> 22:10.300 of how advanced agents are built and connected in the near future. 22:10.540 --> 22:11.980 I will see you in the next lesson.