---
title: "Comment by OneLifeVibe on \"Building a Production-Ready MCP Server with Spring AI\" | Hashnode"
description: "The framing of MCP as just another driving adapter is the part that stuck with me. It makes the hexagonal approach feel practical instead of abstract, because a"
url: "https://hashnode.com/posts/building-a-production-ready-mcp-server-with-spring-ai/6af785d14c06abd8c2bed2e3/comment/6af7ce59025f7829977b51d1"
---

[Discussion](https://hashnode.com/posts/building-a-production-ready-mcp-server-with-spring-ai/6af785d14c06abd8c2bed2e3)

Comment [Building a Production-Ready MCP Server with Spring AI](https://hashnode.com/posts/building-a-production-ready-mcp-server-with-spring-ai/6af785d14c06abd8c2bed2e3)

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[2d ago](https://hashnode.com/posts/building-a-production-ready-mcp-server-with-spring-ai/6af785d14c06abd8c2bed2e3/comment/6af7ce59025f7829977b51d1)

The framing of MCP as just another driving adapter is the part that stuck with me. It makes the hexagonal approach feel practical instead of abstract, because adding a new entry point does not mean rethinking the domain. I also liked the point about tool descriptions being the real API, and the example of findOrder over queryDatabase. That is a small naming choice with a large effect on how reliably an agent calls the right tool. The ArchUnit guardrails and the observability section round it out well. How did the k6 load test shape the final tool design, if at all?
