MCP in production: the good, the bad and the ugly
a year ago
- #Software Development
- #MCP
- #AI Integration
- Boris Radulov discusses his experience with MCP (Machine Communication Protocol) in a production environment.
- He built a custom web app for a Bulgarian construction materials company to help salespeople log site visits and data, replacing paper and note apps.
- The initial UI was disliked by salespeople, leading to a pivot to a chatbot interface using MCP.
- MCP allowed quick integration with Claude Desktop to access MongoDB for client and sales data.
- Despite the ease of setting up tools for data interaction, debugging and deployment issues were significant.
- MCP's three main capabilities (Resources, Tools, Prompts) were critiqued, with Tools being the most useful.
- The protocol's current form is seen as overengineered and not yet ready for widespread adoption.
- Radulov remains optimistic about text and speech-based computer interaction but doubts MCP's current viability.