---
title: "Comment by Mirna De Jesus Cambero on \"Building a Customer-Facing MCP Server: What Do You Actually Need?\" | Hashnode"
description: "Totally agree with you. The AI client doesn't know your data model—that's exactly why good tool descriptions and the right context matter so much. AI is smart,"
url: "https://hashnode.com/posts/building-a-customer-facing-mcp-server-what-do-you-actually-need/6a47ef4f6a19961ca143144c/comment/6a4af4f2686f49c6dcc4fed9"
---

[Discussion](https://hashnode.com/posts/building-a-customer-facing-mcp-server-what-do-you-actually-need/6a47ef4f6a19961ca143144c)

Comment [Building a Customer-Facing MCP Server: What Do You Actually Need?](https://hashnode.com/posts/building-a-customer-facing-mcp-server-what-do-you-actually-need/6a47ef4f6a19961ca143144c)

[Mirna De Jesus Cambero](https://hashnode.com/@mirnadjc)

[Jul 6](https://hashnode.com/posts/building-a-customer-facing-mcp-server-what-do-you-actually-need/6a47ef4f6a19961ca143144c/comment/6a4af4f2686f49c6dcc4fed9)

Totally agree with you. The AI client doesn't know your data model—that's exactly why good tool descriptions and the right context matter so much. AI is smart, but the quality of the outcome is often only as good as the clarity of the input and context you provide.

I couldn't agree more about the stdio part as well. I got my server working with stdio pretty quickly, and it was a great way to get my feet wet. But I soon realized it was really just a prototype, and that building a production-ready MCP server meant moving to HTTP to support multiple users and proper session handling.

Thanks for stopping by and taking the time to leave such a thoughtful comment!

[Opportunity Biz](https://hashnode.com/@opptybiz)

[Jul 6](https://hashnode.com/posts/building-a-customer-facing-mcp-server-what-do-you-actually-need/6a47ef4f6a19961ca143144c/comment/6a4af4f2686f49c6dcc4fed9#reply-6a4b821f4baf028a0efbeee6)

The session isolation point is where most production issues surface — the typical trap is passing auth context at server init instead of per-request, so the first time two users hit the server concurrently, one session's context bleeds into the other. Worth calling out explicitly in a follow-up article if you cover the multi-tenant path in more depth.