想了解 MCP 和 CLI 到底怎么选？Eric 分享了他每天用两者的实战经验，帮你理清场景。
Eric Zakariasson 认为 MCP 和 CLI 服务于不同目的。CLI 适合模型已知的命令如 git、gh、npm、docker、file ops，基于 man pages 训练，几乎不消耗上下文。MCP 适合集成 Slack、Notion、Linear、Twitter 等服务，提供统一协议和 OAuth 认证。在 Cursor 中 MCP 体验更佳，有丰富图标和可追踪操作。作者建议个人用 CLI，团队用 MCP。
mcp > cli im glad this debase is not as active anymore. i use both every day. they just serve diffe...
mcp > cli im glad this debase is not as active anymore. i use both every day. they just serve different purposes cli for stuff the model already knows. git, gh, npm, docker, file ops. trained on man pages, and costs almost nothing in context. if im already signed in locally theres no reason to wrap it in anything mcp for most integrations. slack, notion, linear, twitter and its neat to have a protocol for all these integrations - add one server to my teams cursor and everyone gets access - auth once, persists, same locally and in cloud it also just feels better in cursor. rich icons, traceable, you can easily follow whats happening (tbh not reading that much) cli for personal, mcp for team (with oauth) 💬 2 🔄 2 ❤️ 6 👀 212 📊 4 ⚡