🧑‍💻

MCP Config Merger

🔒 In your browser

Merge multiple MCP server configs into one file — deduped, with conflicts flagged.

How it works

Combine several MCP server configs into one file. Paste a JSON array of config objects (or one object with multiple servers) and get a single merged mcpServers block — deduplicated, with conflicts and hard-coded secrets flagged. Everything runs in your browser.

Root key

Merging keeps each server entry as-is; on a name clash the first wins and the conflict is flagged. Remote-server shapes can differ between clients, so after merging, validate the result with the MCP Config Validator. Nothing is uploaded.

🔬You might also need MCP tools/list Inspector →

About the MCP Config Merger

As you add more MCP servers, you end up copying entries between config files by hand — and one duplicate name or misplaced brace breaks everything. This free MCP config merger combines several configs into a single, valid file, deduplicates servers, and flags name conflicts and hard-coded secrets.

Everything is merged in your browser; nothing you paste, including any keys, is uploaded.

How to use it

Paste a JSON array of config objects — each a { "mcpServers": { … } } block — or a single object with several servers.
The tool merges every server into one mcpServers object and shows the combined file.
Choose the root key: mcpServers for most clients, or servers for VS Code.
Copy or download the merged mcp.json.

How conflicts and secrets are handled

If the same server name appears twice with different settings, the first wins and the clash is reported so you can resolve it deliberately. Identical duplicates are silently deduplicated. Any env value that looks like a real, hard-coded API key is flagged, because merged files are exactly the kind that get committed to a shared repo by accident.

Frequently asked questions

What input does it expect?

A JSON array of MCP config objects to merge (each with an mcpServers or servers block), or a single object containing several servers. It collects every server it finds and merges them.

What happens on a duplicate server name?

If the duplicates differ, the first definition is kept and the conflict is flagged for you to fix. If they're identical, the duplicate is removed silently.

Does it transform remote-server settings between clients?

No — entries are merged as-is. Remote (HTTP) server shapes can differ between clients, so validate the merged result with the MCP Config Validator before using it.

Are my keys uploaded?

No. Merging happens entirely in your browser, so any secrets in the configs stay on your device.

Related Developer tools

MCP Security Scanner MCP Config Generator MCP Config Validator Prompt Secret Redactor Prompt Injection Checker

🔗 Embed this tool on your website — free

Copy this and paste it into your page's HTML. The tool runs in the visitor's browser, just like here. Change height to fit, or add the optional auto-resize snippet below. Add ?theme=dark to the URL for dark mode.

<iframe src="https://toolhq.dev/embed/mcp-config-merger/" title="MCP Config Merger — ToolsHub" width="100%" height="520" style="border:1px solid #e5e7eb;border-radius:12px;max-width:680px" loading="lazy"></iframe>

Optional: auto-resize the iframe height

Add this once on the same page so the iframe grows to fit the tool:

<script>
addEventListener("message", function (e) {
  if (e.data && e.data.type === "toolshub:resize") {
    document.querySelectorAll('iframe[src*="/embed/"]').forEach(function (f) {
      if (f.contentWindow === e.source) f.style.height = e.data.height + "px";
    });
  }
});
</script>