Resources User Guide
These guides cover exposing readable content from an MCP server: how a resource is declared and addressed, and what its reader actually returns. Start with Getting started if you have not registered a resource yet.
Guides
| Guide | Scope | API starting points |
|---|---|---|
| Declaring resources | Direct resources, URI templates and how they are matched segment by segment, the fluent builder, titles and icons, and listing resources at runtime. | TTMSMCPResource, TTMSMCPResources, TTMSMCPResourceBuilder |
| Resource content and updates | Text and binary content, MIME types, reader ownership, reporting an error from a reader, subscriptions, and change notifications. | TTMSMCPResourceContent, TTMSMCPResource |
Related components
- MCP Server owns the
Resourcescollection, answersresources/list,resources/templates/list, andresources/read, and sends the change notifications a subscribed client relies on. - Tools can return a resource link rather than inlining content, which is how a tool hands back something large the client fetches separately.
- Prompts is the third collection a server exposes.
- Attributes generates resources from RTTI attributes, so a plain Delphi method becomes a resource reader without explicit registration.