jongalloway / jongalloway/dotnet-mcp
Opportunity: first-class MCP Apps APIs (SEP-1865)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 36
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Opportunity: first-class MCP Apps APIs (SEP-1865)
Part of #481.
The server already exposes McpAppsResources (DotNetMcp/Resources/McpAppsResources.cs). SDK 2.0 promotes MCP Apps to a structured extension with typed APIs: McpApps.ExtensionId (io.modelcontextprotocol/ui), McpUiToolMeta, and the [McpAppUi] attribute (diagnostic MCPEXP003, experimental).
Tasks
- Evaluate moving
McpAppsResourcesto the typedModelContextProtocol.Extensions.AppsAPIs. - Use
McpApps.ExtensionIdinstead of any hard-coded identifier. - Note that the API remains experimental (
MCPEXP003) and may change before the spec finalizes.
Acceptance
- MCP Apps support uses the SDK's typed extension surface (or a documented decision to defer).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with DotNetMcp/Resources/McpAppsResources.cs and compare its current MCP Apps support with the SDK 2.0 typed APIs: ModelContextProtocol.Extensions.Apps, McpApps.ExtensionId, McpUiToolMeta, and [McpAppUi]. Done means the support uses that typed extension surface, or the repository documents a decision to defer while noting the MCPEXP003 experimental status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100