Why I'm building ConfKit
It started with frustration. I was deep into building with AI—Claude Desktop for conversations, Cursor for coding, Gemini CLI for quick terminal tasks. Each one powerful on its own. But every time I discovered a useful MCP server, I had to configure it in three different places.
Copy-paste the same JSON. Hunt for where each client stores its config. Wonder why one client connects fine while another throws cryptic errors. I'd spend more time managing configs than actually building.
One evening, after the third time I forgot to update an API key across all my clients, I thought: "This is ridiculous. Why isn't there one place to manage all of this?"
That question became ConfKit. A single source of truth for every MCP server, every secret, every client. Configure once, sync everywhere. No more duplicate configs. No more "works on Claude but not on Cursor" mysteries.
I'm building ConfKit because I need it myself—every single day. And if you're juggling multiple AI clients like me, I think you'll need it too.
Want to chat about MCP workflows or share ideas? I'd love to hear from you.
☕Grab 15 min with me