Ask HN: 征求意见：MCP 与基于浏览器的代理
1 分•作者: giaco_hendel•6 个月前
大家好，我想问问你们对一件事的看法。<p>我们开发了 vykee.co 作为一款用户引导工具。它的理念是：通过对新用户隐藏高级功能，让 SaaS 界面更容易理解。<p>其中一个主要功能是标签系统，它允许 SaaS 公司标记界面元素，并将多个元素组合成一个功能。所以基本上我们有一个前端的 UI 层（为每个元素和功能都配备了唯一的标识符和注释）。<p>我认为这个 UI 层对 LLM 来说可能非常有用：如果我们把所有这些 UI 信息放在一个简单的 llms.md 文件中（就像一个针对 LLM 的 robots.txt），它们就能比解析 HTML 或依赖截图更好地理解界面。<p>现在——这只对基于浏览器的代理有用。<p>我们讨论过这个问题，有人认为押注 MCP 而不是基于浏览器的代理更有意义，因为 MCP 是标准，并且被更广泛地采用。他们的想法是设置一个 MCP 并将其连接到已标记的前端元素。<p>你们认为押注基于浏览器的代理还有意义吗？<p>谢谢！
查看原文
Hi guys, I want ask for your opinion on something.<p>We’ve built vykee.co as an onboarding tool. Idea = make SaaS interfaces easier to understand, by hiding advanced features for new users.<p>One of the main features is a tagging system that allows the SaaS company to tag elements, and group multiple elements into one feature. So basically we have an UI layer of the frontend (complete with unique identifiers and annotations for every element and feature).<p>I think this UI layer could be pretty useful to LLMs: If we put all that UI info in a simple llms.md file (like a robots.txt but for LLMs), they could understand the interface much better than having to parse the hmtl or rely on screenshots.<p>Now – this would only be helpful for browser-based agents.<p>We’ve had this discussion where some argue it would make much more sense to bet on MCP instead of browser-based agents, since it’s the standard and more widely adopted. The idea being to set up an MCP and connect it to the tagged frontend elements.<p>Do you think it still makes sense to bet on browser-based agents?<p>Thanks!