Gabriel AlmirPTTwo boundaries
MCP serves agents; REST keeps a conventional integration path.
lab / experimental
MCP AnimagineXL
How can image generation be exposed through MCP and REST without hiding the GPU boundary?
01 / Context
An exploration of tool contracts over local models, packaging, and GPU resources.
- Large models and GPUs are operational dependencies.
- MCP and REST must describe the same capability.
02 / Architecture map
Architecture map
- 01MCP / REST
Input contracts.
- 02Model + GPU
Explicit operational dependency.
- 03Image
Implemented output.
03 / Decisions
Decisions
Evidence
- ImplementationServer, endpoints, and Docker in the repository.
Known limits
- A laboratory, not a product or production service.
- Capacity and latency depend on model and hardware.