Comment by tkocmathla

It's a fair point, but for any well-established capability, the plugin with the most monthly downloads (overwhelmingly) is generally going to be "the one". For MCP, the top plugin [1] has 1M/mo, and the next one down has less than 2k/mo.

I do agree that in the case of benchmarking, it's a bit silly to put the onus on the benchmark runner to try and pick the right plugin for each capability that won't make someone point to /that/ as the reason Pi didn't do as well as expected.

[1] https://pi.dev/packages/pi-mcp-adapter?name=pi-mcp-adapter