User/asklar/dotnet #2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Complete .NET 8 CLI port with feature parity to TypeScript version - Interactive init command with server type auto-detection - Pack/unpack with identical archive format and output formatting - Validate command with comprehensive manifest validation - Sign/verify/unsign using .NET SignedCms with PKCS#7 detached signatures - Info command showing bundle details and signature status - Self-signed certificate generation for testing - Comprehensive test suite with CLI integration tests - Modern .slnx solution format - Updated .gitignore with .NET build artifact patterns - Documentation in dotnet/README.md and main README.md
- Updated author information - Added NuGet package metadata (license, URLs, tags) - Removed unused Spectre.Console dependency - Configured README.md to be included in package - Enhanced package description and tags for discoverability
- Disabled debug symbols generation (DebugType=none, DebugSymbols=false) - Excluded satellite resource assemblies (SatelliteResourceLanguages=en) - Bumped version to 0.1.1 - Reduced package size from ~507KB to ~367KB (28% reduction)
…and manifest validation improvements - Added options for dynamic tool discovery in PackCommand: --force, --update, and --no-discover. - Implemented validation of referenced files in the manifest before packing. - Improved handling of tool and prompt mismatches during packing, with options to update the manifest. - Enhanced ValidateCommand to support directory-based validation and update capabilities. - Introduced ValidationSeverity enum to categorize validation issues as errors or warnings. - Updated ManifestValidator to provide more detailed validation feedback, including warnings for missing prompt texts. - Added JsonSerializerOptions customization for better JSON handling in McpbJsonContext. - Updated project dependencies to include ModelContextProtocol for enhanced functionality.
…ltiple files - Updated formatting and indentation in CLI documentation and test files for better readability. - Enhanced the structure of manifest-related classes and validation logic to ensure clarity. - Adjusted JSON serialization settings for better compatibility and maintainability. - Fixed minor issues in project file references and ensured consistent use of naming conventions.
…nd improve error handling
Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
…on from client Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
… trigger Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
…d document file-system-node rich schemas Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
…ified manifest args Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
…ation Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
…gnment time Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
…rate updates not commit them Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
Co-authored-by: asklar <22989529+asklar@users.noreply.github.com>
|
Hi @asklar May I ask if this is the recommended way to use MCPB CLI on Windows? I noticed this is a forked repo. Is this .NET CLI implementation going to be merged to the MCP community managed repo, or will it be maintained through Microsoft? I'm asking because when I found this project from the Microsoft documentation at https://learn.microsoft.com/en-us/windows/ai/mcp/servers/mcp-mcpb#build-your-mcp-bundle links to this repo, but I wasn't sure if it's a personal project or Microsoft supported. I see PR modelcontextprotocol#166 is still open. Also, I noticed the package is published on NuGet as Mcpb.Cli. Just wanted to understand the maintenance and support model before using it. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.