November 16, 2025
Bash bros vs Plugin pros
What if you don't need MCP at all?
Do you even need MCP? Simplicity stans vs plugin purists
TLDR: Mario argues you can ditch plugin servers and use simple scripts for browser tasks instead. Comments split between minimalists cheering, platform defenders saying MCP serves a different purpose, and pragmatists suggesting tool-trimming or a one-button “write code” approach—proof that simpler tools can beat bloated setups.
Developer Mario Zechner dropped a spicy take: skip fancy “MCP servers” (think: plugin hubs for AI apps) and just let your AI run simple commands and tiny scripts. His pitch? Four bare‑bones browser tricks—start, navigate, run a snippet, screenshot—powered by small Node tools, not bulky toolkits like Playwright MCP or Chrome DevTools MCP. The crowd went loud. The minimalists cheered, calling it “clean, fast, and actually usable,” and one fan even shouted out his “LLM‑as‑crappy‑state‑machine” approach with a link to claude-commands.
Then the purists arrived. “You’re misunderstanding MCP,” argued one commenter, saying MCP exists so AI platforms can host plugins for users, not just dev toys. Another voice of reason chimed in: why not just trim which tools are exposed instead of tossing the whole system? Meanwhile, the pragmatists lit a match: one dev said they’re trying to replace all tools with a single “write code” button—chaotic energy, big applause. The meme of the day: Bash bros vs Plugin pros. The drama? Whether MCP is overused religion or solid platform architecture. The vibe? Half “keep it simple,” half “don’t throw away the app store,” with everyone agreeing on one thing: too many tools make AIs dumber, not smarter.
Key Points
- •The author argues many MCP servers are inefficient for specific tasks due to numerous tools and lengthy descriptions that consume model context.
- •He notes MCP servers are hard to extend and are not inherently composable; outputs must pass through the agent’s context, with sub-agents adding complexity.
- •For browser-related agent tasks, he proposes a minimal toolset: start Chrome (optionally with a profile), navigate, execute JavaScript, and take screenshots.
- •His implementation uses simple Bash-invoked Node.js scripts built on Puppeteer Core, documented via a concise README for the agent to follow.
- •He contrasts token overheads: Playwright MCP (21 tools; ~13.7k tokens; ~6.8% of Claude’s context) and Chrome DevTools MCP (26 tools; ~18.0k tokens; ~9.0%).