Version 0.7.2 of mcptoon adds no new token compression. No new spec support. No new agent integrations. The whole release is about what happens in the thirty seconds after somebody types pip install mcptoon, and a contributor friend of mine thinks that is a wasted release. I think it is the highest-leverage thing I shipped all month.
Here is the reasoning. A developer tools project lives or dies on its first run. Not the docs, not the benchmark table, the first run. People paste one command, watch the output, and their brain quietly votes keep or delete. If that first run ends in a config error, the tab closes and the repo becomes another star they forgot about. My earlier quickstart was functional and completely forgettable, which in practice means the same thing as broken.
So 0.7.2 rebuilt the first run around three moments.
The install got shorter. There are now one-line installers for every common platform:
curl -fsSL https://raw.githubusercontent.com/activeing123/mcptoon/main/install.sh | bash
irm https://raw.githubusercontent.com/activeing123/mcptoon/main/install.ps1 | iex
The shell script tries pipx first, falls back to pip --user, and if the system Python is distro-managed (the PEP 668 externally-managed-environment wall) it builds a venv on its own. The Windows script finds the py launcher, fixes PATH when it can, and tells you honestly when it cannot. Both end by launching quickstart for you, so the installer is not a dead end.
The quickstart got a payoff. When setup finishes, it closes with the actual count from your machine: N tools ready across M servers, followed by exactly two commands worth running next, sync to write the configs into every agent and serve to expose everything as one stdio gateway. That is the celebration screen. If you are scripting and think party output is nonsense, --dry keeps it sober, plain next-steps only. The celebration is earned, not decorative: it only prints real numbers it just counted on your disk.
The demo got a punchline. mcptoon demo used to open with a table, which is the correct format for verification and the wrong format for a first impression. Now it leads with one plain sentence, something like: SAME data, 99 percent fewer tokens, 12,400 to 117. Then the detailed table for people who want to check the math. Then a "Now you can" checklist. The order matters. The headline number is computed live from your own servers, so it is not a marketing claim I typed, it is a measurement your machine just made.
That last point is the whole philosophy of the release, so let me be precise about it. I did not add these numbers to make the tool feel bigger. I added them so the user never has to take my word for anything. The demo runs before and after on the user's actual config, with the user's actual servers, using the same tokenizer both times. If the number is unimpressive on your setup, the tool tells you so on your screen, and you can uninstall with two minutes lost. That honesty did more for the project than any feature list.
The honest limits of the release itself: the celebration screen is cosmetic and skips cleanly with --dry, the installers assume common layouts and will not handle exotic Python setups, the PEP 668 fallback targets distro-managed Pythons specifically, and demo percentages still vary by tokenizer, expect 10 to 25 percent difference from what your provider bills. The new flows carry their own fresh test file, and everything else in the suite stays green.
Compression, spec support, agent coverage, those features got people to install. The first thirty seconds decide whether they stay. One release for thirty seconds is a trade I will make every time.
Top comments (0)