Skip to content

Conversation

@asklar
Copy link
Contributor

@asklar asklar commented Dec 3, 2025

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

asklar and others added 30 commits October 13, 2025 10:05
- 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.
…d document file-system-node rich schemas

Co-authored-by: asklar <[email protected]>
Copilot AI and others added 30 commits October 30, 2025 22:58
…n-theming

Add localization and icons support to .NET MCPB CLI (manifest v0.3)
Add NuGet publishing workflow with trusted publishing
This workflow publishes the .NET tool to NuGet using Trusted Publishing (OIDC). It includes steps for checkout, setup, restoring dependencies, building, testing, packing, and publishing.
Removed API key from NuGet push command for security.
Removed API key from NuGet push command for security.
- Added `--discover` option to validate that discovered tools/prompts match the manifest without updating.
- Introduced `--verbose` option to print detailed validation steps.
- Implemented checks to prevent simultaneous use of `--update` and `--discover`.
- Enhanced logging for asset path normalization and discovery violations.
- Updated manifest name and version based on server responses when using `--update`.
- Improved error handling and reporting for validation mismatches.
- Incremented version number to 0.3.4 in the project file.
Add the ability to pass user_config to discovery
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant