Resources
The read-only raster:// resource URIs the MCP server exposes.
Alongside tools, the server exposes three read-only MCP
resources with stable raster:// URIs. Clients that prefer the resource
primitive — for example to attach data to a prompt — can read these directly
instead of calling the equivalent read tool.
raster://organizations/{orgId}/libraries
raster://organizations/{orgId}/libraries/{libraryId}/assets
raster://organizations/{orgId}/libraries/{libraryId}/tags| URI template | Returns |
|---|---|
raster://organizations/{orgId}/libraries | Library[] the key can access. |
raster://organizations/{orgId}/libraries/{libraryId}/assets | Asset[] in the library. |
raster://organizations/{orgId}/libraries/{libraryId}/tags | Tag[], sorted by usage count descending. |
Every resource is application/json and enforces the same
access check as the matching tool: a
resource read returns data only for an organization or library the API key
authorizes.
Resources return the default first page of results. They carry no pagination
or filter syntax in v1 — the URIs are stable identifiers. For pagination,
filtering, or search, use the equivalent tool:
list_libraries,
list_assets, or
list_tags.
Discovery
resources/list returns the three collection URI templates above rather
than enumerating every concrete library or asset, so discovery stays O(1)
regardless of how much data the key can reach. Clients resolve the templates via
resources/templates/list and then read a concrete URI by substituting the
{orgId} / {libraryId} segments.