tumiki-mcp-proxy-architecture

Define clear service boundaries and separate write operations as commands from read operations as queries. Applying CQRS in the features layer reduces coupling and maintains explicit responsibilities for each MCP proxy feature slice.

The best way to add a feature is following the vertical slice pattern across defined layers and registering it in the mcpServerFactory with appropriate handlers. This keeps new features cohesive without increasing system coupling.

Yes, you can combine DDD and vertical slices for MCP proxy development. The architecture uses DDD to define domain and shared layers while using vertical slices across those layers to keep feature delivery clean and independent.

Use layered architecture for an MCP proxy to manage system complexity and enable clean feature delivery. Explicit inter-layer import rules and separated infrastructure prevent tangled dependencies as the proxy scales.

Import rules dictate strict dependencies between the domain, shared, infrastructure, and features layers. These explicit rules prevent unauthorized cross-layer references, ensuring the MCP proxy maintains its modular boundaries.