Taming MCPs, Skills, and Agent Chaos with ToolHive

Source: Dev.to

I use a lot of AI coding tools—OpenCode, Antigravity, Claude Code, Codex, Gemini CLI, Pi, Zed, GitHub Copilot, and probably others too. I’m having a ton of fun coding and learning each of these systems, but ultimately I need to understand them because my job is helping developers make sense of this stuff.

I’m lucky to have a (reasonably) unlimited AI budget. However, managing what feels like 30 different tools has become a pain. Every tool wants its own config, MCP setup, skills folder, auth, etc. Trying every AI dev tool has stopped feeling like product research and started feeling like I’m torturing a tiny fleet of confused robots.

A Dream of Consistency

I am painfully organized at times. My sprawling collection of agents feels out of hand. It isn’t strictly difficult to reconfigure an MCP server or drop in a skill I need, but I want a more consistent experience across every tool.

If I (read: my agents) create a skill, I do not want to copy it into six different folders. This has been the real pain point for me:

• AI tool sprawl is the new dotfile hell.

What I Tried (Today)

I bumped into the Stacklok/ToolHive folks at a couple of conferences and finally had time to try out their project today. Initial thoughts are pretty positive.

I ended up using their CLI and desktop app, ToolHive Studio (GitHub). My hope was that ToolHive could become the control plane for:

• Running MCPs
• Storing auth credentials
• Distributing skills

Most importantly, I wanted one command that could register an MCP or skill across all of my coding agents.

It mostly worked! There was still plenty of configuration and testing to do, but I am pretty happy with where I landed. I now have the start of a governable setup that works across my agents.

I ran into a Podman configuration issue with their official package. Skills are still a beta/alpha feature and needed to be enabled to be used inside Studio. Their built‑in playground worked well for testing.

Takeaways

• If you’re using one AI coding tool, config is an annoying chore. The agent can probably configure itself.
• When you’re using ten coding tools, config is a nightmare.
• ToolHive made my system governable and solved a real problem for me right now. I needed a control plane. It’s not perfect, but it’s useful in exactly the way I needed: one place to make the growing pile of AI tools behave like an environment instead of a junk drawer.