请问HN：手动发现和配置MCP服务器是唯一的方法吗？
在阅读了关于自主工具调用的论文（https://arxiv.org/pdf/2506.01056）后，我想知道是否还有其他人和我一样，对当前的MCP（模型上下文协议）工作流程感到沮丧。
我为我的智能体添加新功能的典型流程是：
1) 搜索可能具备我所需功能的MCP服务器
2) 阅读文档以验证其是否确实能满足我的需求
3) 安装MCP服务器并手动将其添加到我的智能体工具列表中
这个过程感觉非常耗时，并且不够“智能”。
我是不是漏掉了什么？对于那些使用MCP构建的人：
- 你们是如何发现与自己用例相关的MCP服务器的？
- 是否有工具/平台可以聚合MCP服务器并提供可搜索的功能？
- 有没有人自动化了从“我需要X功能”到“智能体现在可以做X”的过程？
感觉应该有更好的方法，让智能体能够根据功能需求自行发现和配置工具。
查看原文
After reading this paper on autonomous tool invocation (https://arxiv.org/pdf/2506.01056), I'm wondering if others share my frustration with the current MCP (Model Context Protocol) workflow.
My typical process for adding a new capability to my agent:<p>1) Search for MCP servers that might have the functionality I need
2) Read through documentation to verify it actually does what I want
3) Install the MCP server and manually add it to my agent's tool list<p>This feels incredibly time-consuming and not "agentic".<p>Am I missing something? For those building with MCP:<p>- How do you discover relevant MCP servers for your use cases?
- Is there a tool/platform that aggregates MCP servers with searchable capabilities?
- Has anyone automated the process of going from "I need X functionality" to "agent can now do X"?<p>Feels like there should be a better way where agents could discover and configure tools themselves based on capability requirements.