Bad MCP design costs your agent 5x more tokens
I recently did some tests on two MCPs with identical functionalities. Turns out one of them has really bad performance. So I wanna share those bad MCP design patterns that cause this. It all started when I wrote an MCP Server (MCP-A) for a to-do list app. Later, the app officially released its own MCP Server (MCP-B). Both MCPs have the same functionalities and hit the same backend API. The experiment is set up as follows: - Both MCP Servers connect to the same ToDo list account, and it will be r