MCP servers aren't dead. You're just using them wrong. Here are two proven patterns on how to correc...
TL;DR · AI 摘要
Philipp Schmid分享了正确使用MCP服务器的两种模式：显式使用和子代理，以避免资源浪费。
核心要点
- MCP服务器只有在用户@提及的时候才被包含。
- 通过子代理启用MCP服务器可以提高效率。
- 盲目启用MCP服务器会导致上下文膨胀、成本增加及性能下降。
结构提纲
按章节快速跳转。
思维导图
用一张图看清主题之间的关系。
查看大纲文本（无障碍 / 无 JS 友好）
- 正确使用MCP服务器
金句 / Highlights
值得收藏与分享的关键句。
MCP servers are only included when user @mentions.
Enable MCP servers per-subagent, e.g., a code review agent always needs GitHub.
Blindly enabling them bloats your context, which leads to higher cost and worse performance.
- Explicit Use: MCP servers are only included when user @mentions. Nothing loads unless requested.
- Subagents: Enable MCP servers https://t.co/YbOKefUoCY" / X
Philipp Schmid on X: "MCP servers aren't dead. You're just using them wrong. Here are two proven patterns on how to correctly use MCP servers and avoid the bloat 1. Explicit Use: MCP servers are only included when user@mentions. Nothing loads unless requested. 2. Subagents: Enable MCP servers https://t.co/YbOKefUoCY" / X
Don’t miss what’s happening
Philipp Schmid 
MCP servers aren't dead. You're just using them wrong. Here are two proven patterns on how to correctly use MCP servers and avoid the bloat 1. Explicit Use: MCP servers are only included when user@mentions. Nothing loads unless requested. 2. Subagents: Enable MCP servers per-subagent, e.g. a code review agent always needs GitHub. Read more ↓
Quote
Philipp Schmid
@_philschmid
·
Apr 27
Article
How to correctly use MCP servers with your AI Agents
MCP servers are not dead. But blindly enabling them bloats your context, which leads to higher cost and worse performance. Unlike Agent Skills, MCP servers don't come with progressive disclosure out...
·
10
18
189
188
Read 10 replies