Menu

Post image 1
Post image 2
1 / 2
0

"Cutting MCP token bloat by 12x: what happened when we packed 31 tools into one server"

DEV Community·Takayuki Kawazoe·21 days ago
#7ICxOF1t
#mcp#claude#python#codens#tool#five
Reading 0:00
15s threshold

Earlier this week @akshay_pachaar summarized a year of MCP-vs-CLI arguing into one sharp line: "The MCP vs CLI debate. For most of 2025, AI Engineers argued about it. The skeptics had real numbers: Playwright MCP eats 13.7K tokens, Chrome DevTools MCP eats 18K. A 5-server setup burns 55K tokens before any work." He is right. Those numbers are the steady drumbeat against MCP as a delivery format. If your agent burns 55K tokens just advertising capabilities, the protocol starts to look like a tax. We just shipped a counter-data point. codens-mcp is a single Python package that exposes 31 tools across five products (Purple, Red, Blue, Green, Auth, plus a cross-product registration tool). I sat down with wc -c and a calculator and got a number I had to triple-check: the entire tool surface, descriptions and all, is ~4,720 tokens. That is roughly 12x less than the 5-server number in the tweet, and about 3x less than Playwright MCP alone. This is not a "look how clever we are" post.…

Continue reading — create a free account

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

Read More