跨国深谈

MCP

56分钟阅读

跨国深谈← 返回←MCP
MC

MCP

概念
本站收录 95 集 · 21 条金句 · 关联 10 个

集里怎么说它

① 提到它的金句

21 条

智能体会做出完全一样的事情。它们会查一下 Notion 的 MCP，查一下 Slack 的 MCP，找到某个看起来对的东西，然后就心满意足地继续走下去了。
Agents do the exact same thing. They’ll hit the Notion MCP, they’ll hit the Slack MCP, they find something that looks right, and they carry on their merry way.
—— Dennis Pilarinos · [07:26]

指向原始笔记的链接

所有这些带来的结果是，现在我们拥有 1000 多个 MCP 工具，仅凭这些优化工作，我们就在整个集群范围内节省了超过 40%。
And all of this led to, like, now we have 1,000-plus MCP tools, and just with these optimization efforts, we’ve saved more than 40% fleet-wide savings.
—— Uday Kiran Medisetty · [05:27]

指向原始笔记的链接

这会产生复利效应，因为当人们去构建自己的东西并连接到我们的 MCP 时，他们基本上是在告诉我们：这是我的一个问题。
And this compounds because when people go and build their own thing and they go and connect to our MCP, they’re basically telling us, here is a problem that I have.
—— Arman Vaziri · [14:57]

指向原始笔记的链接

如果你今天真的把 Figma MCP 的输出复制下来，粘贴到一个简单的 HTTP server 里，它应该是像素级精确的。如果不是，请提一个 bug。
If you actually copy the output of the Figma MCP today and you paste it into a simple HTTP server, it should be pixel perfect. And if it’s not, file a bug.
—— Jesse Lumarie · [04:18]

指向原始笔记的链接

右边的截图是 MCP Inspector,如果你在开发 MCP server 却没用过它，那你就是在亏待自己。
The screenshot on the right is the MCP Inspector, and if you haven’t used it and you’re developing an MCP server, you’re doing yourself a disservice.
—— Jesse Lumarie · [12:04]

指向原始笔记的链接

我并没有被正式指派到 MCP 项目上，也没有被正式指派到我们的 make 产品上。但我最终帮助了它们被构建出来，只是因为我被给予了这样做的自由空间，并在此过程中学到了大量东西。
I wasn’t staffed on MCP. I wasn’t staffed on our make product. But I ended up helping them be built just because I was kind of giving the leeway to do so and learning a ton along the way.
—— Jesse Lumarie · [16:10]

指向原始笔记的链接

MCP 最强大的地方不在于 MCP 本身的任何特性，而在于所有人都在使用 MCP。
And the most powerful thing about MCP is not anything about MCP itself, but it’s that everyone uses MCP.
—— Alex Hancock · [02:45]

指向原始笔记的链接

这话说出来很俗，但我跟 LinkedIn 的产品经理说过，如果我能够用 MCP 接入 LinkedIn，我可能愿意多付 10 倍的钱。
This is so cheesy, but I’ve told LinkedIn product managers, I’d probably pay 10x more for LinkedIn if I just could MCP into it.
—— Aaron Levie · [44:27]

指向原始笔记的链接

我今天来真的就是想挑战你们:除了在又一家公司为另一个 SaaS 方案再做又一个 MCP 之外,还有其他问题值得解决。
And I really am just here to challenge you that there are other problems to solve than just another MCP for another SaaS solution at another company.
—— Cody Menefee · [04:17]

指向原始笔记的链接

MCP 就已经用 100 个工具占满了你的上下文。可能你三分之一的上下文就这么没了，却什么工作都没做。
MCP would already eat 100 tools in your context. Maybe one third of your context would be gone without actually doing any work.
—— Jan Čurn · [03:00]

指向原始笔记的链接

所以大多数智能体仍然生活在黑暗时代，它们不支持这些功能，你知道的，大多数 MCP 客户端也是如此。
So still, most agents are living in the dark ages, and they don’t support these features, you know, and most MCP clients.
—— Jan Čurn · [07:03]

指向原始笔记的链接

所以请不要再说什么 CLI 比 MCP 好了，因为 MCP 加 CLI 才是最好的。
So please stop saying CLI is better than MCP because MCP plus CLI is the best.
—— Jan Čurn · [18:18]

指向原始笔记的链接

所以 MCP 给了智能体一扇通往每个应用的门，却让它们站在成千上万个彼此隔绝的房间里，没有地图，也没有曾到过那里的记忆。
And so MCP gave agents a door into every app, but it left them standing in thousands of separate rooms with no map and no memory of ever being there.
—— Sarah Simionescu · [04:45]

指向原始笔记的链接

但人类已经厌倦了仪表盘，而他们的智能体也厌倦了设计糟糕的 MCP 服务器。
But the humans are tired of dashboards and their agents are tired of poorly designed MCP servers.
—— Sarah Simionescu · [09:28]

指向原始笔记的链接

以至于当人们在集成时，默认方式就是通过 MCP，而我必须真的去问：你是不是其实只需要一个 API？
Like, to the point that when people are integrating, the default is via MCP and I have to go, and I have to literally go, Chua, it’s like, do you just need an API for this, really?
—— Matt Jones · [13:55]

指向原始笔记的链接

而且所有 MCP 服务器中有 43% 实际上存在漏洞。
And 43% of all the MCP servers actually has vulnerabilities.
—— Eli Cohen · [04:35]

指向原始笔记的链接

你可以创建一个远程 MCP 服务器,它可以成为你整个公司的事实来源。
You can create a remote MCP server, which can become the source of truth across your whole company.
—— Rafal Wilinski · [08:10]

指向原始笔记的链接

所以 MCP 和 CLI，我们构建它们的方式是，它们是接入我们平台的薄而统一的接口，而不是平台的重实现。
So the MCP and the CLI, the way that we’ve structured things is that they are thin, unified interfaces into our platform, not re-implementations of the platform.
—— Pedro Lopez · [03:04]

指向原始笔记的链接

技术上讲，你可以通过 MCP 使用其他认证机制，但如果你用 bearer auth 或类似的东西，你会非常难受，因为规范非常偏重 OAuth，而且所有的客户端，至少是主流的那些，都非常倾向于把 OAuth 作为安装该连接器的更好用户体验。
And technically, you can use other authentication mechanisms through MCP, but you’re really going to have a hard time if you do like bearer auth or anything like that, because the spec is really heavy on OAuth, and all of the clients, the main ones at least, are really leaning towards the OAuth as a better UX for installing that connector.
—— Pedro Lopez · [07:15]

指向原始笔记的链接

我也很高兴我甚至没有构建 MCP 支持。OpenClaw 非常成功，里面没有 MCP 支持
I’m also very happy that I didn’t even build MCP support. OpenClaw is very successful and there’s no MCP support in there
—— Peter Steinberger · 来自原文

指向原始笔记的链接

是的。没有理智的人类会尝试手动调用 MCP。
Yeah. No sane human tries to call MCP manually.
—— Peter Steinberger · 来自原文

指向原始笔记的链接

② 出现在这些集

95 集

③ 关联

点进去有真内容 —— 本页主要出口

智能体 · Claude · Anthropic · Claude Code · Codex · 沙箱 · OpenAI · harness · 护栏 · 技能

反向链接