Menu

Post image 1
Post image 2
Post image 3
Post image 4
Post image 5
Post image 6
Post image 7
Post image 8
Post image 9
Post image 10
Post image 11
Post image 12
Post image 13
Post image 14
Post image 15
Post image 16
Post image 17
Post image 18
Post image 19
Post image 20
Post image 21
Post image 22
Post image 23
Post image 24
Post image 25
Post image 26
Post image 27
Post image 28
1 / 28
0

From toy AI to production: the MCP problem no one talks about, and how to save 90% on costs

Medium·Fabio Matricardi·26 days ago
#wYiaSo1E
Reading 0:00
15s threshold

The moment everything with my AI agents fell apart and how I solved the infrastructure issue, not the model one. Press enter or click to view image in full size Even if I feel quite ashamed, I need to confess something. Three months ago, I sat staring at my Claude usage bill and I swear I felt my soul leave my body. I hit the token limits every single day, for one month. And it was only me! This was a huge defeat for me: I am really a fan of local AI and llama.cpp and for the first time I was trying to see what would have been of my productivity using a top tier LLM. And if this happened to me, I cannot even imagine if I had to work on a team project in my Company… That’s when I knew: something had gone terribly wrong with how I’d set up my MCP infrastructure. And there is also an additional embarrassing part: I tried to connect only eight MCP servers. It was a test, an experiment, my way to understand what these damn MCPs are and if they are really useful . But eight: that’s supposed to be simple, right?…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More