
I'm a fan of the Code Mode approach - i.e. letting agents run code rather than narrow functions. Many people agree: CircleCI, Perplexity, etc. In fact, mcp2cli gives MCPs a CLI interface.
I feel the main reason is UNIX composability. I can run CLI commands in a loop, pipe them, etc.
I tested it out on ChatGPT. ChatGPT has an @Gmail Plugin. I build a Local MCP Server that exposes my CLIs, including gws (Google Workspace CLI). I gave it 3 tasks in a single prompt:
The @Gmail plugin did surprisingly well. After 19 minutes:
The @LocalMCP plugin had issues. I'm wrapping gws inside a developer MCP plugin, and:
gws via an MCP interface, rather than just read it.Clearly, I know less and mess up more than I think - better to use well-tested well-maintained tools and interfaces.
But anyway, I said: "ChatGPT, use codex on @LocalMCP to process the files from gws." That took 39 minutes:
The quality and scale of the latter are certainly better.
But my main learnings is: don't underestimate agents' ability to loop! They can iterate for long - mode like code than humans.