I keep messing up my MCP config files, so I built a visual generator

Every time I set up a new MCP server for Claude Desktop, I end up in the same loop: copy some JSON from a README, tweak the paths, fat-finger a comma, wonder why nothing works, stare at the config for 10 minutes, find the typo. I figured there had to be a better way. There wasn't. So I built one. What even is MCP? If you haven't touched it yet — MCP (Model Context Protocol) is how AI apps like Claude Desktop, Cursor, and Windsurf connect to external tools. Want Claude to read your files? Search the web? Query your database? You need an MCP server, and that means editing a JSON config file by hand. The config looks something like this: { "mcpServers" : { "filesystem" : { "command" : "npx" , "args" : [ "-y" , "@modelcontextprotocol/server-filesystem" , "/Users/me/projects" ], "env" : {} } } } Simple enough for one server. But once you're running GitHub + Slack + PostgreSQL + Brave Search + a couple more, the config turns into a wall of JSON that's begging for a missing comma. What I buil