English Translation
I believe the following is related to previous posts, but regarding MCP, I think it would be convenient if the following could be implemented:
- Display a list of available tools and allow users to select which tools to use when customizing modes
- Allow users to explicitly specify which tool to use through @ (annotations)
Sometimes, when multiple MCP tools are available, the LLM might call a tool that wasn’t actually intended by the user based on its own judgment.
For a specific example, when both GitHub MCP server and Fetch MCP server are configured, and you want to check the latest commit information from a GitHub repository URL in a prompt to the LLM, ideally you’d want the GitHub MCP server to be used. However, due to the randomness of the LLM, sometimes the Fetch MCP server gets used instead, resulting in unexpected outcomes. This happens because of MCP’s design philosophy of entrusting tool selection to the LLM, but it can sometimes be very inconvenient.
The attached image shows how I customized Claude Code to explicitly call the tools of connected MCP servers. This has reduced the uncertainty in tool selection, and I would be happy if similar functionality could be incorporated into Cursor as well. (Of course, I’d like to keep the automatic tool selection and usage functionality of the LLM intact. I believe a hybrid approach would be preferable.)