Context engineering is sleeping on the humble hyperlink
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Context engineering for LLMs faces a key challenge: providing all necessary context without overwhelming the model. While techniques like RAG and subagents help, hyperlinks offer an underutilized solution. By implementing a simple read_resources tool that accepts URIs, agents can dynamically load relevant context on-demand, similar to how humans navigate documentation. This approach is token-efficient, flexible, and enables just-in-time context loading. The Model Context Protocol (MCP) Resources provides the infrastructure needed, though most clients don't yet expose resources to models directly. The Firebase MCP Server demonstrates this pattern in practice with linked workflows for project initialization.
Table of contents
The obligatory human analogyHATEOAS in the era of AgentsOne Tool to Read Them AllBenefits of LinksMCP Resources: The future is now(ish)Working with what you haveSort: