Built a visual MCP config generator for AI tools — free, no signup
Hey everyone 👋
I've been building free browser-based dev tools at webtoolz.dev. Started with JSON tools, added a Mermaid diagram editor, and now just shipped something for the AI tooling crowd.
The problem
If you use Claude Desktop, Cursor, or Windsurf with MCP servers (the protocol that connects AI to external tools like GitHub, databases, file systems, etc.), you know the setup involves hand-editing JSON config files. One wrong comma and nothing works.
There are 100+ MCP servers out there now, each with different args, env vars, and setup steps. Every time I wanted to add a new one, I'd spend 15 minutes reading a GitHub README to figure out the exact config format.
What I built
A visual MCP config generator with a catalog of 40+ servers. You pick what you want, fill in your API keys, choose your AI client (Claude Desktop, Cursor, etc.), and it generates valid config JSON.
- 40+ pre-configured server templates
- 6 AI clients supported (each has slightly different formats)
- Custom server support for anything not in the catalog
- Share links to send configs to teammates
- 100% client-side — your API keys never leave your browser
Link: webtoolz.dev/ai/mcp
The market angle
MCP is blowing up right now. Claude Code hit 72K GitHub stars, agent frameworks are trending daily, and everyone's trying to connect AI to their existing tools. But the config experience is still "copy JSON from a README and pray."
I'm betting this drives organic search traffic as more people adopt MCP. The tool is free (no plans to charge), monetization is through the broader webtoolz.dev platform.
Stack: Next.js, fully static, deployed on Vercel. Zero backend.
Would love feedback from anyone using MCP servers. What's missing? What servers should I add to the catalog?
Great tool!
One thing I've noticed exploring MCP is that most servers have no monetization layer — agents can call tools but there's no native pay-per-call mechanism. Has been an interesting problem to tackle. Do you plan to support remote MCP servers with token authentication? That would open the door to premium/paid tools too.
This is a lifesaver, Kai! Hand-editing JSON configs and hunting for ENV vars in READMEs is definitely the 'dark ages' of MCP setup.Your 'client-side only' approach for API keys is a huge trust builder. I’m currently building AgentShare (a price & offer data layer for agents) and I’d love to see it in your catalog once we’re fully public.Quick question: Are you planning to support 'remote' MCP servers that require bearer token auth in your generator? That seems to be where the 'Agent era' is heading to avoid local resource bottlenecks.Bookmarking webtoolz [dot] dev for my team!