What if you don't need MCP at all?
6 days ago
- #BrowserDevTools
- #AgenticCoding
- #MCP
- MCP servers can be inefficient for specific tasks due to their broad coverage and large context consumption.
- Extending or modifying existing MCP servers is complex and requires understanding the codebase.
- MCP servers lack composability, requiring results to pass through the agent's context for persistence or combination.
- Simple Bash and code execution can be more efficient and composable than MCP servers for many tasks.
- A minimal set of browser dev tools (start, navigate, evaluate JavaScript, screenshot) can replace bulky MCP servers.
- Custom tools like a picker for DOM elements or a cookies tool can be easily added to enhance functionality.
- Using simple scripts reduces token usage and leverages the agent's existing knowledge of Bash and coding.
- Setting up a dedicated agent-tools directory with aliases ensures tools are globally available without polluting the environment.
- This approach offers flexibility, efficiency, and ease of modification compared to rigid MCP server structures.