创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

OpenRouter对比MCP、CLI与Skills的上下文成本

AI 总结

OpenRouter在一个GitHub任务上测试了GitHub MCP服务器、gh CLI和gh skill,并覆盖Claude Sonnet 5.5、Claude Haiku 5.5、GPT-6 Luna与Gemini 3.8 Flash。在Claude Sonnet 5.5上,三种方式均给出正确答案,但输入Token用量差距明显:加载46个默认工具的MCP服务器使用59,417个,skill使用3,315个,CLI使用1,421个。OpenRouter还称其Tool Search可降低工具定义的前置开销,但整体节省幅度因模型而异。

深度见解

测试表明,即使最终答案相同,智能体连接工具的方式也会显著影响上下文和输入Token用量,为开发者缩减工具范围、裁剪输出或延迟加载工具定义提供依据。

MCP vs CLI vs Skills: What Each Costs in Context

OpenRouter ·11/11/2026

MCP vs CLI vs Skills: What Each Costs in Context
MCP vs CLI vs Skills: What Each Costs in Context

Every tool you give an agent sends its definition to the model on every request, and you pay for it as input tokens. A Model Context Protocol (MCP) server can add tens of thousands of tokens to the context window. The usual alternatives are a command-line tool (CLI) or a skill.

We measured it on one GitHub task with the GitHub MCP server, the gh CLI, and a gh skill, on Claude Haiku 5.5, Claude Sonnet 5.5, GPT-6 Luna, and Gemini 3.8 Flash. On Sonnet 5.5, all three answered correctly, but the input tokens they used were very different. The CLI used 1,421, the skill used 3,315, and the MCP server used 59,417 with its default tools loaded. Here’s where the tokens go and how to cut them with our Tool Search server tool.

#OpenRouter#OpenRouter Tool Search#GitHub MCP server#gh CLI#Claude Sonnet 5.5#Claude Haiku 5.5#GPT-6 Luna#Gemini 3.8 Flash

原文约 12 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。