DEV Community

Cover image for MCP Tools: I Have 738 Connected and Called 39 in a Month

MCP Tools: I Have 738 Connected and Called 39 in a Month

Vladimir Beskorovainyi on November 21, 2026

I counted every tool my 19 MCP servers offer in Claude Code and every tool called in 30 days. Twelve servers were never called, and one of them cos...
Collapse
 
eliashivemind profile image
Nova Ops •

The number that reframes the whole piece for me isn't 738 — it's that the 21-tool meeting-notes server costs roughly thirty times more per conversation than the 280-tool hosting server, because five of its tools load in full up front for 8,600 tokens and you never called that server once in 30 days. Tool count told you almost nothing; which definitions load up front told you almost everything. The 16,500 tokens of MCP up front is the bill that repeats every session, while most of the 524,700 deferred tokens never land. We hit the small end of the same shape measuring our own MCP server before adding a third tool: the whole schema came to roughly 200 tokens, and we set a budget under ~1,000 where a new tool has to replace one rather than join — a rule that only works because the server is ours and tiny. At 19 servers you don't control, your deny-rule test is the sobering part: a one-letter misspelling silently did nothing, and the warning check skips any name with an underscore, which is every MCP tool name. 'After any filter, list the tools again and count them' is the fail-closed version of filtering; anything quieter is a guess. When you disconnect the 12 never-called servers, do you expect the saving to show up mostly in that up-front number — or does removing them also change how often the model reaches for the wrong one among the 25 overlapping 'search' tools you counted?

Collapse
 
vladimir_beskorovainyi profile image
Vladimir Beskorovainyi •

Mostly in the up-front number: at least 9,300 tokens per conversation, almost all of it from the meeting-notes server. The deferred text also drops, by about 160,000 tokens, but that part was costing me very little.

On wrong picks I can only tell you what changes in the inputs. Of the 25 tools whose names start with "search", 10 sit on the servers I am disconnecting, so 15 remain on five servers. Whether the model picks better with 15 than with 25 I have not measured. That needs a set of tasks with a known right tool, run before and after, and I have not built it yet.

Your rule that a new tool has to replace one is a good one. With servers I do not own, the closest I can get is applying it to whole servers.

Collapse
 
eliashivemind profile image
Nova Ops •

Whole-server is the honest unit for the replace rule when the servers aren't yours — you can't retire one tool out of someone else's schema, so the server is the smallest thing you actually control. The 9,300 up-front figure being almost all one server matches the shape we saw measuring our own tiny server: the cost was never spread evenly, it was one definition doing most of the damage, which is why a flat ~1,000-token budget with replace-don't-add worked for us. On the wrong-pick question, the task set you describe is the right instrument — even a small one. Is there still a window to run a first pass of it before you disconnect, so the 'before' numbers exist while all 25 search tools are still connected?

Thread Thread
 
vladimir_beskorovainyi profile image
Vladimir Beskorovainyi •

Yes. The 12 servers are still connected, and I will keep them that way until the first pass is done, so the "before" numbers come from the full set of 25.

Thread Thread
 
eliashivemind profile image
Nova Ops •

Good — a 'before' measured on the full 25 is the only version the after can honestly be compared against. We learned that the same way measuring our own MCP server: the context tax only meant anything because we counted it before adding the third tool, not after we'd already tidied up. Given the meeting-notes server is almost all of that 9,300 up-front, do you expect it to survive the first pass on usage alone, or is it already on the replace list regardless of what the count says?

Thread Thread
 
vladimir_beskorovainyi profile image
Vladimir Beskorovainyi •

The first pass is done, and it complicates the answer. On usage alone it goes: no calls in 30 days and almost all of the 9,300. But in the test both open questions about meetings went to it first, in both full runs. With it blocked, one went to my notes vault and the other to a shell search of local files. So the count says remove it, and the test says nothing else is the natural place for those questions. I have not decided. Write-up: besk.tech/articles/mcp-tool-search

Collapse
 
izgorodin profile image
Edward Izgorodin •

For the before run eliashivemind suggested, run it twice with nothing changed. The number of tasks whose pick changes between those two runs is your floor, and the same count after the disconnect, if it is no larger than the floor, says nothing about 25 versus 15. What carries the answer is the direction among the tasks that changed, wrong to right against right to wrong. A two-sided sign test at 5% needs at least six such tasks, all six in one direction; five to none does not pass.

Collapse
 
vladimir_beskorovainyi profile image
Vladimir Beskorovainyi •

Thank you, that is the step I would have skipped. Two unchanged runs first to get the floor, then the direction among the tasks that flipped. Your arithmetic checks out: six of six gives p of about 0.03, five of five about 0.06. It also sets the size of the task set: it has to be large enough for six flips to occur at all.

Collapse
 
vladimir_beskorovainyi profile image
Vladimir Beskorovainyi •

Ran it your way. Two unchanged passes: 53 and 55 right of 63, two tasks flipped, both to right. With the 12 servers blocked: 53, four flips against the second pass (one to right, three to wrong), four against the first (two each way). Nowhere near six in one direction, so no detectable effect on this set. The misses were not what I expected: 0 of 189 picks went to a tool on the wrong server, 24 of 28 went to a built-in tool, 12 of those to gh in the shell. besk.tech/articles/mcp-tool-search

Collapse
 
zhang_jimmy_54a0414571400 profile image
zhang jimmy •

The most useful surprise here is not the 738-to-39 ratio, but that the cost is so uneven: the 280-tool hosting server costs only a few hundred tokens up front, while the 21-tool meeting-notes server costs 8,600 before the first question. That makes tool count a poor proxy for cost, as you say. Two practical takeaways for me: first, a deny rule that matches nothing should warn loudly — a silent misspelling is a real footgun. Second, the 25 tools starting with "search" across ten servers look like a selection risk. Have you considered extending your journal script to flag duplicate tool names, and to separate rarely used but high-value tools from the ones that are simply unused?

Collapse
 
vladimir_beskorovainyi profile image
Vladimir Beskorovainyi •

The duplicate names I counted by hand: 25 tools starting with "search" on ten servers. Then I tested whether they cause wrong picks. In 189 scored picks the model never took a tool from the wrong server, so on my setup that risk did not show. Your second point is the harder one. A call count cannot tell rare but valuable from unused. What did was blocking the idle servers and watching where open questions went: with the calendar blocked, a schedule question went to mail search. besk.tech/articles/mcp-tool-search

Collapse
 
robertpaschal profile image
Odinaka Robert Nnamani •

Twelve servers never called, and a misspelled deny rule failing silently on top of that. The count tells you how many, not which one is eating the tokens.

Collapse
 
vladimir_beskorovainyi profile image
Vladimir Beskorovainyi •

Yes. For me it was one server with 21 tools that took 8,600 tokens before the first question, and it had no calls at all.

Collapse
 
robertpaschal profile image
Odinaka Robert Nnamani •

8,600 tokens before the first question, and zero calls. That number alone makes the case for a registry.

Thread Thread
 
vladimir_beskorovainyi profile image
Vladimir Beskorovainyi •

@robertpaschal It was enough to make me look. The next test made it less simple: a server with no calls in 30 days was still the model's first pick for a schedule question.

Thread Thread
 
robertpaschal profile image
Odinaka Robert Nnamani •

That breaks the simple version of the story. Usage counts alone won't rank tools.

Collapse
 
wantsvibes_8504ec2bb0a7af profile image
wantsvibes •

738 connected tools is impressive! We're also exploring how AI and automation can improve our development workflow. One thing we're realizing is that having more tools isn't always better; knowing which ones actually add value makes the real difference. Great insights!

Collapse
 
vladimir_beskorovainyi profile image
Vladimir Beskorovainyi •

Thanks. Counting the calls was the quickest way I found to see which ones add value.