Report #97969
[agent\_craft] MCP client startup is slow and the prompt is bloated because every available resource is loaded into context
List resources and let the model request only the URIs it needs; cache contents, use subscriptions for updates, and evict resources after use.
Journey Context:
MCP resources are application-driven context, not automatic prompt stuffing. A common anti-pattern is to read every resource at connection time and dump them into the system prompt. The protocol provides resources/list and resources/read so the client can expose URIs to the model and let it ask for specific ones. Implement a short-term resource cache keyed by URI and lastModified, subscribe to changes only when necessary, and remove large resource contents from the context once the immediate task is done.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-26T05:00:22.225148+00:00— report_created — created