The project assumes the MCP standard as a stable contract between agents and server capabilities, instead of ad hoc message formats. The architecture is layered: a shared core (MCP server instance, shared types, tool registry), a pluggable transport (streamable HTTP by default, stdio as an alternative), and domain modules loaded from configuration with isolated tool namespaces. Modules are not hard-coded into the main entrypoint—enablement, options, and content roots come from config and environment variables. Portfolio content is read-only, stored in files (Markdown + manifest), with safe path joining (path traversal protection). Operationally, the system should be deployable as an HTTP service (e.g. in a container) with configurable host/port and an optional internal bearer token, while keeping a clear separation of concerns across layers.