Reducing MCP token usage by replacing servers with CLI alternatives

Token optimization through MCP server reduction

A developer discovered that each MCP server added to their setup was dumping its entire tool schema into the context window with every message, consuming 30-40% of their available context. This was causing them to hit context limits faster than expected.

Specific MCP-to-CLI replacements

After auditing their setup, they identified several MCP servers that had CLI equivalents and made these replacements:

• agentmail mcp → agentmail cli (installed via npm install -g agentmail-cli) - allows Claude to manage inbox, send emails, and check messages through bash
• github mcp → gh cli - using commands like gh issue create and gh pr list
• postgres mcp → psql - using commands like psql -c "select * from users"

MCP servers kept in the setup

Two MCP servers were retained because they lacked good CLI alternatives:

• playwright mcp - for browser automation tasks
• memory mcp - for persistent memory functionality

Resulting configuration and rule

The developer reduced their MCP server count from 6 to 2 while maintaining all previous functionality. They established a new rule: "if there's a CLI, skip the MCP. Only add MCPs for stuff that genuinely doesn't have a command line option." This change made their context window feel larger and reduced how often they hit limits.