WEBVTT 00:00.120 --> 00:06.320 So in case there's any confusion, the most important thing that we've done today is explored how easy 00:06.360 --> 00:14.840 it is, how incredibly easy it is to set up an AI agent, which uses a couple of different sets of tools 00:14.840 --> 00:16.480 offered by third parties. 00:16.480 --> 00:18.880 We do it by putting in an MCP client. 00:18.880 --> 00:22.040 Here the MCP client connects to an MCP server. 00:22.040 --> 00:28.640 We just give it a URL and it's able to query that server, find out what tools it offers, find out 00:28.640 --> 00:30.880 why and then use them. 00:30.880 --> 00:33.200 And this worked and it worked great. 00:33.200 --> 00:38.360 And it came back with a list of real sales prospects with emails predicted. 00:38.360 --> 00:39.720 And that was terrific. 00:39.720 --> 00:45.440 And this is the place where you might well use MCP yourself to take advantage of all of the tools that 00:45.440 --> 00:51.760 are out there, although of course, a bunch of them are already implemented in Nan right off the bat. 00:52.040 --> 00:56.480 But should you find one that isn't and that you do want to use, this is ideal. 00:56.800 --> 00:57.360 Okay. 00:57.400 --> 01:02.900 And now we've taken it another step further, which is less common, but I want to show it to you anyway. 01:02.900 --> 01:06.620 And it's to say, how can we build our own MCP server? 01:06.620 --> 01:13.140 And in fact, let's put all this functionality behind an MCP server so all of this could be used. 01:13.300 --> 01:18.780 And we've done that by, first of all, turning all this into one workflow that can be called by another. 01:18.780 --> 01:21.180 And I called it prospecting Subagent. 01:21.460 --> 01:30.260 And then we went to, to uh, to this to uh, here and we created a prospecting MCP, a separate workflow. 01:30.260 --> 01:33.420 And it just contains one trigger MCP server trigger. 01:33.420 --> 01:35.180 The outside world would hit this. 01:35.380 --> 01:39.900 And this is where we have here our single tool. 01:40.060 --> 01:42.980 And the tool works by calling another workflow. 01:42.980 --> 01:45.580 And we've described what this tool does. 01:45.580 --> 01:50.380 It finds sales prospects for a given sales query. 01:50.660 --> 01:53.740 Okay I hope you're following this. 01:53.740 --> 01:55.820 And if you're not it doesn't really matter. 01:55.860 --> 01:57.460 This is a more advanced thing. 01:57.660 --> 02:01.890 Um, but people are always interested in how you could build an MCP server. 02:01.930 --> 02:04.370 The final thing we're going to do is actually use it. 02:04.370 --> 02:05.290 And how do we use it? 02:05.330 --> 02:08.290 Well, to use it we would want to have a URL. 02:08.650 --> 02:09.610 And I'm going to go ahead. 02:09.610 --> 02:10.490 We're going to be bold here. 02:10.490 --> 02:13.090 We're going to we're going to push it straight to production. 02:13.090 --> 02:16.090 And I'm going to copy this production URL. 02:16.090 --> 02:17.570 So let me go right here. 02:17.610 --> 02:18.810 Publish this guy. 02:19.170 --> 02:21.210 Uh actually maybe I should save it first. 02:21.210 --> 02:21.850 It says it's saved. 02:21.850 --> 02:22.730 Publish it. 02:22.730 --> 02:23.650 Publish. 02:24.170 --> 02:27.450 And now that green check there means that it's been published. 02:27.610 --> 02:29.050 This is out there. 02:29.290 --> 02:32.810 It only remains now for us to actually use it. 02:32.810 --> 02:37.330 So you might have been thinking, okay, it's cool that we've made an MCP server that can go and do 02:37.330 --> 02:40.770 sales prospecting, but how would we actually use this anywhere? 02:40.810 --> 02:44.810 Like what is there available to us that can take advantage of MCP servers? 02:44.810 --> 02:46.530 Well, actually, there's tons of things. 02:46.530 --> 02:51.010 All sorts of applications, AI applications support MCP servers. 02:51.010 --> 02:57.330 And one of the first and best is, of course, Claude, uh, from anthropic, the makers, the people 02:57.330 --> 02:59.650 that invented the MCP protocol. 02:59.650 --> 03:02.470 So here I am in Claude, and I can. 03:02.510 --> 03:07.230 I can of course, say hi there or whatever, but I'm going to press the plus button here and I'm going 03:07.270 --> 03:10.310 to go to add connectors down there. 03:10.310 --> 03:16.510 And here up comes, uh, the ability to, to add a different connector to Claude. 03:16.550 --> 03:21.430 And you can see choose from anthropic review tools, add a custom one or learn more. 03:21.430 --> 03:25.790 So I'm going to click on add a custom one, add a custom connector. 03:25.870 --> 03:30.990 So I'm going to call it Sales Prospecting Tool. 03:31.110 --> 03:35.350 And you can see that it hasn't used the word MCP anywhere in this terminology. 03:35.350 --> 03:40.550 But here you can see remote MCP server URL is what it wants now. 03:40.550 --> 03:43.430 And up to this point you might have never known what that even meant. 03:43.430 --> 03:51.550 But now you know that I can paste in there the MCP server URL that is copied straight out of Nan, the 03:51.550 --> 03:57.390 production one, not the test one, and this is the one that we're going to send add. 03:57.870 --> 04:01.140 And that has just been added sales Prospecting tool. 04:01.460 --> 04:05.060 It's in there and now we can try and use it. 04:05.100 --> 04:07.420 Okay, let me go to a new chat. 04:07.580 --> 04:23.220 Please use your sales prospecting tool to find, uh, people to find, uh, good targets for me to sell 04:23.460 --> 04:31.860 my accounting software to consulting firms in the US. 04:32.260 --> 04:34.220 Let's give this a shot. 04:34.460 --> 04:41.180 So I am just going to call this to to to Claude just through the user interface. 04:41.940 --> 04:44.980 So I'll use the sales prospecting tool. 04:45.180 --> 04:46.900 So it's making a request. 04:47.220 --> 04:50.780 Uh, it's saying can it use this sales prospecting tool. 04:50.820 --> 04:53.220 I'm going to say I'm going to say always allow. 04:53.380 --> 04:55.300 And did you see it had the query there. 04:55.300 --> 05:01.800 It used the query parameter by using our MCP server and connecting to N810, it discovered that that 05:01.800 --> 05:08.120 is the information that we want that is now calling our prospect Subagent, that is now running out 05:08.160 --> 05:08.560 there. 05:08.840 --> 05:15.280 Uh, and uh, momentarily, uh, when it's completed, all the various tool calls, I am very hopeful 05:15.280 --> 05:16.440 that I will get an answer. 05:16.680 --> 05:18.640 And I did indeed get an answer. 05:18.640 --> 05:19.560 Here's the answer. 05:19.560 --> 05:24.760 There are five strong prospects at US consulting firms for your accounting software, and here they 05:24.760 --> 05:26.520 are with their email address. 05:26.800 --> 05:31.880 And there are the five people different different set of five than before. 05:32.120 --> 05:34.640 And uh, a great set of results. 05:34.840 --> 05:38.400 And you can see that it called the prospecting Subagent. 05:38.400 --> 05:43.720 And it's synthesized the, the results within Claude right here. 05:43.920 --> 05:45.040 How about that. 05:45.040 --> 05:51.720 We just used an AI application, Claude, and it used an MCP server that we had written and published 05:51.720 --> 05:54.360 in Nan, and that was running in. 05:54.360 --> 06:02.540 And that then ran a workflow which, somewhat confusingly, itself then used a couple of MCP tools too. 06:02.580 --> 06:05.860 So we're using MCP in both directions for this. 06:05.900 --> 06:09.900 I hope you followed it all, but if not, don't worry, we'll do a quick recap tomorrow. 06:09.900 --> 06:10.820 And you can. 06:10.860 --> 06:17.220 You can focus mostly on the using the tools, but I thought this was a really cool end to end example. 06:17.220 --> 06:24.020 And just to really bring it to life back here in N810, I'm looking again at our prospecting MCP here. 06:24.020 --> 06:28.660 If I go to executions, I'm hoping to see there we go that it was run. 06:28.660 --> 06:30.460 It was run a few moments ago. 06:30.660 --> 06:36.340 Uh, and if we look at the logs, we will see that the call came in fine consulting firms in the US 06:36.380 --> 06:41.700 to sell accounting software to target midsize management consulting business advisory firms. 06:41.700 --> 06:42.820 So a great query. 06:42.820 --> 06:44.820 And that's why we didn't get the same set. 06:44.820 --> 06:50.580 We got something that was more midsize companies thanks to Claude adding on that bit of context there. 06:50.580 --> 06:51.700 So that's really great. 06:51.700 --> 06:53.300 And this was what came back. 06:53.300 --> 06:57.020 And these are the same, of course, as what got presented back in the Claude AI. 06:57.180 --> 07:03.810 So so this was the result of running our MCP, our prospecting MCP workflow. 07:03.850 --> 07:09.650 It was triggered automatically in production by Claude calling us via our MCP server. 07:09.690 --> 07:10.130 Okay. 07:10.170 --> 07:17.730 And if I come back here to the prospecting subagent and I look at the executions here, we will hopefully 07:17.770 --> 07:22.490 see this one right here that also just ran. 07:22.610 --> 07:25.730 And you will see that that was the query that was passed in. 07:25.850 --> 07:31.410 Sure enough, this was the same, the outputs that came back and this was the bunch of MCP calls that 07:31.410 --> 07:33.010 were made a number. 07:33.170 --> 07:34.810 Uh it's interesting. 07:34.970 --> 07:36.130 Let's have a look at this. 07:36.370 --> 07:38.330 Uh, let's see what it did there. 07:38.370 --> 07:47.010 So this time it only used Hunter because Hunter has a discover tool that is a sales prospecting tool. 07:47.170 --> 07:52.730 Uh, and I don't believe that this tool is available, at least as of now on the the nodes. 07:52.730 --> 07:55.810 It's only available through the MCP server. 07:55.930 --> 07:57.930 So, so this is really cool. 07:57.930 --> 08:02.670 We actually use functionality from Hunter that's only available, I believe, through the MCP server. 08:03.030 --> 08:05.870 To do a specific discovery. 08:06.190 --> 08:11.470 And so we use multiple different tools and a domain search tool and more domain searching. 08:11.630 --> 08:14.670 And then presumably here we've got email verifier. 08:14.870 --> 08:21.030 Uh and to to to check that the emails were accurate before it responded with the structured outputs. 08:21.030 --> 08:23.270 So a really interesting workflow. 08:23.310 --> 08:24.710 Maybe you have the same kind of workflow. 08:24.710 --> 08:26.310 Maybe you have something different. 08:26.310 --> 08:31.190 But for sure we can see that everything worked and we achieved our business outcome. 08:31.230 --> 08:31.870 Okay. 08:32.030 --> 08:36.030 And with that I know that we covered a lot of ground today. 08:36.030 --> 08:38.630 I know that I went pretty fast as well. 08:38.950 --> 08:41.030 Let me just make this nice and big again. 08:41.590 --> 08:44.870 I want to present to you one more time our workflow. 08:45.150 --> 08:47.670 At the end of the day, it's actually pretty simple. 08:47.670 --> 08:53.270 We built a prospecting subagent that was able to be executed by another workflow. 08:53.510 --> 09:01.220 It has two MCP clients, one that is Fire crawl, one that is Hunter, and it outputs in structured 09:01.260 --> 09:01.900 output. 09:01.940 --> 09:03.580 And it worked great. 09:03.580 --> 09:10.420 And we also used all of this and published it as an MCP server, which we then called from Claude. 09:10.660 --> 09:11.860 And everything worked. 09:11.860 --> 09:13.300 And I hope it worked for you too. 09:14.020 --> 09:17.620 Okay, so with that, we'll head over to the wrap up. 09:17.620 --> 09:21.940 And I promised you a big day today, and I hope you agree it was a big day. 09:22.220 --> 09:24.620 We got tons done and it was pretty satisfying. 09:24.860 --> 09:26.020 All right, see you for the wrap. 09:26.060 --> 09:29.340 A massive day, definitely our most advanced day so far. 09:29.460 --> 09:31.500 We covered tons of material. 09:31.540 --> 09:37.340 Tomorrow is a day I'm really looking forward to when we cover the great topic of context, engineering 09:37.340 --> 09:39.460 and recap on Subagents. 09:39.460 --> 09:46.780 And it takes just one second to pause and recognize your 87% of the way through. 09:46.820 --> 09:49.940 Today probably felt like like it was it was a big step. 09:50.060 --> 09:58.100 Uh, but, uh, wow, we're nearly at the finish line and oh, do I have two great days in store for 09:58.100 --> 09:58.500 you? 09:58.740 --> 10:00.180 I can't wait to show you.