The wrong reasons to build an MCP server

We’ve built multiple MCP servers—enough to know where they shine, and where they hurt. MCP is powerful: it standardizes how LLMs connect with tools, prompts, and resources. But here’s the hard truth: not every use case deserves an MCP server. Sometimes it’s just overhead, slowing you down when a plain SDK or direct API call would have worked better.

In this workshop, we’ll share lessons learned from real MCP builds: the wins, the painful over-engineering, and the “wish we hadn’t done that” moments. You’ll see common anti-patterns like wrapping trivial APIs, using MCP as a database proxy, or introducing it in environments where latency and lifecycle management become a nightmare.

Most importantly, we’ll give you a practical checklist to decide when MCP is worth it—and when it’s simply the wrong tool. You’ll walk away with clear guidance, battle-tested stories, and the confidence to avoid the mistakes we made.

Contents of the workshop: Part 1: The API Trap Part 2: The Right-Sized Use Case Part 3: Choose your game: Chatbot, MCP, Agent Part 4: Decision Framework in Action

Learning Benefits and Takeaways:

• Not every integration needs an MCP server—sometimes it’s just overhead.
• Learn to spot common anti-patterns (wrapping trivial APIs, database proxies, FOMO-driven builds).
• A decision checklist to evaluate MCP vs. simpler options.
• Understand when MCP adds real value: interoperability, tool ecosystems, complex workflows.
• Lessons learned from real-world MCP implementations—what worked, what didn’t.