Skip to content
Clean Model Context Protocol
Lean Mean Clean Apps

Five templates, one brand, one search box. Everything in the docs is in here, including the bits we hoped you'd skim.

Try one of these

Results say which template they came from, so you won't end up reading about Lambda when you wanted GraphQL. Again.

Project structure

  • Directorysrc/
    • DirectoryApplication/ the domain and the rules
      • DirectoryAuthors/ queries and entities for authors
        • …
      • DirectoryMovies/ queries and entities for movies
        • …
      • DirectoryReviews/ queries, commands and entities for reviews
        • …
      • DirectoryVersions/ the version query
        • …
      • DirectoryCommon/
        • DirectoryBehaviours/ the logging and validation pipeline behaviours
          • …
        • DirectoryEnums/ the entity types NotFoundException names
          • …
        • DirectoryExceptions/ NotFoundException
          • …
        • DirectoryPaging/ shared paging rules
          • …
        • DirectoryTelemetry/ the activity source for the use case spans
          • …
      • DependencyInjection.cs
    • DirectoryInfrastructure/ the data
      • DirectoryDatabases/MovieReviews/ the EF Core context, models, mapping, migrations and repositories
        • …
      • DependencyInjection.cs
    • DirectoryPresentation/ the MCP server
      • DirectoryTools/ one static class of tools per feature
        • …
      • DirectoryResources/ movies, authors, reviews and the version as resources
        • …
      • DirectoryPrompts/ the movie prompts
        • …
      • DirectoryCompletions/ argument completion for the prompts
        • …
      • DirectoryModels/ the results the tools return, and the mapper that builds them
        • …
      • DirectoryErrors/ Application exceptions to tool errors and protocol errors
        • …
      • DirectorySerialization/ the source-generated JSON context
        • …
      • DirectoryAuthentication/ the JWT bearer and resource metadata settings, only with --include-auth
        • …
      • DirectoryTelemetry/ the OpenTelemetry settings
        • …
      • DirectoryExtensions/ builder and app configuration
        • …
      • Program.cs
      • appsettings.json, appsettings.local.json, appsettings.docker.json
  • Directorytests/
    • DirectoryApplication.Tests.Unit/
      • …
    • DirectoryInfrastructure.Tests.Integration/
      • …
    • DirectoryPresentation.Tests.Integration/
      • …
    • DirectoryPresentation.Tests.Unit/
      • …
  • Directory.agents/ Jacques and the skills your coding agent reads
    • …
  • .github/workflows/ci.yml formats, builds and tests with the 95% coverage bar
  • docs/RUN.md
  • README.md
  • AGENTS.md the map for coding agents
  • CLAUDE.md points Claude Code at AGENTS.md
  • WorksOnMyMachine.Movies.slnx
  • Directory.Build.props build rules and analyzers for every project
  • Directory.Packages.props every package version, in one place
  • Dockerfile
  • docker-compose.yml the server, an OpenTelemetry Collector and the Aspire dashboard
  • otel-collector.yaml where the collector sends logs, traces and metrics
  • global.json
  • NuGet.config
Project References Notes
Presentation Application, Infrastructure References Infrastructure only to wire up dependency injection
Application none Owns the entities, the repository interfaces and the rules
Infrastructure Application Every class but DependencyInjection is internal