It’s like you didn’t even read my comment.
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
The one that everyone else uses, the most popular. Exactly the one I listed.
I wrote "pi install npm:pi-mcp-adapter". It would install the mcp adapter.
> Now answer the same questions for all of the other plugins necessary for Pi to reach parity with Strands.
That's the whole point of Pi, it doesn't have to reach checklist level parity with Strand. Just benchmark it with its default config. Add mcp adapter if your benchmark really requires it, but that's it.
> It’s like you didn’t even read my comment.
I did, but it seems you didn't read my comment, or you didn't understand that the command I gave you is an actual recipe, and not a pseudo instruction.
In that same vein, Pi is less bloated then Deepseek and Oh My Pi, which are built on top of Pi. Isn’t it dubious to leave it out?