How I Gave My AI Agents a Dynamic MCP Marketplace
I've written before about agent-comm, agent-tasks, and agent-knowledge — tools for giving AI coding agents coordination, task management, and persistent memory. But there was still one friction poi...

Source: DEV Community
I've written before about agent-comm, agent-tasks, and agent-knowledge — tools for giving AI coding agents coordination, task management, and persistent memory. But there was still one friction point I hadn't solved: getting the right MCP servers in front of the agent in the first place. The problem with static MCP configs is that everything is always on. Every server you've ever registered is running whether you need it or not. You want to add a new tool? Edit a JSON file, restart your agent. You want to try something from the official MCP registry? Good luck figuring out what's available and how to install it without leaving your coding session. I built agent-discover to fix this. The problem When you configure MCP servers in Claude Code (or any MCP client), you write a static config file. That list is fixed. All those servers load at startup. If you want to browse what else is out there, you leave the agent, search the internet, manually edit the config, and restart. It doesn't soun