WEBVTT 00:00:00.000 --> 00:00:03.160 Have you ever stopped to think, like, what really 00:00:03.160 --> 00:00:06.580 makes an AI assistant powerful? Not just, you 00:00:06.580 --> 00:00:08.720 know, a chat bot that can talk back. Yeah, it's 00:00:08.720 --> 00:00:10.619 a great question. It's more than just smart conversation, 00:00:10.720 --> 00:00:13.980 isn't it? Exactly. That key thing, the real game 00:00:13.980 --> 00:00:17.039 changer, it seems to be its ability to actually 00:00:17.039 --> 00:00:19.250 connect out to your other stuff. your tools, 00:00:19.429 --> 00:00:22.010 your data. Right, like hooking into your calendar 00:00:22.010 --> 00:00:24.050 or maybe digging into your company database, 00:00:24.269 --> 00:00:26.690 even checking your emails or using your CRM. 00:00:27.129 --> 00:00:29.089 That's where the power lies. It's that jump from 00:00:29.089 --> 00:00:33.090 just understanding words to understand your whole 00:00:33.090 --> 00:00:36.049 business setup. Precisely. And the tech that 00:00:36.049 --> 00:00:38.549 makes this possible and crucially makes it scalable 00:00:38.549 --> 00:00:41.409 for almost anyone is this open source standard 00:00:41.409 --> 00:00:44.929 called Model Context Protocol, MCP for short. 00:00:45.210 --> 00:00:47.689 And MCP is exactly what we're diving deep into 00:00:47.689 --> 00:00:49.829 today. We want to walk you through everything 00:00:49.829 --> 00:00:52.070 you need to know, what it is, why it matters, 00:00:52.170 --> 00:00:55.329 and how you can actually use it. Yeah, the goal 00:00:55.329 --> 00:00:57.270 is really to show you how to take your AI from 00:00:57.270 --> 00:00:59.689 just talking to actually being a core part of 00:00:59.689 --> 00:01:02.969 your business systems. OK, so. To really get 00:01:02.969 --> 00:01:05.530 why MCP is such a big deal, maybe let's think 00:01:05.530 --> 00:01:08.310 about what it was like before MCP. Good idea. 00:01:08.650 --> 00:01:11.430 Imagine trying to manage a big international 00:01:11.430 --> 00:01:13.409 team where everyone speaks a totally different 00:01:13.409 --> 00:01:15.870 language. That's kind of what connecting AI to 00:01:15.870 --> 00:01:18.510 tools used to be like. Right. So if your AI needed 00:01:18.510 --> 00:01:22.390 data from, say, Salesforce, it had to learn Salesforce 00:01:22.390 --> 00:01:24.549 speak. Exactly. And then if it needed something 00:01:24.549 --> 00:01:27.390 from Google Analytics, OK, now it needs to learn 00:01:27.390 --> 00:01:30.200 that specific language too. which meant custom 00:01:30.200 --> 00:01:33.219 coding for every single connection, like hiring 00:01:33.219 --> 00:01:35.060 a separate human translator for every single 00:01:35.060 --> 00:01:37.579 app. Yeah. And you can see pretty quickly how 00:01:37.579 --> 00:01:39.819 that just doesn't scale, right? What if you add 00:01:39.819 --> 00:01:42.120 a new tool or you want to switch the AI model 00:01:42.120 --> 00:01:44.400 you're using? You're back to square one, rebuilding 00:01:44.400 --> 00:01:47.239 integrations. Just managing that web of connections 00:01:47.239 --> 00:01:50.900 sounds frankly exhausting. It was a real efficiency 00:01:50.900 --> 00:01:53.560 tiller. And this is precisely where MCP comes 00:01:53.560 --> 00:01:56.700 in. Think of it as the the universal translator. 00:01:57.120 --> 00:01:59.819 OK. So the AI doesn't need to learn 10 different 00:01:59.819 --> 00:02:02.519 tool languages anymore. Nope. It just needs to 00:02:02.519 --> 00:02:06.659 learn one. The MCP language. And when tool providers, 00:02:07.040 --> 00:02:09.159 the Salesforce's notions of the world, adopt 00:02:09.159 --> 00:02:12.300 MCP, they all start speaking that same standard 00:02:12.300 --> 00:02:14.460 language. Which gets rid of all that constant 00:02:14.460 --> 00:02:16.900 custom integration work on your end. Exactly. 00:02:17.280 --> 00:02:19.639 And here's the really cool part for you, the 00:02:19.639 --> 00:02:25.210 user. Your AI apps become model agnostic. Okay. 00:02:25.229 --> 00:02:26.969 What does that mean in practice? It means you 00:02:26.969 --> 00:02:29.229 can switch between AI models. Maybe you start 00:02:29.229 --> 00:02:32.430 with chat GPT, then try Claude, or maybe some 00:02:32.430 --> 00:02:34.550 new AI comes along. You can swap them without 00:02:34.550 --> 00:02:36.530 having to rebuild all those connections to your 00:02:36.530 --> 00:02:39.090 tools. Wow. Okay. So you're not locked into one 00:02:39.090 --> 00:02:41.229 AI vendor just because you built integrations 00:02:41.229 --> 00:02:43.610 for it. Precisely. It makes adopting AI much 00:02:43.610 --> 00:02:46.270 more flexible. And that's why MCP is becoming 00:02:46.270 --> 00:02:48.909 like really critical infrastructure. It's fundamentally 00:02:48.909 --> 00:02:51.229 changing what AI can do within a business. Makes 00:02:51.229 --> 00:02:53.780 sense. So let's break down. MCP itself, what 00:02:53.780 --> 00:02:55.960 are the main pieces we need to understand? Okay, 00:02:56.080 --> 00:02:58.099 so fundamentally, there are two core components. 00:02:58.360 --> 00:03:01.379 First, you've got the MCP servers. Servers, okay, 00:03:01.520 --> 00:03:03.520 what are those? Think of these as your actual 00:03:03.520 --> 00:03:07.020 business tools, the database, the CRM, the analytics 00:03:07.020 --> 00:03:09.879 platform. They're the ones providing the capabilities 00:03:09.879 --> 00:03:13.280 or the data. Got it, the sources. And the second 00:03:13.280 --> 00:03:15.740 part. That's the MCP clients. These are your 00:03:15.740 --> 00:03:19.180 AI applications. Cloud, Chat, GPT, maybe a custom 00:03:19.180 --> 00:03:21.539 system you've built. They're the ones using the 00:03:21.539 --> 00:03:24.460 tools or consuming the data. And MCP is the bridge 00:03:24.460 --> 00:03:26.919 connecting them. Exactly. It handles all that 00:03:26.919 --> 00:03:30.039 translation work. So when your AI client says, 00:03:30.280 --> 00:03:32.979 hey, CRM, give me last quarter sales figures, 00:03:33.599 --> 00:03:36.520 MCP makes sure the CRM understands the request 00:03:36.520 --> 00:03:39.699 and sends back the data in a way the AI understands. 00:03:39.819 --> 00:03:42.379 It's that communication layer. OK. And you mentioned 00:03:42.379 --> 00:03:44.830 servers. How do those actually run? Are they 00:03:44.830 --> 00:03:47.009 complicated to set up? Well, you've got options, 00:03:47.069 --> 00:03:48.969 which is nice. There are remote servers, which 00:03:48.969 --> 00:03:51.270 are usually cloud -based. These tend to be easier, 00:03:51.330 --> 00:03:53.289 right? Often it's just pasting a link somewhere. 00:03:53.409 --> 00:03:55.490 They're managed by someone else. Easier setup, 00:03:55.729 --> 00:03:57.729 less maintenance for me. OK, what's the other 00:03:57.729 --> 00:04:00.310 option? Local servers. These run right on your 00:04:00.310 --> 00:04:02.830 own machine or within your company's network. 00:04:03.069 --> 00:04:06.419 Ah, so more control, maybe more security. Exactly. 00:04:06.599 --> 00:04:09.199 Your data doesn't leave your environment. But 00:04:09.199 --> 00:04:11.360 yeah, it does usually require a bit more technical 00:04:11.360 --> 00:04:13.699 setup. So it's a trade -off between convenience 00:04:13.699 --> 00:04:16.480 and control, really. OK. That clarifies the basic 00:04:16.480 --> 00:04:19.439 structure. So now, how do we actually make that 00:04:19.439 --> 00:04:22.980 connection between the AI client and the MCP 00:04:22.980 --> 00:04:24.899 server? You said there are different ways. Yeah, 00:04:24.939 --> 00:04:27.639 there are basically four main approaches, and 00:04:27.639 --> 00:04:29.779 choosing the right one depends on things like, 00:04:29.779 --> 00:04:32.120 you know, how easy you want it to be, your security 00:04:32.120 --> 00:04:34.540 needs, how flexible you need the connection to 00:04:34.540 --> 00:04:36.240 be. All right, let's walk through them. What's 00:04:36.240 --> 00:04:39.480 the first, maybe the easiest? That would be native 00:04:39.480 --> 00:04:41.699 integration. This is usually built right into 00:04:41.699 --> 00:04:44.480 the big AI platforms like ChatJepiT or Claude. 00:04:44.759 --> 00:04:47.459 Ah, so the AI platform itself already has connections 00:04:47.459 --> 00:04:50.100 ready to go for certain tools. Exactly. Things 00:04:50.100 --> 00:04:54.470 like Gmail. Google Calendar, Google Drive are 00:04:54.470 --> 00:04:56.930 common ones. It's definitely the simplest for 00:04:56.930 --> 00:05:00.490 non -technical folks. Zero setup, really, beyond 00:05:00.490 --> 00:05:02.930 just logging in and giving permission. And it's 00:05:02.930 --> 00:05:05.410 low risk because it's officially supported. OK, 00:05:05.550 --> 00:05:08.319 sounds great. Any downsides? Well... Sometimes 00:05:08.319 --> 00:05:11.040 the functionality can be a bit limited. For instance, 00:05:11.759 --> 00:05:14.160 ChatGPT's native connectors right now are mainly 00:05:14.160 --> 00:05:18.199 for what they call deep research, meaning it's 00:05:18.199 --> 00:05:20.519 great at pulling information like summarizing 00:05:20.519 --> 00:05:23.379 emails or finding docs, but maybe not so much 00:05:23.379 --> 00:05:26.379 at doing things like sending an email or creating 00:05:26.379 --> 00:05:29.439 an event, at least not yet. It's mostly read 00:05:29.439 --> 00:05:32.639 -only for now. Gotcha. Still useful, but limited 00:05:32.639 --> 00:05:34.870 scope. Okay, what's about the number two? Number 00:05:34.870 --> 00:05:38.209 two is using official MCP servers. This is what 00:05:38.209 --> 00:05:40.509 we generally recommend if native integration 00:05:40.509 --> 00:05:42.769 isn't available for the tool you need. Official 00:05:42.769 --> 00:05:45.009 servers. So these are built by the tool companies 00:05:45.009 --> 00:05:48.610 themselves, like Notion or HubSpot. Precisely. 00:05:48.889 --> 00:05:50.889 Major providers are building and maintaining 00:05:50.889 --> 00:05:53.589 their own MCP servers. You can usually find a 00:05:53.589 --> 00:05:56.769 list on the official MCP GitHub page. These can 00:05:56.769 --> 00:05:59.389 often be installed either locally or used remotely. 00:05:59.649 --> 00:06:02.079 And the big advantage here is... Reliability 00:06:02.079 --> 00:06:04.360 and security. Because they're built by the original 00:06:04.360 --> 00:06:06.480 company, you know they're likely to be more secure, 00:06:06.639 --> 00:06:08.639 better maintained, and kept up to date with the 00:06:08.639 --> 00:06:11.160 tool itself. It's the most trustworthy option 00:06:11.160 --> 00:06:13.439 after native integration. Okay, makes sense. 00:06:13.680 --> 00:06:16.420 Official is usually better. What if there's no 00:06:16.420 --> 00:06:19.600 native or official server for a tool I use? Ah, 00:06:19.920 --> 00:06:22.250 that brings us to option three. Community -built 00:06:22.250 --> 00:06:25.829 servers. Community -built, so made by other users 00:06:25.829 --> 00:06:28.870 or developers. Exactly. These can be great for 00:06:28.870 --> 00:06:31.089 niche tools or things that don't have official 00:06:31.089 --> 00:06:34.529 support yet, maybe something like Airtable. But, 00:06:34.569 --> 00:06:36.709 and this is important, you need to be cautious. 00:06:37.009 --> 00:06:39.269 Right, cautious. Well... Because they're not 00:06:39.269 --> 00:06:41.329 maintained by the original company, the risk 00:06:41.329 --> 00:06:43.569 is higher. There could be potential security 00:06:43.569 --> 00:06:46.250 issues, maybe data leaks. You really need to 00:06:46.250 --> 00:06:48.149 check who built it and how well it's maintained. 00:06:48.250 --> 00:06:50.389 It's not necessarily bad, just requires more 00:06:50.389 --> 00:06:52.709 due diligence. Right, proceed with caution. Okay, 00:06:52.970 --> 00:06:55.290 and the last method. The fourth way is building 00:06:55.290 --> 00:06:58.449 custom MCP servers. This is definitely the advanced 00:06:58.449 --> 00:07:01.310 option. For specific, maybe unique business needs. 00:07:01.550 --> 00:07:04.730 or connecting to internal proprietary systems. 00:07:05.029 --> 00:07:07.730 Exactly that. Or if you need very specific functions 00:07:07.730 --> 00:07:09.990 that aren't covered elsewhere, this usually requires 00:07:09.990 --> 00:07:12.370 some development skills, maybe using Python or 00:07:12.370 --> 00:07:15.709 JavaScript SDKs. Oh, okay. Sounds complex. It 00:07:15.709 --> 00:07:18.149 can be, but there are also no code platforms 00:07:18.149 --> 00:07:20.829 like N8n that can help you build these custom 00:07:20.829 --> 00:07:23.930 servers without writing actual code, which makes 00:07:23.930 --> 00:07:26.069 it a bit more accessible. Interesting. So... 00:07:25.790 --> 00:07:28.870 Quick recap, native is easiest, official is recommended 00:07:28.870 --> 00:07:32.269 for reliability, community needs caution, and 00:07:32.269 --> 00:07:35.370 custom is for specific advanced needs. You got 00:07:35.370 --> 00:07:38.069 it. And a key piece of advice, really a pro tip, 00:07:38.509 --> 00:07:40.670 always start with native if it does what you 00:07:40.670 --> 00:07:43.670 need. If not, look for an official server. Only 00:07:43.670 --> 00:07:45.870 go down the community or custom routes if you 00:07:45.870 --> 00:07:48.470 absolutely have to. Think crucially. Crucially, 00:07:48.610 --> 00:07:51.250 whatever you connect, always grant the absolute 00:07:51.250 --> 00:07:54.660 minimum permissions necessary. If the AI only 00:07:54.660 --> 00:07:56.759 needs to read data, don't give it permission 00:07:56.759 --> 00:07:59.060 to write or delete. Start with least privilege. 00:07:59.439 --> 00:08:01.680 Always. Absolutely critical for security. Okay, 00:08:01.680 --> 00:08:04.040 let's make this more concrete. Can we walk through 00:08:04.040 --> 00:08:06.079 the idea of setting one of these up? Not a full 00:08:06.079 --> 00:08:08.600 tutorial, but the principle? Sure. Let's take 00:08:08.600 --> 00:08:11.319 that native integration with ChatGPT first. It's 00:08:11.319 --> 00:08:13.540 designed to be simple. You'd typically go into 00:08:13.540 --> 00:08:16.100 your ChatGPT settings, find a section like connectors 00:08:16.100 --> 00:08:18.639 or integrations. And you'd see things like Gmail, 00:08:19.139 --> 00:08:21.540 Calendar there? Yeah. you'd click the one you 00:08:21.540 --> 00:08:24.459 want, say Gmail. It'll likely prompt you to log 00:08:24.459 --> 00:08:27.120 in to your Google account and then ask you to 00:08:27.120 --> 00:08:30.279 approve certain permissions like allow chat GPT 00:08:30.279 --> 00:08:32.919 to read your emails. Okay, pretty standard permission 00:08:32.919 --> 00:08:35.500 stuff. And then what? Does Gmail show up like 00:08:35.500 --> 00:08:39.080 a plugin? Not usually, no. Instead, when you 00:08:39.080 --> 00:08:41.419 use a specific function within ChatGPT, maybe 00:08:41.419 --> 00:08:44.019 one called deep research, you'll see an option 00:08:44.019 --> 00:08:46.240 to toggle on your connected Gmail account for 00:08:46.240 --> 00:08:49.159 that specific query. Oh, so you enable it when 00:08:49.159 --> 00:08:51.720 you need it for a task. Exactly. So you could 00:08:51.720 --> 00:08:54.500 then ask something like, can you find all the 00:08:54.500 --> 00:08:56.759 newsletters about AI I received in the last six 00:08:56.759 --> 00:08:59.580 months and summarize them? And ChatGPT would 00:08:59.580 --> 00:09:01.580 use that Gmail connection to do the research. 00:09:01.700 --> 00:09:04.019 That's powerful. Turns it into a research assistant 00:09:04.019 --> 00:09:06.610 for your own info. Definitely. especially for 00:09:06.610 --> 00:09:09.009 companies with lots of internal documents or 00:09:09.009 --> 00:09:11.429 emails. OK, what about setting up an official 00:09:11.429 --> 00:09:13.350 server? You mentioned that might involve a bit 00:09:13.350 --> 00:09:15.750 more configuration, maybe with something like 00:09:15.750 --> 00:09:18.330 Cloud Desktop. Yeah, it's often a multi -step 00:09:18.330 --> 00:09:20.990 process, but logical. Let's use Notion as an 00:09:20.990 --> 00:09:23.629 example. First, you'd go into your Notion settings 00:09:23.629 --> 00:09:26.370 and create a new integration or service connection. 00:09:26.450 --> 00:09:28.009 You tell Notion you want to connect something 00:09:28.009 --> 00:09:30.509 to it. Right. You'd give it a name, configure 00:09:30.509 --> 00:09:33.549 what it can do again, minimum permissions, maybe 00:09:33.549 --> 00:09:36.970 only allow it to read specific pages or databases, 00:09:37.330 --> 00:09:39.789 not your whole Notion workspace. Okay, lock it 00:09:39.789 --> 00:09:42.330 down. Then Notion will generate a secret key, 00:09:42.610 --> 00:09:45.549 like an API token. You copy that token. Got the 00:09:45.549 --> 00:09:48.210 key, now what? Now you go to your AI client, 00:09:48.490 --> 00:09:51.669 say Claw Desktop. There's usually a developer 00:09:51.669 --> 00:09:54.389 or settings area where you can edit a configuration 00:09:54.389 --> 00:09:56.820 file. It sounds technical, but it's often just 00:09:56.820 --> 00:09:58.740 text. And you paste the Notion token in there? 00:09:58.820 --> 00:10:01.639 Pretty much. You'd find the section for MeICP 00:10:01.639 --> 00:10:03.879 servers, paste in some configuration details 00:10:03.879 --> 00:10:06.279 provided by Notion's MCP server instructions, 00:10:06.620 --> 00:10:09.259 and replace a placeholder with your unique API 00:10:09.259 --> 00:10:12.779 token. Then save the file, maybe restart Claude. 00:10:12.799 --> 00:10:15.159 And if you did it right... Notion should appear 00:10:15.159 --> 00:10:18.179 as a tool Claude can now use directly. You could 00:10:18.179 --> 00:10:20.980 then ask Claude, draft a social media plan for 00:10:20.980 --> 00:10:23.539 the new product launch using the brand guidelines 00:10:23.539 --> 00:10:26.159 document in our Notion. And it would access that 00:10:26.159 --> 00:10:28.299 specific Notion page and use the guidelines. 00:10:28.500 --> 00:10:31.840 That's the idea. It seamlessly pulls your company's 00:10:31.840 --> 00:10:34.500 knowledge into the AI's workflow. It's incredibly 00:10:34.500 --> 00:10:36.860 useful for keeping things consistent. I can see 00:10:36.860 --> 00:10:39.659 that. Okay, one more example. The custom route. 00:10:39.879 --> 00:10:42.159 Maybe using that NAN platform you mentioned. 00:10:42.639 --> 00:10:44.700 Let's say I want to connect to Google Analytics 00:10:44.700 --> 00:10:47.740 data. Right. So NAN is a workflow automation 00:10:47.740 --> 00:10:50.159 tool. You'd start by creating a new workflow 00:10:50.159 --> 00:10:52.960 in NAN. The trigger for this workflow would be 00:10:52.960 --> 00:10:55.919 MCP server. So the workflow starts when the AI 00:10:55.919 --> 00:10:59.799 asks for something via MCP. Exactly. Then within 00:10:59.799 --> 00:11:02.600 the workflow, you'd add a node for Google Analytics. 00:11:03.019 --> 00:11:05.399 You connect NAN to your Google Analytics account 00:11:05.399 --> 00:11:07.879 and configure exactly what data you want the 00:11:07.879 --> 00:11:11.039 AI to be able to access. Like maybe website traffic 00:11:11.039 --> 00:11:13.360 from the last 30 days broken down by source? 00:11:13.860 --> 00:11:16.279 Precisely. You set the parameters, date ranges, 00:11:16.620 --> 00:11:19.059 metrics, dimensions. Once you've built this workflow 00:11:19.059 --> 00:11:22.639 and activated it, the NAN and MCP server node 00:11:22.639 --> 00:11:25.659 gives you a special URL, a production URL. And 00:11:25.659 --> 00:11:28.259 that URL is what I give to the AI. Yes. You'd 00:11:28.259 --> 00:11:30.580 go into your AI client, maybe the Cloud web app 00:11:30.580 --> 00:11:33.759 this time, find the setting for add custom integration 00:11:33.759 --> 00:11:37.879 or similar, and paste that NAN URL in. Save it. 00:11:38.080 --> 00:11:41.279 And suddenly, my AI can talk to my specific Google 00:11:41.279 --> 00:11:45.120 Analytics setup via an 8M. Bingo. You could then 00:11:45.120 --> 00:11:47.679 ask your AI, generate a quick dashboard showing 00:11:47.679 --> 00:11:49.700 website traffic trends from Google Analytics 00:11:49.700 --> 00:11:52.500 for the past month, and Claude, through N8AN, 00:11:52.799 --> 00:11:55.340 fetches that specific data and presents it. Wow. 00:11:55.340 --> 00:11:57.600 That really opens things up. Connecting to almost 00:11:57.600 --> 00:11:59.840 anything with an API becomes possible. It really 00:11:59.840 --> 00:12:02.039 does. It bridges the gap for tools without official 00:12:02.039 --> 00:12:04.480 support or for very custom data needs. This is 00:12:04.480 --> 00:12:07.139 great. So with all these ways to connect, which 00:12:07.139 --> 00:12:09.840 AI platforms are actually good at using MCP right 00:12:09.840 --> 00:12:12.600 now? Is the support widespread? It's evolving 00:12:12.600 --> 00:12:15.039 quickly. But there are definitely leaders. Claude, 00:12:15.139 --> 00:12:17.299 I'd say, currently has the most comprehensive 00:12:17.299 --> 00:12:19.779 support. It handles local and remote servers 00:12:19.779 --> 00:12:22.620 well. It can do both read and write operations 00:12:22.620 --> 00:12:25.600 in many cases. And they seem really focused on 00:12:25.600 --> 00:12:28.879 expanding custom integration support. It feels 00:12:28.879 --> 00:12:31.399 pretty baked into the experience. OK. Claude 00:12:31.399 --> 00:12:34.639 is strong. What about ChatGPT? ChatGPT is definitely 00:12:34.639 --> 00:12:36.740 making progress. They have those native connectors 00:12:36.740 --> 00:12:39.220 for popular tools, which is great for ease of 00:12:39.220 --> 00:12:42.120 use. But as we mentioned, it's still often limited 00:12:42.120 --> 00:12:45.570 to that deep research read -only mode. So more 00:12:45.570 --> 00:12:47.990 about getting info out than putting info in or 00:12:47.990 --> 00:12:50.629 taking action. Generally, yes, for the native 00:12:50.629 --> 00:12:53.169 ones right now. However, they are rolling out 00:12:53.169 --> 00:12:56.230 support for custom MCP servers, especially on 00:12:56.230 --> 00:12:59.929 their paid plans, like Pro and Teams. So that 00:12:59.929 --> 00:13:02.370 capability is growing. OK, good to know. And 00:13:02.370 --> 00:13:06.129 Gemini, Google's AI. With Gemini, MCP support 00:13:06.129 --> 00:13:08.029 seems to be mainly available if you're using 00:13:08.029 --> 00:13:10.889 the Gemini API directly, like through their SDKs 00:13:10.889 --> 00:13:13.190 for developers. Ah, so not really a simple click 00:13:13.190 --> 00:13:15.129 and connect thing on the main Gemini website 00:13:15.129 --> 00:13:17.850 or app yet? Not typically, no. It requires more 00:13:17.850 --> 00:13:20.250 technical implementation at the moment. Got it. 00:13:20.529 --> 00:13:22.279 Any others worth mentioning? Yeah, you're seeing 00:13:22.279 --> 00:13:25.120 other platforms pop up too. Tools like Windsurf, 00:13:26.299 --> 00:13:29.559 Cursor. They're also integrating MCP support. 00:13:29.679 --> 00:13:31.639 It's definitely becoming a feature that more 00:13:31.639 --> 00:13:34.500 and more platforms are recognizing as essential. 00:13:34.899 --> 00:13:37.860 The ecosystem is growing fast. That's encouraging. 00:13:38.139 --> 00:13:39.840 OK, we touched on this earlier, but let's really 00:13:39.840 --> 00:13:42.919 hammer it home. Security. When you're connecting 00:13:42.919 --> 00:13:45.299 your AI to all your sensitive business data, 00:13:45.759 --> 00:13:48.340 security has to be front and center, right? Absolutely 00:13:48.340 --> 00:13:50.779 non -negotiable. It has to be priority number 00:13:50.779 --> 00:13:54.200 one. So what are the key security best practices 00:13:54.200 --> 00:13:57.139 people absolutely most follow? First, as we said, 00:13:57.539 --> 00:14:00.059 minimum necessary permissions. Always start there. 00:14:00.220 --> 00:14:02.720 Don't grant delete access if read is all that's 00:14:02.720 --> 00:14:05.379 needed. And don't just set it and forget it regularly. 00:14:05.500 --> 00:14:07.340 Review and audit the permissions you've granted. 00:14:07.519 --> 00:14:10.080 Makes sense. What else? Choose reliable sources. 00:14:10.659 --> 00:14:13.759 Strongly prioritize those official MCP servers 00:14:13.759 --> 00:14:16.320 from the tool vendors themselves over community 00:14:16.320 --> 00:14:18.419 builds whenever possible. They're just inherently 00:14:18.419 --> 00:14:20.740 more trustworthy and better maintained. Okay, 00:14:20.879 --> 00:14:22.919 stick to official channels if you can't. Also, 00:14:23.200 --> 00:14:26.330 really understand the data access. Know exactly 00:14:26.330 --> 00:14:29.269 what data each connected tool or MCP server can 00:14:29.269 --> 00:14:32.110 see. Don't make assumptions. Read the documentation. 00:14:32.870 --> 00:14:35.970 And finally, regular maintenance. Keep any local 00:14:35.970 --> 00:14:39.269 MCP servers updated, patch them, and periodically 00:14:39.269 --> 00:14:41.610 check your integration settings everywhere. Good 00:14:41.610 --> 00:14:44.250 hygiene, basically. Keep things clean and updated. 00:14:44.870 --> 00:14:47.129 Now, on the flip side, what are the common traps, 00:14:47.509 --> 00:14:49.669 the mistakes people make that we should actively 00:14:49.669 --> 00:14:53.570 avoid? The biggest one, hands down, is over -granting 00:14:53.570 --> 00:14:56.830 permissions. It's so easy to just click allow 00:14:56.830 --> 00:14:59.090 all for convenience, but that's a huge risk. 00:14:59.210 --> 00:15:02.000 Be granular from the start. resist the urge to 00:15:02.000 --> 00:15:04.740 give it the keys to the kingdom. Exactly. Another 00:15:04.740 --> 00:15:06.960 common mistake is ignoring official servers. 00:15:07.259 --> 00:15:09.240 People sometimes default to building a custom 00:15:09.240 --> 00:15:11.559 solution or using a community one out of habit. 00:15:11.980 --> 00:15:14.360 Even when a perfectly good secure official server 00:15:14.360 --> 00:15:16.659 exists, always check for an official one first. 00:15:16.740 --> 00:15:18.480 Don't reinvent the wheel if you don't have to, 00:15:18.580 --> 00:15:20.879 especially if the official wheel is safer. Right. 00:15:21.080 --> 00:15:22.980 And then there's the issue of cramming too many 00:15:22.980 --> 00:15:24.899 tools onto one connection. What do you mean? 00:15:25.220 --> 00:15:28.200 Trying to connect, say, seven different types 00:15:28.200 --> 00:15:32.860 of tools through a single custom MCP server setup. 00:15:33.340 --> 00:15:35.720 It sounds efficient, but it can actually confuse 00:15:35.720 --> 00:15:39.440 the AI. If you ask it to summarize recent activity, 00:15:40.019 --> 00:15:43.080 it might not know if you mean emails or CRM updates 00:15:43.080 --> 00:15:45.840 or project tasks because it has too many options 00:15:45.840 --> 00:15:48.639 linked through that one channel. It dilutes the 00:15:48.639 --> 00:15:52.279 AI's focus. We generally advise sticking to maybe 00:15:52.279 --> 00:15:55.080 five or fewer distinct tool times per server 00:15:55.080 --> 00:15:57.240 connection for clarity. Interesting. So give 00:15:57.240 --> 00:16:00.159 the AI focused access, not just a massive jumble 00:16:00.159 --> 00:16:02.919 of everything. Precisely. And the last big mistake, 00:16:03.720 --> 00:16:06.240 skipping the documentation. Seriously. People 00:16:06.240 --> 00:16:08.440 run into problems because they miss one small 00:16:08.440 --> 00:16:10.639 configuration detail mentioned in the setup guide. 00:16:11.049 --> 00:16:13.090 Read it carefully. It can save you major headaches, 00:16:13.490 --> 00:16:15.529 especially security ones. OK, excellent advice. 00:16:15.570 --> 00:16:17.350 So we've covered the tech, the setup, the security. 00:16:17.789 --> 00:16:20.590 Let's talk impact. Where are we seeing MCP really 00:16:20.590 --> 00:16:22.009 make a difference in the real world? How are 00:16:22.009 --> 00:16:24.090 teams using this today? Oh, the use cases are 00:16:24.090 --> 00:16:26.210 fantastic. Take marketing teams, for example. 00:16:26.210 --> 00:16:28.029 Yeah, what are they doing? Think about automated 00:16:28.029 --> 00:16:30.629 reporting. Instead of someone manually pulling 00:16:30.629 --> 00:16:33.529 data from Google Analytics, then HubSpot, then 00:16:33.529 --> 00:16:36.669 maybe Facebook ads, the AI can connect to all 00:16:36.669 --> 00:16:40.779 three via MCP. It automatically generates a consolidated 00:16:40.779 --> 00:16:43.639 weekly performance report, maybe even pulls out 00:16:43.639 --> 00:16:46.879 key insights, and emails a summary. Wow, that 00:16:46.879 --> 00:16:49.419 saves a ton of manual work. Huge amounts. It 00:16:49.419 --> 00:16:51.980 frees up marketers to actually analyze and strategize, 00:16:52.000 --> 00:16:54.440 not just compile numbers. Another big one is 00:16:54.440 --> 00:16:58.080 content creation. The AI can access brand guidelines 00:16:58.080 --> 00:17:00.720 stored in Notion or Google Drive. So it can write 00:17:00.720 --> 00:17:03.360 stuff that's actually on brand. Exactly. generate 00:17:03.360 --> 00:17:06.279 content briefs, draft social media posts, write 00:17:06.279 --> 00:17:09.460 initial email copy, all adhering to the company's 00:17:09.460 --> 00:17:11.980 specific voice, style, and messaging guidelines 00:17:11.980 --> 00:17:14.039 because it can read them directly. OK, that's 00:17:14.039 --> 00:17:16.400 powerful for consistency. What about sales teams? 00:17:16.579 --> 00:17:18.940 For sales, lead research becomes turbocharged. 00:17:19.500 --> 00:17:21.920 An AI connected to your CRM, like Salesforce 00:17:21.920 --> 00:17:24.660 and maybe LinkedIn via an MCP connection, can 00:17:24.660 --> 00:17:27.099 automatically gather info on prospects. So what 00:17:27.099 --> 00:17:28.400 does the background check for the sales rep? 00:17:28.559 --> 00:17:32.140 Yeah, it summarizes key info, identifies potential 00:17:32.140 --> 00:17:35.079 talking points, maybe even suggests personalized 00:17:35.079 --> 00:17:37.640 outreach angles based on the prospect's activity 00:17:37.640 --> 00:17:40.420 or company news. It makes outreach much more 00:17:40.420 --> 00:17:43.759 effective. And related to that is email automation. 00:17:43.960 --> 00:17:46.900 Going beyond just mail merge. Way beyond. Using 00:17:46.900 --> 00:17:50.160 data from the CRM, the AI can generate highly 00:17:50.160 --> 00:17:53.240 personalized outreach emails. Not just inserting 00:17:53.240 --> 00:17:56.140 a name, but referencing specific interactions, 00:17:56.259 --> 00:17:58.410 needs, or interests pulled directly from the 00:17:58.410 --> 00:18:01.049 customer record. It's personalization at scale. 00:18:01.230 --> 00:18:03.130 I can see how that would improve response rates 00:18:03.130 --> 00:18:06.349 and customer support. Huge potential there too, 00:18:06.509 --> 00:18:08.950 mainly through quick information retrieval. Imagine 00:18:08.950 --> 00:18:11.329 an AI connected to your help desk system, like 00:18:11.329 --> 00:18:13.789 Zendesk, and your internal knowledge base. So 00:18:13.789 --> 00:18:16.259 when an agent gets a query... The AI instantly 00:18:16.259 --> 00:18:18.640 pulls up that customer's history, details about 00:18:18.640 --> 00:18:20.980 the products they use, and relevant troubleshooting 00:18:20.980 --> 00:18:22.920 articles or solutions from the knowledge base. 00:18:23.380 --> 00:18:25.619 All right there for the agent. Faster resolution, 00:18:26.000 --> 00:18:28.599 happier customers, more efficient agents. Exactly. 00:18:29.039 --> 00:18:31.259 It provides the agent with instant context and 00:18:31.259 --> 00:18:33.900 answers, dramatically improving the support experience 00:18:33.900 --> 00:18:36.259 for everyone. These examples really bring it 00:18:36.259 --> 00:18:39.099 to life. It's clear MCP is already enabling some 00:18:39.099 --> 00:18:42.359 amazing things. What's next? Where's this technology 00:18:42.359 --> 00:18:44.880 headed? Oh, it's moving incredibly fast. We're 00:18:44.880 --> 00:18:48.109 seeing platform support just exploding, more 00:18:48.109 --> 00:18:51.309 AI clients adding MCP, more tool providers building 00:18:51.309 --> 00:18:53.509 official servers. It's becoming table stakes. 00:18:53.990 --> 00:18:56.710 So broader adoption. Definitely. And we're seeing 00:18:56.710 --> 00:18:59.490 enhanced functionality. Those read -only limitations 00:18:59.490 --> 00:19:02.269 we talked about, they're disappearing. Full read 00:19:02.269 --> 00:19:04.410 -write capabilities are becoming much more common, 00:19:04.609 --> 00:19:06.809 allowing AI to not just see data but actively 00:19:06.809 --> 00:19:09.690 work with it across systems. More action, less 00:19:09.690 --> 00:19:12.049 just observation. Right. We're also expecting 00:19:12.049 --> 00:19:14.329 more advanced enterprise features, things focused 00:19:14.329 --> 00:19:17.490 on robust security controls, compliance auditing, 00:19:17.869 --> 00:19:20.569 granular governance, stuff larger organizations 00:19:20.569 --> 00:19:22.910 absolutely need. Makes sense for wider business 00:19:22.910 --> 00:19:25.210 adoption. And just continued standardization. 00:19:25.420 --> 00:19:27.980 As more providers build official MCP servers, 00:19:28.119 --> 00:19:31.700 it creates a more reliable, secure, and interoperable 00:19:31.700 --> 00:19:34.500 ecosystem for everyone, reducing the reliance 00:19:34.500 --> 00:19:36.960 on those riskier community builds. So wrapping 00:19:36.960 --> 00:19:39.359 this all up, it feels like MCP is really the 00:19:39.359 --> 00:19:42.799 key to unlocking that next level of AI capability 00:19:42.799 --> 00:19:45.859 in business. It absolutely is. It's what transforms 00:19:45.859 --> 00:19:48.460 AI from being just a clever conversationalist 00:19:48.460 --> 00:19:51.579 into a truly integrated, intelligent partner 00:19:51.579 --> 00:19:53.920 that understands and interacts with your actual 00:19:53.920 --> 00:19:56.309 business processes. and data. So for listeners 00:19:56.309 --> 00:19:58.529 wanting to get started, what's the final takeaway? 00:19:58.930 --> 00:20:01.750 The advice? Start simple. Play around with the 00:20:01.750 --> 00:20:03.910 native integrations first. See what they can 00:20:03.910 --> 00:20:06.210 do. Get comfortable with the concept. See the 00:20:06.210 --> 00:20:08.430 value firsthand. Dip your toes in the water. 00:20:08.549 --> 00:20:11.869 Exactly. Then, as your needs grow, look towards 00:20:11.869 --> 00:20:14.789 those official servers. Only venture into custom 00:20:14.789 --> 00:20:17.150 solutions when you have a clear, specific need 00:20:17.150 --> 00:20:20.190 and understand the implications. And always, 00:20:20.470 --> 00:20:23.710 always put security first. Start small. Prove 00:20:23.710 --> 00:20:26.440 the value. and then scale up carefully. Sound 00:20:26.440 --> 00:20:29.180 advice. It really feels like the future of practical 00:20:29.180 --> 00:20:31.759 AI in business isn't just about the AI model 00:20:31.759 --> 00:20:34.000 itself, but about how well it connects to everything 00:20:34.000 --> 00:20:36.279 else. That's the core of it. Integration is the 00:20:36.279 --> 00:20:39.400 intelligence multiplier, and MCP is the standard 00:20:39.400 --> 00:20:41.480 making that integration seamless and scalable. 00:20:41.819 --> 00:20:44.599 So maybe the final thought for everyone listening 00:20:44.599 --> 00:20:47.579 is this. The question isn't if you should adopt 00:20:47.579 --> 00:20:50.299 MCP, but really, how quickly can you start using 00:20:50.299 --> 00:20:52.859 it to transform your AI from just a chatbot into 00:20:52.859 --> 00:20:54.279 a truly intelligent business partner?