Unverified80% confidenceFactExact time
每次MCP调用都会产生大量Token消耗，且由于需求动态变化，这些消耗无法像固定文档那样被缓存复用
1
Sources
80%
Confidence
Medium-term (~90 days)
Relevance
5/25/2026
First Seen
Valid until: 8/23/2026(expired)
Sources
UE5 + AI in Practice: Using MCP to Bridge Blueprint and C++ Development Workflows
bilibili虚幻小刚5/25/2026
Related Entities
Related Claims
UnverifiedMCP的工作机制需要将大量上下文信息注入模型输入，导致Token消耗过大76% similarVerifiedWhen connecting to multiple MCP servers simultaneously, tool descriptions alone can consume thousands or even tens of thousands of tokens.69% similarUnverifiedAt the tool layer, using large models with Function Calling or the MCP protocol to handle complex requests can only serve as a fallback and cannot carry the main traffic; otherwise, costs will severely overrun as user volume grows.67% similarUnverifiedUnder the traditional MCP calling approach, intermediate data (such as a meeting recording transcript) enters the context twice—once when read and once when passed as a parameter—causing redundant token consumption66% similarUnverifiedWhen each MCP is loaded, its tool descriptions are stuffed into the context; attaching a large number of MCPs to an Agent without restricting Tools will cause token explosion, increased latency, and rising costs.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1722API
curl https://kongchang.com/api/v1/knowledge/claims/1722MCP
get_claim(id=1722)