CLI vs MCP Tradeoffs

Suggestions to use CLI tools like GitHub CLI instead of MCPs for fraction of token cost, with discussion of when each approach is appropriate

The discussion highlights a growing preference for using robust CLI tools, such as the GitHub CLI, as a more token-efficient alternative to the Model Context Protocol (MCP). While some users argue that injecting MCPs into context is becoming an outdated practice, others are exploring how emerging "context-mode" features might be applied to refactor or eliminate these tools entirely. There is a clear tension between the high cost of MCP token usage and the cross-platform versatility they offer compared to direct command-line execution. Ultimately, the consensus suggests that while CLI apps offer significant savings, their viability often depends on whether the user requires a solution that works across all interface surfaces.

View on HN · Topics

Really intrigued and def will try, thanks for this.

In connecting the dots (and help me make sure I'm connecting them correctly), context-mode _does not address MCP context usage at all_, correct? You are instead suggesting we refactor or eliminate MCP tools, or apply concepts similar to context_mode in our MCPs where possible?

Context-mode is still very high value, even if the answer is "no," just want to make sure I understand. Also interested in your thoughts about the above.

I write a number of MCPs that work across all Claude surfaces; so the usual "CLI!" isn't as viable an answer (though with code execution it sometimes can be) ...

Edit: typo

View on HN · Topics

A lot of this token usage can be avoided by using CLI apps instead of MCPs. For example, the github cli is very robust and does the job of the MCP with a fraction of the token cost

View on HN · Topics

Does context mode only work with MCPs? Or does it work with bash/git/npm commands as well?

View on HN · Topics

are people still injecting mcp into their context ? lmao.

Use skills and cli instead.

Summarizer