Okay, I've got a few minutes to do some technical stuff on MCP that is like optional. Many of you 好的，我有几分钟时间在 MCP 上做一些技术工作，这就像可选的。你们中的许多人
may know this already. Some of you may not know and may not care because it's not necessary to 可能已经知道了。你们中的一些人可能不知道也可能不关心，因为没有必要
get through the using it. But for those that do care, the next couple of minutes are for you. 通过使用它。但对于那些关心的人来说，接下来的几分钟是给你的。
Some technicalities about MCP. The terminology isn't that important for using it in Cloud Code. 有关 MCP 的一些技术细节。对于在 Cloud Code 中使用它来说，术语并不那么重要。
We're not going to build MCP, we're going to just use it. But you might as well know these are 我们不会构建 MCP，我们只会使用它。但你可能也知道这些是
terms you've probably already heard. There are these three things that people talk about with 您可能已经听说过的术语。人们谈论的有这三件事
MCP. The MCP host, the MCP client, the MCP server. The MCP host is the name of the overall MCP。 MCP 主机、MCP 客户端、MCP 服务器。 MCP主机是整体的名称
AI application which is running, which needs to call tools. And so Cloud Code is an example of AI应用程序正在运行，需要调用工具。 Cloud Code 就是一个例子
an MCP host. ChatGBT is an MCP host. If you're writing your own agentic app like we do in my MCP 主机。 ChatGBT 是 MCP 主机。如果您正在编写自己的代理应用程序，就像我们在我的文章中所做的那样
agentic track of my AI engineer course, we use OpenAI Agents SDK and that as an application, 我的人工智能工程师课程的代理轨迹，我们使用 OpenAI Agents SDK 并将其作为应用程序，
the software, is an MCP host. That's the MCP host. The MCP client is a bit of code that runs 该软件是一个MCP主机。那是 MCP 主机。 MCP 客户端是一段运行的代码
within the MCP host where there's one of them for each of the sets of tools that you're using. 在 MCP 主机内，您正在使用的每组工具都有一个对应的工具。
And that is again, that is something that's part baked into a Cloud Code or OpenAI Agents SDK 再说一遍，这是一部分融入到 Cloud Code 或 OpenAI Agents SDK 中的东西
or ChatGBT and so on. And then finally, the thing that you actually really care about 或ChatGBT等。最后，你真正关心的事情
is called the MCP server. And that is the thing that manages the set of tools 称为 MCP 服务器。这就是管理工具集的东西
written by somebody else. So what they give you is an MCP server. An MCP server for browsing the 别人写的。所以他们给你的是一个MCP服务器。用于浏览的 MCP 服务器
internet. An MCP server for looking up stock prices. These are each MCP servers. And they 互联网。用于查找股票价格的 MCP 服务器。这些都是 MCP 服务器。而他们
give you a little description of it. And that's what you take and you give it to your MCP host 给你一些描述。这就是您所获取的并将其提供给您的 MCP 主机
like Cloud Code. And it takes that description of an MCP server and it knows what to do. 比如云代码。它接受 MCP 服务器的描述并且知道要做什么。
It knows how to set up a client. It knows how to launch that server. It knows how to run it. 它知道如何设置客户端。它知道如何启动该服务器。它知道如何运行它。
That's what's going on when you use MCP. And then the other technicality is that they can 这就是使用 MCP 时发生的情况。另一个技术问题是他们可以
run in two different modes, perhaps two different techniques. They're known as the different 以两种不同的模式运行，也许是两种不同的技术。他们被称为不同的
transports. It can run locally, in which case it's running on your computer. The MCP server, 运输。它可以在本地运行，在这种情况下，它在您的计算机上运行。 MCP 服务器，
this thing which is going to look up market data or whatever, is running on your computer. Or it 这个用来查找市场数据或其他什么的东西正在你的计算机上运行。或者它
can run remotely, which means it's running up on the cloud. So if it's a Jira-related one, maybe 可以远程运行，这意味着它在云端运行。所以如果它是与 Jira 相关的，也许
Atlassian is running it. If it's GitHub, we'll use GitHub. Maybe Microsoft or GitHub are running it Atlassian 正在运行它。如果是 GitHub，我们就使用 GitHub。也许 Microsoft 或 GitHub 正在运行它
on their servers and you're connecting remotely to it. And even in that sort of sub-device, there 在他们的服务器上，并且您正在远程连接到它。即使在那种子设备中，也有
are two different techniques. One is called SSE and is now a legacy. It's been replaced, but still 是两种不同的技术。其中一个称为 SSE，现已成为遗产。已经换了，但是还是这样
works. And one of them is streamable HTTP, which is the new way. SSE is deprecated, but you can 作品。其中之一是流式 HTTP，这是一种新方式。 SSE 已弃用，但您可以
still use it. And the thing is that there is a big source of confusion about this that I want to 仍然使用它。问题是，这件事有一个很大的混乱根源，我想
try and nix right now. So it's a huge source of confusion that some people have. When I say 现在就尝试拒绝。所以这是一些人感到困惑的一个巨大根源。当我说
that these are local or remote MCP servers, I'm referring, as I say, to where the MCP servers 这些是本地或远程 MCP 服务器，正如我所说，我指的是 MCP 服务器所在的位置
actually run on your computer or running remotely. That's where the thing that figures 实际上在您的计算机上运行或远程运行。这就是问题的所在
out what tools you've got access to and what you can do with those tools. But often the 了解您可以使用哪些工具以及可以使用这些工具做什么。但往往
implementation of those tools involves making a web call. So just because the tools are running 这些工具的实施涉及进行网络调用。所以只是因为工具正在运行
on your computer doesn't mean you're not accessing online services in some way. For example, the 在您的计算机上并不意味着您无法以某种方式访问​​在线服务。例如，
market data one that we're going to try in a second that looks up stock prices. It's a local 我们稍后将尝试查找股票价格的市场数据。这是一个本地人
tool that runs, the MCP server runs on my computer, but for sure it's looking up stock prices on the 运行的工具，MCP 服务器在我的计算机上运行，​​但可以肯定的是，它正在查找股票价格
internet. The stock prices aren't on my computer. So just because it runs locally doesn't mean it's 互联网。我的电脑上没有股票价格。因此，仅仅因为它在本地运行并不意味着它是
not connecting remotely in some way as part of its implementation. So that's one source of 作为其实施的一部分，不以某种方式远程连接。所以这是一个来源
confusion. And the other confusion is that people sometimes think that because it's a local MCP 困惑。另一个令人困惑的是，人们有时会认为这是因为它是当地的 MCP
server, and by the way, most MCP servers are local MCP servers, they think in some way that that's 服务器，顺便说一句，大多数 MCP 服务器都是本地 MCP 服务器，他们在某种程度上认为这是
not real MCP, that you're not sharing, it wasn't written by somebody else. But that's all a 不是真正的 MCP，您没有分享，它不是由其他人编写的。但这只是一个
confusion. A local, it's still completely, all the benefits of MCP applies. That code that's 困惑。对于本地来说，它仍然完全适用，MCP 的所有好处都适用。那个代码就是
running locally will still have been fetched from a remote repository. It's been installed 本地运行仍将从远程存储库获取。已经安装了
probably either with something like PIP or with UV, a modern version, or with something like 可能使用 PIP 或 UV（现代版本）或类似的东西
MPX, if it's a node, a JavaScript program, it's been installed locally in your computer, but from MPX，如果它是一个节点，一个 JavaScript 程序，它已本地安装在您的计算机中，但来自
a shared place, and then it's running on your computer. So it's just about where it actually 一个共享位置，然后它就在您的计算机上运行。所以这只是关于它实际上在哪里
runs, but it's still shared code, a shared tool written by somebody else. It's just about whether 运行，但它仍然是共享代码，是其他人编写的共享工具。这只是关于是否
you're accessing it on the cloud or accessing it running on your computer. So as I say, not super 您正在云上访问它或访问在您的计算机上运行的它。 So as I say, not super
important, but I do like to bring clarity to this. And just so that you understand, most MCP servers 很重要，但我确实想澄清这一点。让您了解一下，大多数 MCP 服务器
actually are local, but you've still got all the benefits of MCP, and it still might well be 实际上是本地的，但您仍然可以获得 MCP 的所有好处，而且它仍然很可能
connecting online. And that's the difference between MCP host, MCP client, and MCP server. 在线连接。这就是 MCP 主机、MCP 客户端和 MCP 服务器之间的区别。
And often when you hear someone saying, I'm using this MCP, that's shorthand for saying I'm using 通常当你听到有人说“我正在使用这个 MCP”时，这是“我正在使用”的简写
this MCP server. So at this point, we're going to go and experiment with MCP servers before we move 这个MCP服务器。所以此时，我们将在移动之前先尝试一下 MCP 服务器
on to skills. One of the things that's kind of odd, that's sort of funky about MCP, is that it's not a 关于技能。 MCP 有点奇怪的一点是，它不是一个
super standard way to discover MCP servers that other people have written. It's given you this 发现其他人编写的 MCP 服务器的超级标准方法。它给了你这个
great way to connect together, but it's not like there's been a kind of sort of everyone 这是联系在一起的好方法，但并不是每个人都有某种联系
converging on one place to find MCP servers. There are a bunch of different marketplace sites, 汇聚一处寻找 MCP 服务器。有很多不同的市场网站，
a lot of them, and there are thousands, tens of thousands, lots of MCP servers available, 很多，并且有数千、数万、大量可用的 MCP 服务器，
including very popular ones. But it's a little bit of a wild west to understand how to navigate them. 包括非常受欢迎的。但了解如何驾驭它们有点像在狂野西部。
And of course, I will put links in the resources, and this stuff changes all the time. But let's go 当然，我会在资源中添加链接，而且这些内容一直在变化。但我们走吧
and look at some right now, and then we'll use a couple of them in Cloud Code. Now, this first site 现在就看一些，然后我们将在 Cloud Code 中使用其中的一些。现在，第一个网站
is called registry.modelcontextprotocol.io. That is the official MCP website. And MCP, 称为registry.modelcontextprotocol.io。那是MCP的官方网站。还有MCP，
by the way, I should say at this point, Anthropic has donated it, as they say, to the Linux Foundation. 顺便说一句，我现在应该说，正如他们所说，Anthropic 已将其捐赠给 Linux 基金会。
So they've now made sure that it's got complete open source governance. So this is the 所以他们现在已经确保它有完整的开源治理。所以这就是
website for the official MCP registry. But in my opinion, there's some crickets around this. MCP 官方注册网站。但在我看来，这方面有一些蟋蟀。
It's a bit quiet. It's not actually the most active of the places that you go to find MCP 有点安静。它实际上并不是您寻找 MCP 的最活跃的地方
servers, perhaps because there's not enough. It's kind of everything is here, and it's kind of hard 服务器，也许是因为不够。好像一切都在这里，但有点困难
to navigate around. Another place you could go is a website that is part of a GitHub repo 导航。您可以访问的另一个地方是属于 GitHub 存储库一部分的网站
that Anthropic put together with reference MCP servers. It has some ones that they wrote Anthropic 将其与参考 MCP 服务器放在一起。其中有一些是他们写的
in the early days that I've used a lot, that lots of people use. And then there are some ones that 早期我用过很多，很多人也用过。然后还有一些
are official ones made by third parties, a great place to go for ones that have kind of been 是第三方制作的官方产品，对于那些已经被使用过的产品来说是一个好地方
blessed by Anthropic here. So I often start by looking on this list and experimenting with some 在这里受到人性的祝福。所以我经常首先查看这个列表并尝试一些
of these. But there are, separate to this, some websites that operate marketplaces, a place where 这些。但除此之外，还有一些运营市场的网站，
people can post their MCP servers, where people can write kind of reviews and there are ratings 人们可以发布他们的 MCP 服务器，在那里人们可以写评论并且有评级
and things like that. And those are the most active places to go to get your MCP information. 诸如此类的事情。这些是获取 MCP 信息最活跃的地方。
Let's look at three of them now. So first up is this one here, mcp.so. And again, I'll have links 现在让我们看看其中的三个。首先是这个，mcp.so。再说一次，我会有链接
to these in the resources. And you can see that it's like a marketplace that shows the different 资源中的这些。你可以看到它就像一个展示不同产品的市场
MCP servers that are available with like a search and keywords and tags and all the usual stuff. MCP 服务器可提供搜索、关键字、标签以及所有常用内容。
They've got 17,000 MCP servers. That's a lot. Let me bring up one that we'll look at in a second 他们有 17,000 台 MCP 服务器。就这么多了。让我提出一个我们稍后会讨论的
that's very popular for using in Cloud Code, which is called Context 7. And the idea is that one of 这在 Cloud Code 中非常流行，称为 Context 7。其想法是
the problems with Cloud Code is that it doesn't have up-to-date information about APIs and often Cloud Code 的问题在于它没有有关 API 的最新信息，并且经常
assumes APIs are current as of its training cutoff. And so it's useful to be able to equip 假设 API 在训练截止时是最新的。所以能够装备是很有用的
it with a tool that will inform it about the latest APIs. And that's what Context 7 does. 它有一个工具可以通知它最新的 API。这就是 Context 7 所做的。
It allows the LLM to, it allows Claude Opus to ask, okay, brief me on this package, 它允许法学硕士，它允许克劳德·奥普斯问，好吧，向我介绍一下这个包，
this library, and it will respond with the latest information about that library. So it's a really 这个图书馆，它将响应有关该图书馆的最新信息。所以这真的是一个
useful one to know. Now looking for this one called Context 7 immediately illuminates a classic 有用的人知道。现在找这个叫Context 7的就立刻阐释了经典
problem with these marketplaces that they're full of noise. Back comes tons of different versions 这些市场的问题在于它们充满了噪音。回来了有很多不同的版本
of Context 7, including one that says it's an unofficial MCP server, a Context 7 clone, Context 7，包括一个说它是非官方 MCP 服务器、Context 7 克隆的服务器，
things that look dubious. And I just happened to know that the right one is this one because I 看起来可疑的事情。我只是碰巧知道正确的就是这个，因为我
recognize that logo. And if we click into it, you can see that the maker is Upstash. And I happen to 认出那个标志。如果我们点击进去，你可以看到制作者是Upstash。而我碰巧
know that they are indeed the authors of Context 7. But you kind of have to know that. Now fear not, 知道他们确实是上下文 7 的作者。但你必须知道这一点。现在不要害怕，
when we get to plugins, you'll see that there is a way that there can be a better discovery 当我们谈到插件时，您会发现有一种方法可以更好地发现
mechanism. But for MCP servers, discovery is something that comes from doing research, 机制。但对于 MCP 服务器来说，发现来自于研究，
from exploring things. There is here a comments section where you can leave comments and you 来自探索事物。这里有一个评论区，你可以发表评论，你
can look for people's reviews of something, but it's empty. That's not much good. So this is 可以查找人们对某事的评论，但它是空的。那不太好。所以这是
mcp.so, which is usually okay. And next up is Glamour.ai, which has a bunch of different mcp.so，通常没问题。接下来是 Glamour.ai，它有很多不同的
things in it. And we are looking here in the MCP directory, we can click on servers to come 里面的东西。而我们这里是在MCP目录下查找，我们可以点击servers来
straight into their servers. And you'll see it's been updated very recently. For me, it's got 16,000 直接进入他们的服务器。您会看到它最近已更新。对我来说，有 16,000
servers, so a bit less than mcp.so. And I like the way they have this security license and quality 服务器，所以比 mcp.so 少一点。我喜欢他们拥有安全许可证和质量的方式
rating of things. You can see how much has been downloaded, how much has been favorited. So this 对事物的评级。您可以看到已下载了多少，已收藏了多少。所以这个
is definitely a more thriving marketplace, I would say. But let's do the same test. Let's look for 我想说，这绝对是一个更加繁荣的市场。但让我们做同样的测试。我们来寻找一下
Context 7 here. And here we go. Well, again, you see that there's a bunch of them, you sort of have 这里是上下文 7。我们开始吧。好吧，再一次，你看到有很多这样的人，你有点
to know that Upstash is the right one. And some of them all have several triple... three of them 知道 Upstash 是正确的选择。其中一些都有几个三重...其中三个
at least have a triple A rating, no, four of them. But I know that this is the right one, I can click 至少有 3A 评级，不，是四个。但我知道这是正确的，我可以点击
into this, and we can see information about this. And we can see that there is also a link to their 进入这个，我们可以看到这方面的信息。我们可以看到还有一个链接到他们的
actual GitHub where they have it. And you can see that they've got information about how to use it, 他们有实际的 GitHub。你可以看到他们有关于如何使用它的信息，
including specifically how to use it in Cloud Code. And you can see that the instructions for 具体包括如何在 Cloud Code 中使用它。您可以看到以下说明
Cloud Code have specifically one if you want to do it remotely, and one if you want to do 如果您想远程操作，Cloud Code 有专门的一种，如果您想远程操作，则有一种
it locally. The two different transport mechanisms that both work, both have the same benefits, 它在本地。这两种不同的传输机制都起作用，都有相同的好处，
just whether the MCP server runs on my box or in the cloud. So this is the specific command 只是 MCP 服务器是在我的盒子上运行还是在云中运行。所以这是具体的命令
that we will use to equip Cloud Code with this MCP server. It's as simple as that. It's just 我们将使用它来为 Cloud Code 配备此 MCP 服务器。就这么简单。这只是
a command that will run in a terminal, and that will bolt these tools into Cloud Code. It's that 将在终端中运行的命令，并将这些工具连接到 Cloud Code 中。就是那个
simple. And I just want to double down on this point that the big deal with MCP, the big deal 简单的。我只是想强调这一点，MCP 的大事，大事
comes down to the fact that there is this one line of code, one command that you run in a terminal. 归结为这样一个事实：有一行代码，即您在终端中运行的一个命令。
And after running that command, now Cloud Code has been equipped with a new set of tools. 运行该命令后，现在 Cloud Code 已配备了一套新工具。
In this case, it's tools to do something quite specific about telling Cloud about latest APIs, 在这种情况下，它是一些非常具体的工具，可以告诉云最新的 API，
but there could be many other things like retrieving market data or other things, 但可能还有很多其他的事情，比如检索市场数据或其他事情，
different sets of tools. And with a single line, it just suddenly means that Cloud Code 不同的工具集。只需一行，它就突然意味着 Cloud Code
has that ability. That is the kind of eureka, that's the big deal about MCP and the reason 有这个能力。这就是那种顿悟，这就是 MCP 的重要意义和原因
people love it so much. It's not like it's a super ingenious thing. It's just that everyone's 人们非常喜欢它。这并不是什么超级巧妙的事情。只是每个人的
adopted this standard, making it really easy. And the other point I want to make is that if you want 采用这个标准，使它变得非常容易。我想说的另一点是如果你想要
to know whether or not an MCP server is legit, I was sort of jokey about it earlier. It's like, 要知道 MCP 服务器是否合法，我之前对此有点开玩笑。就像，
how do you tell? You just know the name of the person that made it. Well, the best way is the 你怎么知道？你只知道制作它的人的名字。嗯，最好的方法是
same as any other open source software, like something you might pip install, anything like 与任何其他开源软件相同，就像您可以 pip 安装的东西一样
that. Go to the source, go to GitHub. If you scroll down here for a start, they've got a little 那。转到源代码，转到 GitHub。如果你从这里开始向下滚动，他们有一些
advert for themselves in a way. They've got this little star history thing to show that Upstash 以某种方式为自己做广告。他们用这个小小的明星历史来证明 Upstash
slash Context 7 has got quite a few GitHub stars. I think earlier I said that there was a GitHub 斜线上下文 7 已经获得了相当多的 GitHub star。我记得之前我说过有一个 GitHub
link above, which was wrong. The GitHub link is right over here. You can see it just here to the 上面的链接是错误的。 GitHub 链接就在这里。你可以在这里看到它
GitHub repo. And if you click there, we flip over to the GitHub repo. Here we are in Upstash Context GitHub 存储库。如果您单击此处，我​​们将转到 GitHub 存储库。我们现在处于 Upstash 上下文中
7. This is the GitHub repo. You can see it does indeed have more than 40,000 stars. That's a good 7. 这是 GitHub 存储库。可以看到它确实有超过40,000颗星。这是一个很好的
sign. You can see about the GitHub issues. You can look through them if you wanted. You can see that 符号。您可以查看 GitHub 问题。如果您愿意，可以查看它们。你可以看到
it was last updated 10 hours ago or something. So it's clearly got a lot of traction. It gives you 上次更新是在 10 小时前或者什么的。所以它显然受到了很大的关注。它给你
a good sense that this is actively maintained. And then this is the readme that's always worth 良好的感觉是这是积极维护的。这是始终值得的自述文件
looking at. And you can see in here, it will tell us exactly how to install it. It's got the same 看着。你可以在这里看到，它会准确地告诉我们如何安装它。它有相同的
advert again. And I'm sure it will tell us in here the ways to install it. Yes, in Cloud Code, 再次打广告。我相信它会在这里告诉我们安装它的方法。是的，在云代码中，
it's got the same commands right here. You could take it straight here from GitHub as well. 这里有相同的命令。您也可以直接从 GitHub 获取它。
So that's the kind of authoritative source to make sure you're satisfied 这就是确保您满意的权威来源
with the MCP server that you're about to add to Cloud Code. 与您要添加到 Cloud Code 的 MCP 服务器。