请问HN：在Cursor/agents中，插件是否会将MCP工具隐藏在主代理之外？
快速架构问题。<p>当在 Cursor 中直接使用 MCP 服务器时，代理似乎将所有工具视为同一级别。<p>但是，当使用一个内部连接到 MCP 服务器的插件/扩展时，主代理：<p>是将插件视为一个单一工具，并将任务委派给其内部的子代理，还是<p>仍然将每个底层的 MCP 工具单独识别？<p>换句话说：插件是作为工具抽象边界存在，还是仅仅作为打包/安装机制？
查看原文
Quick architecture question.<p>When using MCP servers directly in Cursor, the agent seems to see all tools at the same level.<p>But when using a plugin/extension that internally connects to MCP servers, does the main agent:<p>see only the plugin as a single tool and delegate to a sub-agent inside it,
or<p>still see every underlying MCP tool individually?<p>In other words: do plugins act as a tool abstraction boundary, or just a packaging/install mechanism?