π¦
MCP.Pack
A .NET MCP server implementing the Model Context Protocol (MCP) for NuGet package management π¦. Built with Clean Architecture and Domain-Driven Design (DDD) ποΈ, this project supports Ahead-Of-Time (AOT) compilation for fast startup and low memory usage β‘.
0 installs
Trust: 34 β Low
Browser
Ask AI about MCP.Pack
Powered by Claude Β· Grounded in docs
I know everything about MCP.Pack. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Loading tools...
Reviews
Documentation
MCP.Pack π
A modern .NET server for Model Context Protocol (MCP) and NuGet package management π¦. Built with Clean Architecture ποΈ and Domain-Driven Design (DDD) π§ , supporting AOT compilation β‘ and comprehensive automated testing π§ͺ.
β¨ Features
- π Discover and search NuGet packages via the Model Context Protocol (MCP)
- π Retrieve rich package metadata for any NuGet feed
- π§© Designed for extensibility and integration in modern .NET ecosystems
π οΈ Technical Highlights
- ποΈ Clean Architecture: strict separation of Domain, Application, Infrastructure, and API layers
- β‘ AOT (Ahead-Of-Time) compilation: fast startup, low memory usage
- π§ͺ Comprehensive automated tests: unit, integration, and architecture validation
- π Modern .NET 9: minimal APIs, dependency injection, async/await everywhere
ποΈ Project Structure
McpPack.sln
src/
McpPack.Domain/ # Domain logic, aggregates, value objects, repositories
McpPack.Application/ # Use cases, service interfaces
McpPack.Infrastructure/ # Implementations for repositories, external services
McpPack.Api/ # API endpoints, orchestration
tests/
McpPack.UnitTests/ # Unit tests for Domain & Application
McpPack.IntegrationTests/ # Integration & architecture tests
π Getting Started
π§° Prerequisites
- π£ .NET 9 SDK
- π (Optional) dotnet-reportgenerator-globaltool for coverage reports
πββοΈ Build & Run
dotnet build
dotnet run --project src/McpPack.Api
π§ͺ Test
dotnet test
ποΈ Architecture Principles
- π§ Domain: no dependencies, pure business logic
- π― Application: orchestrates use cases, depends only on Domain
- ποΈ Infrastructure: implements interfaces, depends on Application & Domain
- π API: exposes endpoints, depends only on Infrastructure
- π§ͺ Tests: separated by type (unit/integration/architecture)
π€ Contributing
- π Follow Conventional Commits
- π§ͺ Write tests for all new features and bugfixes
- π§Ή Keep code clean and robust
π License
MIT
Because good enough is never enough. π
