Struct StaticResourceHandler 

pub struct StaticResourceHandler { /* private fields */ }

Handler for static resources loaded from configuration.

Implements the PMCP SDK ResourceHandler trait for serving pre-loaded resources via MCP resources/list and resources/read. Storage is an IndexMap (Pattern D) so iteration order is deterministic across runs.

Orthogonality with skills

StaticResourceHandler is independent of [pmcp::server::skills::Skill] and bootstrap_skill_and_prompt. Downstream consumers can register both surfaces side-by-side; the toolkit makes no assumption about skill registration (RESEARCH §Risks #3).

Implementations

impl StaticResourceHandler

pub fn new(resources: IndexMap<String, LoadedResource>) -> Self

Create a handler from a pre-built IndexMap.

This is the constructor Plan 08 will target from impl From<&ServerConfig> for StaticResourceHandler.

Example

use pmcp_server_toolkit::resources::StaticResourceHandler;
use indexmap::IndexMap;
let map = IndexMap::new();
let handler = StaticResourceHandler::new(map);

pub fn from_configs(configs: &[ResourceConfig]) -> Result<Self>

Create a new handler from a list of resource configurations.

Insertion order is preserved — list() reflects the order configs were supplied in.

pub fn empty() -> Self

Create an empty handler with no resources.

pub fn is_empty(&self) -> bool

Returns true if there are no resources.

pub fn len(&self) -> usize

Returns the number of resources.

pub fn get(&self, uri: &str) -> Option<&LoadedResource>

Get a resource by URI (for use outside of the trait).

pub fn uris(&self) -> impl Iterator<Item = &str>

Iterate over resource URIs in deterministic insertion order.

Trait Implementations

impl From<&ServerConfig> for StaticResourceHandler

fn from(cfg: &ServerConfig) -> Self

Build a StaticResourceHandler from a parsed crate::config::ServerConfig.

Each [[resources]] entry in config becomes one LoadedResource. Resources with no content field default to an empty body — the strict-parse path’s crate::config::ServerConfig::validate does not flag empty resource bodies (operators may use the placeholder form "loaded from path.md" as a stable URI handle), so this construction follows suit. Resources WITH content_file semantics are out of scope for the lifted shape (Lambda runtime constraint, mirroring LoadedResource::from_config).

Insertion order matches the order of [[resources]] declarations, satisfying Pattern D (deterministic list() output).

Example

use pmcp_server_toolkit::{ServerConfig, StaticResourceHandler};

let cfg = ServerConfig::default();
let handler = StaticResourceHandler::from(&cfg);
assert_eq!(handler.len(), 0); // default config has no [[resources]]

impl ResourceHandler for StaticResourceHandler

fn list<'life0, 'async_trait>( &'life0 self, _cursor: Option<String>, _extra: RequestHandlerExtra, ) -> Pin<Box<dyn Future<Output = Result<ListResourcesResult>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait,

List available resources.

fn read<'life0, 'life1, 'async_trait>( &'life0 self, uri: &'life1 str, _extra: RequestHandlerExtra, ) -> Pin<Box<dyn Future<Output = Result<ReadResourceResult>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait,

Read a resource at the given URI.