Seven MCP servers isn't a platform, it's ...

Seven MCP servers isn't a platform, it's a blast radius

Sep 05, 2026

I had seven MCP servers turned on. GitHub, filesystem, a docs indexer, Playwright, something that talked to Linear, a half-finished Postgres adapter copied from a gist, and a "helpful" filesystem sibling pointing at my home folder because I was in a hurry on a Tuesday.

The agent was busy. It was not useful. It spent the first minute of every session listing tools, called the wrong one twice, and once opened a pull request with a token that could also delete the repo.

So I turned six off and packed the one job I actually repeat — open a draft PR from this branch, never merge, never touch main — into a single plugin folder. The week got quieter.

That's the One Socket rule: one live connection per job, everything else a paragraph in a skill file. And it clears up the three words people keep mixing: a skill is how, a server is access, a plugin is the envelope.

Name the job first. Then decide whether it needs a live wire at all — most don't.

The piece has the rule, a draft-PR skill you can steal, and a twenty-minute clean-out. 👇

📖 https://medium.com/@thebuildersplaybook/stop-shipping-another-mcp-server-ship-one-plugin-the-agent-can-reuse-220a31dedc89?sharedUserId=thebuildersplaybook

If it quiets your week too, a coffee keeps these coming. ☕❤️

image

Enjoy this post?

Buy Noor Mohammad a coffee

More from Noor Mohammad

PrivacyTermsReport