WEBVTT 00:00.080 --> 00:01.640 Okay, let's dig in. 00:01.640 --> 00:06.960 So first up we used the Fire Crawl MCP server five times. 00:07.120 --> 00:10.400 And these were in fact all fire crawl searches. 00:10.400 --> 00:11.240 All five of them. 00:11.240 --> 00:12.080 I looked through them. 00:12.240 --> 00:13.160 And that's interesting. 00:13.160 --> 00:16.960 Last time I did five searches and then a bunch of scrapes. 00:17.120 --> 00:19.160 This time it didn't bother with the scrapes. 00:19.160 --> 00:23.960 It decided it had enough information from from these searches that it was good to go. 00:24.200 --> 00:25.240 And that's okay. 00:25.480 --> 00:30.800 The reason that we love Agentic AI is because we want the LLM to make its own decision about what it 00:30.800 --> 00:35.840 wants to do next, based on the information it has to hand, and that is what it decided. 00:35.840 --> 00:42.520 If we wanted it to be rigid and we wanted it to always first do a search and then do a scrape, then 00:42.520 --> 00:48.080 we should set up separate workflows steps and use something like structured outputs and different prompts 00:48.080 --> 00:50.520 to make it operate in that regimented way. 00:50.720 --> 00:53.880 But the idea of Agentic AI is no. 00:53.920 --> 00:57.480 Let the LLM decide based on the information it has to hand. 00:57.480 --> 00:59.040 And that is exactly what we did. 00:59.530 --> 00:59.970 Okay. 01:00.010 --> 01:03.250 So how about these 13 uses of Hunter. 01:03.250 --> 01:07.130 So in fact it was all using different email tools. 01:07.130 --> 01:08.530 So Hunter has a bunch of them. 01:08.530 --> 01:15.530 It was using a the email finder and the email verifier to check emails. 01:15.690 --> 01:18.810 And it was also using something else as well. 01:18.810 --> 01:22.690 I seem to remember hang on, it was using domain search as well. 01:22.690 --> 01:29.650 So it was using a bunch of different tools that that that Hunter makes available to try and really dig 01:29.650 --> 01:33.810 in to, to make the best shot at finding a reliable email address. 01:33.810 --> 01:36.650 So it really took the time over that, and that's pretty cool. 01:36.650 --> 01:43.770 And that's why as a result, we end up with this results with five good prospects here, starting with 01:43.810 --> 01:50.490 Yuval Adson, uh, Atzmon from McKinsey and company, uh, the senior partner and CFO at McKinsey. 01:50.690 --> 01:57.050 And with this, that apparently is a very good guess, a very good prediction of his email address. 01:57.210 --> 01:58.700 Um, from Hunter.io. 01:58.980 --> 02:01.660 And then this is the CFO of BCG. 02:01.940 --> 02:06.620 And similarly that's a very credible looking email courtesy of Hunter.io. 02:06.620 --> 02:08.460 And you'll find the same for the others. 02:08.460 --> 02:10.420 And hopefully you have something similar. 02:10.740 --> 02:12.820 So this is really great to see. 02:12.860 --> 02:16.260 If you look here by the way you can see the whole flow of everything that happened. 02:16.340 --> 02:17.900 An awful lot happened. 02:17.940 --> 02:20.460 This was a pretty sophisticated workflow. 02:20.460 --> 02:25.740 And let's face it, it was actually pretty easy just adding these two MCP clients. 02:25.740 --> 02:27.140 There really wasn't much to it. 02:27.140 --> 02:33.540 In fact, the hardest part of all this was just explaining all the terminology about MCP, MCP, client 02:33.540 --> 02:37.380 and host and server and streamable, HTTP and everything else. 02:37.460 --> 02:41.620 Actually using MCP was super easy and that's how it often is. 02:41.660 --> 02:44.140 MCP is very easy to use. 02:44.180 --> 02:46.780 We just bunged on extra tools here. 02:46.820 --> 02:51.460 Now I have a secret that I should reveal, which I didn't want to reveal it, but I probably should 02:51.620 --> 02:57.780 that whilst what we did with Fire Crawl was totally legit because Fire Crawl doesn't have tools. 02:57.780 --> 03:03.700 It turns out that, uh, that, uh, Hunter.io does, in fact have a tool. 03:04.180 --> 03:08.660 And so we could have just used the tool right here instead of using MCP. 03:08.820 --> 03:14.580 But one thing is that we would have then had to have picked these three things separately and had three 03:14.660 --> 03:18.860 separate tool operations, and it would have been more messy and more clunky. 03:18.860 --> 03:23.620 So it was easier perhaps to use MCP, but that is a bit of a stretch. 03:23.620 --> 03:27.300 The bottom line is, if you can use an na n node, you're probably should. 03:27.300 --> 03:31.380 And I had a really hard time finding things that didn't already have an N nodes. 03:31.500 --> 03:32.180 Uh, that. 03:32.220 --> 03:36.860 Which is why we've used this this, uh, Hunter MCP client. 03:36.860 --> 03:39.260 Anyway, just so we could put MCP to good use. 03:39.260 --> 03:41.780 But the fire crawler one was totally legit. 03:41.820 --> 03:43.300 That one I stand behind. 03:43.340 --> 03:44.580 But anyway, here we go. 03:44.620 --> 03:48.180 We've explored and we've used MCP servers. 03:48.340 --> 03:54.220 Uh, we've built the MCP clients to connect to the MCP servers other people have provided and they've 03:54.350 --> 03:56.550 worked great for our business objective. 03:56.590 --> 03:59.350 Okay, now we're gonna do something crazy. 03:59.590 --> 04:06.630 We're going to turn all of this into an MCP server so that someone else can use it. 04:06.990 --> 04:12.230 Which is confusing because this itself contains MCP clients which call other MCP servers. 04:12.230 --> 04:17.870 But we're going to package all of this up to make it into a tool which the outside world can use. 04:18.590 --> 04:19.630 Are you ready for this? 04:19.670 --> 04:20.590 That's what we're going to do now. 04:20.590 --> 04:23.870 I'm going to do it quite fast and I will do recaps another time. 04:23.870 --> 04:26.550 And it's not a common task that you'd often want to do this. 04:26.550 --> 04:28.470 So it's more for the show of it. 04:28.470 --> 04:29.910 So let's let's go and do it. 04:29.950 --> 04:30.310 Okay. 04:30.350 --> 04:31.790 First up I'm going to do something crazy. 04:31.790 --> 04:34.470 I'm going to delete this chat message thing here. 04:34.670 --> 04:36.590 I'm going to add a new trigger. 04:36.790 --> 04:44.790 And the trigger is going to be when executed by another workflow, meaning that this whole workflow 04:44.790 --> 04:48.710 is going to become something that can be called by another workflow. 04:49.070 --> 04:55.240 And, and I'm going to have it have one input field, which is going to be query, which is going to 04:55.240 --> 05:01.760 be the user's question, so that the query has to be passed in to this workflow and that will trigger 05:01.760 --> 05:03.000 this whole thing running. 05:03.880 --> 05:07.640 So far you may be only half with me, but when I escape, here we go. 05:07.680 --> 05:10.160 When executed by another workflow, this is the new trigger. 05:10.160 --> 05:12.880 This is replacing the chat window. 05:13.240 --> 05:15.760 And so now I just have to edit this agent. 05:15.800 --> 05:17.200 It can't be that anymore. 05:17.320 --> 05:19.600 It's not connected to a chat trigger node. 05:19.600 --> 05:22.120 We need to define it and we're going to define it. 05:22.160 --> 05:24.000 Can you think we're going to define it. 05:24.080 --> 05:25.280 What do you think it's going to be. 05:25.400 --> 05:28.560 It's going to be JSON query. 05:29.080 --> 05:33.440 We want to take the query fields from what comes in okay. 05:33.480 --> 05:41.200 So what comes in is then going to to be passed in here as the query okay I'm also going to name this. 05:41.240 --> 05:43.680 It's currently called my workflow 18. 05:43.680 --> 05:48.120 And I'm going to call it something different I'm going to have it be called prospecting. 05:49.000 --> 05:53.490 Prospecting I'm going to call it Subagent. 05:54.090 --> 05:56.330 Now, that might sound fancy to you. 05:56.370 --> 06:03.730 My point is that since this is itself a whole agent flow that can be kicked off by another workflow, 06:03.850 --> 06:06.890 then this whole thing is what we could describe as like a subagent. 06:06.930 --> 06:11.330 It's an agent that could run as part of some bigger, grander plan. 06:11.330 --> 06:13.450 And we're going to cover some agents tomorrow. 06:13.450 --> 06:17.050 So you don't need to worry too much about this, but just get a sense. 06:17.050 --> 06:22.530 We're calling this prospecting Subagent because it's able to prospect, and it is a little agent that 06:22.530 --> 06:25.370 can be within a bigger, grander plan. 06:25.690 --> 06:26.210 All right. 06:26.450 --> 06:27.010 Okay. 06:27.370 --> 06:29.010 Back to amplify again. 06:29.170 --> 06:32.930 Now in MCP, we have prospecting subagent. 06:32.970 --> 06:35.090 Let's make a new workflow. 06:35.370 --> 06:42.210 And this time we're going to call it prospecting MCP. 06:43.050 --> 06:44.010 Here we have it. 06:44.410 --> 06:52.460 And I'm going to add a step which is going to be an MCP server trigger. 06:52.700 --> 06:57.780 Expose tools as an MCP server endpoint. 06:58.420 --> 06:59.740 So here we go. 07:00.100 --> 07:01.540 I open this up and look. 07:01.540 --> 07:03.820 It's given me some URLs. 07:03.820 --> 07:06.580 It's given me a test URL and a production URL. 07:06.580 --> 07:12.820 And this is a URL that you could share with somebody else to say, hey, I'm running an MCP server. 07:12.860 --> 07:15.900 Connect to me if you want access to my tools. 07:16.300 --> 07:16.820 Okay. 07:17.300 --> 07:19.380 So, uh, here we go. 07:19.420 --> 07:21.300 Here it is MCP server trigger. 07:21.300 --> 07:27.220 It's going to expose whatever tools we put here to the outside world as an MCP server. 07:27.220 --> 07:32.940 And what we can put in here can be any, any, any tools that are available from, from all the different 07:32.940 --> 07:38.620 tools we've looked at at the past, including like the, the, the, um, not the firewall tool, the, 07:38.620 --> 07:43.980 the, uh, Hunter tool, it could be any tool that you found from your list of tools, but we don't 07:43.980 --> 07:45.660 want to expose any old tool. 07:45.660 --> 07:47.460 We don't want to expose Hunter. 07:47.590 --> 07:54.390 We want to expose the prospecting workflow that we just built as a tool for the outside world. 07:54.630 --> 08:03.310 So what we put in here is call and workflow tool, a tool which can call an entire workflow. 08:03.470 --> 08:05.510 Now that is starting to make some sense. 08:05.830 --> 08:08.630 And from this list we need to choose the workflow. 08:08.830 --> 08:14.230 The problem is we first need to publish the workflow we just made so that we can pick it from this list. 08:14.350 --> 08:15.230 Let's go and do that. 08:15.270 --> 08:15.590 Okay. 08:15.630 --> 08:17.590 First I press on amplify. 08:17.630 --> 08:18.870 I go to MCP. 08:18.950 --> 08:22.390 I go back to my subagent where we were just a minute ago. 08:22.550 --> 08:25.270 And I press publish and I say publish. 08:25.550 --> 08:30.030 And now a little green tick here appears to say this is published. 08:30.110 --> 08:35.710 Back to amplify back into MCP and to prospecting MCP. 08:35.990 --> 08:36.990 And here we are. 08:37.190 --> 08:43.830 And now we can open this guy up and we should be able to connect to our workflow. 08:43.950 --> 08:44.590 Let's see. 08:44.630 --> 08:47.590 And when I click here you should certainly see. 08:47.590 --> 08:56.950 I hope that there will be a prospecting subagent that appears on the list, and we just need to do a 08:56.950 --> 08:57.510 few more things. 08:57.510 --> 08:59.910 We need to describe this tool. 08:59.910 --> 09:07.510 So I'm going to say call this tool to find sales prospects. 09:09.870 --> 09:27.110 For prospects for a given sales query, this tool hunts for prospective clients and returns them and 09:27.110 --> 09:31.230 returns five leads okay. 09:31.510 --> 09:34.030 And then it says here workflow inputs. 09:34.030 --> 09:36.750 It knows that there's one field called query. 09:37.070 --> 09:40.630 And we want to say that the model can define this. 09:40.670 --> 09:44.110 It's a tool where the model can define what that query should be. 09:44.280 --> 09:50.480 It's an input and we can add a description and we can say, uh, state. 09:51.000 --> 10:00.800 Uh, what kind of, uh, sales prospect you are looking for such as? 10:02.080 --> 10:05.680 Such as find five. 10:05.720 --> 10:05.880 Yes. 10:05.880 --> 10:07.080 I don't think the five. 10:07.120 --> 10:07.440 Yeah. 10:07.600 --> 10:07.920 Fine. 10:07.960 --> 10:13.520 Find uh, um, uh, suitable, um, accountants. 10:16.720 --> 10:24.240 In the, uh, us to sell accounting software. 10:26.800 --> 10:28.000 Okay, that's a good example. 10:28.000 --> 10:29.760 I'm going to take out the number five there. 10:29.760 --> 10:30.320 Just have it be. 10:30.320 --> 10:30.720 Returns. 10:30.720 --> 10:31.320 Leads. 10:31.360 --> 10:32.600 Okay, great. 10:32.600 --> 10:34.160 There is our description. 10:34.160 --> 10:35.200 We have done that. 10:35.200 --> 10:37.080 I'm going to save and come back. 10:37.280 --> 10:41.200 And we're almost ready now to actually put this to use. 10:41.440 --> 10:43.520 But first I want to recap what we've done.