1.1.1

MCP Nexus v1.1.1 Release Notes

🚀 Major New Features

🧩 Configuration & Server Setup

• Rich, strongly-typed configuration models added:
  • AutomatedRecoverySettings, BatchingSettings, DebuggingSettings, ExtensionsSettings,
    IpRateLimitingSettings, LoggingSettings, McpNexusSettings, RateLimitRule,
    ServerSettings, ServiceSettings, SessionManagementSettings, TransportSettings
• Configuration/Logging wiring updated to use the new models for clearer, safer configuration

🌐 Protocol Layer

• New EngineService in nexus_protocol/Services to encapsulate engine operations
• Expanded protocol tests across tools, middleware, notifications, and resources

🔐 External APIs

• Administrator detection utilities added:
  • Security/AdministratorChecker and IAdministratorChecker

⚡ Performance & Reliability

🔧 Engine & Batching

• Settings forwarded into the debug engine for deterministic behavior
• Batching pipeline refinements:
  • BatchProcessor, BatchCommandBuilder, BatchCommandFilter,
    BatchResultParser, BatchSentinels, SessionBatchCache
• Command preprocessing improvements:
  • CommandPreprocessor, PathHandler, WslPathConverter

🧠 Encapsulation & Surface Area

• Reduced number of public classes to tighten encapsulation and improve maintainability
• Setup and Protocol libraries no longer singletons; constructor-injected lifetimes for testability

🧪 Quality & Testing

• Test coverage substantially increased:
  • 1228 total tests (all passing)
  • 87.1% line coverage, 77.8% branch coverage
• Significant test additions across engine internals, protocol server/services/tools,
  middleware, resources, configuration, setup, share, and extensions
• New/expanded tests for:
  • Engine internals (CDB session/queue/debug session/process output)
  • Batching components and sentinels
  • Protocol notifications, tools, middleware, resources
  • Setup managers, validators, installers
  • Config loading/logging and typed settings
  • Shared models and ID generators

🐛 Fixes

• Numerous static analyzer/style issues resolved
• Protocol and extensions callback models split into explicit types for clarity and safer usage
• General hardening across configuration and logging paths