Base Pi doesn’t seem like an apt comparison here. Strands comes with MCP servers, subagents, and web fetch tools built in. To get those on Pi, you have to add addons, and then you get into the space of “which addons should be added to make it an apples-to-apples comparison? Which MCP addon do I use, the fastest one, or the most popular one?”. My guess is they chose OMP because it’s the defacto standard for answering those “which addons should be considered out of the box” questions for Pi.
If "pi install npm:pi-mcp-adapter" is preventing them from including pi in benchmarks, then they might not be competent to run trustworthy benchmarks.
There are four different Pi plugins with the name “pi-mcp-adapter”, not including forks. Which one should they use for the fairest benchmark? And who should be the tie breaker when someone thinks they should use a different plugin? Now answer the same questions for all of the other plugins necessary for Pi to reach parity with Strands.
> There are four different Pi plugins with the name “pi-mcp-adapter”, not including forks. Which one should they use for the fairest benchmark?
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.
theturtletalks · · focus · HN ↗
cobolcomesback · · focus · HN ↗
miroljub · · focus · HN ↗
cobolcomesback · · focus · HN ↗
It’s like you didn’t even read my comment.
miroljub · · focus · HN ↗
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.