MCP primitive enhancements

[Tyler-R-Kendrick]

Pre-submission Checklist

• I have verified this would not be more appropriate as a feature request in a specific repository
• I have searched existing discussions to avoid duplicates

Your Idea

As an author of an MCP Server, I want to be able to optionally configure MCP primitives (tools, prompts, resources, resource-templates, roots, etc.), instead of providing an entire handler where a default option is possible (given the current dependency hierarchy).

For example, say you have a local file hosted that you want to expose. Because you're already referencing the IFileProvider APIs, it would make sense to be able to configure that in DI with a line similar to:

builder.WithResource(localResource); //This would supply a specific file info, or MCPServerResource, or Mcp.Resource, etc...

or

builder.WithResource("path/file.ext", fileProvider); //This could support file providers for remote resources like Azure Storage.

or

builder.WithResources(mcpResources); //This would supply a list of the MCP native resource types, or file infos, or MCPServerResource types, etc...

etc.

After calling those extension methods for configuration, I would expect the handlers for those associated MCP primitives to have default implementations that use the resources I specified for the relevant operations (like list resources, readresourcerequest, etc.).

I'd like to utilize this thread to capture where there are deficits in the design around registration of MCP primitives and capture where / when issues can be raised to help support improving the developer experience towards this goal.

Scope

• Protocol Specification
• SDK Features
• Documentation
• Developer Experience
• Other

[Tyler-R-Kendrick]

#72 and #74 already discuss doing this for resources and resource templates.