Session

Protocol Solved, Design Still Open: Domain-Driven Design for MCP Servers

The Model Context Protocol (MCP) went from zero servers in late 2024 to thousands within a year, most thin wrappers over REST endpoints and database tables. When agents fail, it's rarely the model that's weak; it's that the tool surface is incoherent. We're repeating the REST-over-CRUD mistakes of the 2010s, one layer up.
An MCP tool is an API contract for a non-deterministic consumer: the name, description, and schema are all the agent has to work with. Domain language is a reliability concern, not an aesthetic one.
This talk shows how Domain-Driven Design maps onto MCP design. Building on Anthropic's finding that code execution can cut token usage by up to 98.7%, the question isn't "should we build an MCP server?" but "which capabilities are tools, which are code APIs, and which are skills?"
A before-and-after example leaves you with a repeatable method: start from the bounded context, classify each capability by surface, and name tools in your business's words, not your database's.

Fabrizio Lazzaretti

Senior Managing Consultant @ Wavestone | CNCF Ambassador | Speaker | Author

Zürich, Switzerland

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top