Pedro Lopez
① 他说过的话
6 条
所以 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]
但我们发现，真正有效的是把它保持得很窄，用渐进式发现来了解连接器可用的所有能力，并真正限制你塞进去的上下文数量。
指向原始笔记的链接
But instead what we found is really keeping it narrow, using progressive discovery of all of the capabilities that the connector has available and really limiting the amount of context that you shove into
—— Pedro Lopez · [06:30]
技术上讲，你可以通过 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]
当你制作一个 CLI 时，一些可能对用户有帮助的东西，反而会成为智能体的阻碍。
指向原始笔记的链接
Some of the things that might be helpful for users when you’re making a CLI are going to be like blockers for agents.
—— Pedro Lopez · [11:18]
这里另一个有趣的事实是，如果你看到智能体一遍又一遍地犯同样的错误，多次调用错误的命令，考虑把那个（错误的）用法变成你的契约。
指向原始笔记的链接
And another interesting fact here is if you see agents making the same mistake over and over, calling the wrong command a bunch of times, consider making that your contract.
—— Pedro Lopez · [13:23]
让智能体能够极其简单地撞见正确的使用方式。
指向原始笔记的链接
Make it dead simple for agents to stumble across the right way to use things.
—— Pedro Lopez · [13:33]
② 出现在这些集
1 集
- 《当命令行的使用者变成人工智能助手》 — 作为嘉宾
③ 他谈到的
点进去有真内容 —— 本页主要出口
Airbyte · MCP · CLI · 智能体 · 上下文存储 · OAuth · 技能