I Got Tired of Configuring MCP Servers in Every AI Tool Separately

You know the drill. You finally get your MCP server set up perfectly in Claude Code — filesystem access, your custom search tool, whatever. Then you open Cursor for a different task and realize you have to do the whole thing again. Then Gemini CLI ships and you think "hey, let me try this" and it's config time again. I've lost more hours than I care to admit to this exact loop. That's what led me to Mantra. It solves this specific pain point so cleanly that I wanted to write it up. ## The Core Problem: MCP Config Fragmentation The MCP (Model Context Protocol) ecosystem is genuinely exciting — being able to give your AI coding assistant access to tools, databases, APIs, and custom context is a game changer. But the reality of managing MCP servers across multiple tools is painful: - Each tool (Claude Code, Cursor, Gemini CLI, Codex) has its own config format - Adding a new MCP server means touching multiple files in multiple places - Skills and slash-command configurations are similarly siloed - When something breaks, you're debugging across different log formats and locations This fragmentation means you end up with either a lowest-common-denominator setup (only configure what you're willing to configure everywhere) or constant drift between tools. ## Mantra's MCP Unified Gateway Mantra's answer to this is a **unified MCP gateway**. You add your MCP servers once inside Mantra, and then Claude Code, Cursor, Gemini CLI, and Codex all automatically share that same set of tools and context. No more duplicating config. No more "wait, did I add this to Cursor too?" The model is simple: Mantra sits as a single source of truth for your MCP configuration, and each AI tool pulls from that shared layer. When you add a new MCP server, every tool gets it. When you remove one, it's gone everywhere. ## Skills Hub: Same Idea for Slash Commands and Prompts Beyond MCP servers, Mantra has a **Skills Hub** that does the same thing for Skills — the slash commands, reusable prompts, and workflow shortcuts that different AI tools support. The killer feature here is per-project association. You can define a set of skills and pin them to a specific project, and Mantra handles distributing them to the right tools when you're working in that project context. This is huge for teams where different projects have different conventions, or when you're context-switching between codebases with different tooling setups. ## Smart Takeover and the Built-in Inspector One thing I was worried about when trying Mantra: what happens to my existing config? I've got a reasonably complex Claude Code setup that I've refined over months. Mantra's **Smart Takeover** handles this gracefully. It imports your existing Claude Code or Cursor configuration, shows you a diff of what it found versus what it would manage going forward, and lets you do a shadow preview before committing. Everything gets atomically backed up, so you can roll back if anything feels off. For debugging, there's a **Built-in Inspector** with three parts: - **Tool Explorer**: browse every tool available across your MCP servers - **Tool Tester**: fire a test call to any tool directly, without needing to trigger it through a conversation - **RPC Log Viewer**: real-time log of every MCP request, so when something breaks you can see exactly what was sent and what came back The Tool Tester alone has saved me a lot of time. Being able to verify that a new MCP server is actually working before you start relying on it in a coding session is underrated. ## What Else Is in Mantra The MCP and Skills features are what drew me in, but Mantra also has: - **Replay / Git Time Travel**: replay AI coding sessions with the timeline anchored to git snapshots — useful for understanding what your AI assistant actually did during a long session - **Secure**: local scanning for API keys and tokens before they accidentally end up somewhere they shouldn't - **Remote SSH**: use all of this on a remote server, not just locally ## Worth Trying Mantra is completely free and requires no account signup, which lowered the barrier enough that I just tried it rather than adding it to my "maybe someday" list. If you're using more than one of Claude Code, Cursor, Gemini CLI, or Codex and you're tired of keeping MCP server configs in sync manually, it's worth 20 minutes to check out: [https://mantra.gonewx.com?utm_source=devto&utm_medium=article&utm_campaign=devto-article-launch](https://mantra.gonewx.com?utm_source=devto&utm_medium=article&utm_campaign=devto-article-launch) The unified MCP gateway is the main pitch, but the Inspector tools alone might justify it for anyone doing serious MCP server development.