Hi! 👋 As a developer, I work across multiple IDEs and AI-powered tools every day - JetBrains IDEs, VS Code, Cursor, Windsurf, Antigravity, Claude Code, Jan, and more. When MCP (Model Context Protocol) came along, I was excited. Finally, a standardized way for AI agents and tools to talk to external services. But the reality hit hard - every time I added a new MCP server, I had to manually configure it across every single tool I use. One server, five tools, five configurations. Ten servers... you can do the math. It became a tedious, error-prone ritual that killed my productivity. Then one day I noticed something even worse - the same MCP server was running multiple instances at the same time. VS Code spawned one, Cursor spawned another, Claude Code spawned yet another. Each tool had no idea the others existed. Wasteful, messy, and honestly just wrong. That was the moment I decided to build MCP Server Manager. The idea is simple: one central place to manage all your MCP servers - their configurations, health, and lifecycle. And the best part? It exposes itself as a single MCP server via HTTP transport with streaming support. Your IDEs and AI agents just connect to one endpoint and instantly access every tool you've configured. No more repetitive configurations. No more duplicate instances. Just clean, orchestrated MCP management. I built this because I was tired of being my own DevOps team just to keep my AI tools in sync. Hope it helps you too! 🚀 Would love to hear your thoughts and feedback! 🙌

MCP Server Manager - Orchestrate, configure, and control your MCP servers

Replies