llm/9b2efe03-4d9e-4db2-a79a-13cee83b17d6/topic-5-c4466fc5-5bec-4660-a2cb-cab9ab8dc96a-input.json
The following is content for you to summarize. Do not respond to the comments—summarize them. <topic> 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 </topic> <comments_about_topic> 1. 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 2. 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 3. Does context mode only work with MCPs? Or does it work with bash/git/npm commands as well? 4. are people still injecting mcp into their context ? lmao. Use skills and cli instead. </comments_about_topic> Write a concise, engaging paragraph (3-5 sentences) summarizing the key points and perspectives in these comments about the topic. Focus on the most interesting viewpoints. Do not use bullet points—write flowing prose.
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
4