MCP Product Canvas: designing what your MCP offers
The Model Context Protocol settles how AI agents talk to your systems. It does not settle what they should be able to do. The MCP Product Canvas gives teams a shared space to discuss the functions and data of an MCP offering. On one page, you capture which tools the server exposes, which resources it provides, which prompts guide its use, and who the MCP is for.
The canvas brings the strategic and tactical patterns of Domain-Driven Design to MCP. It helps you draw clear boundaries, use the language of your domain, and decide deliberately what an agent should see and do. This keeps you from simply wrapping existing endpoints.
The canvas was developed by Fabrizio Lazzaretti and Annegret Junker. It builds on their books Crafting Great APIs with Domain-Driven Design and AI meets DDD.
Designing other APIs? For synchronous and asynchronous APIs, use the companion template, the API Product Canvas.
Learn how to use it: We walk through the canvas in our talk “Protocol Solved, Design Still Open: Domain-Driven Design for MCP Servers.”
