Expose data sources and dynamic content generators to your MCP clients.
Resources give an LLM read‑only access to text, JSON, binaries, or files. Templates extend the idea by letting clients request parameterised URIs that generate data on the fly. In Hyperia both are primarily declared with the @mcp.resource decorator (for dynamic content) or mcp.add_resource() (for static assets).
What Are Resources?
When a client issues resources/read for a URI:
Hyperia finds the matching resource definition.
If the resource is dynamic (a function), it executes.
The returned content is packaged (text, JSON, bytes…) and streamed back.
This mechanism lets LLMs inspect configuration, fetch user docs, read database rows, or access freshly computed summaries relevant to a conversation.