Free · no signup · browser-local

Merge MCP Server Configs with Explicit Conflict Rules

Combine local MCP configurations with explicit error, replacement or renaming strategies. Review which servers are retained before downloading the merged JSON.

Browse all tools →

Local document tools · no commands run · no endpoint requests

Merge MCP configurations

Target clientWhen server names conflict

Source configuration 1Source clientConfiguration · strict JSON

{
  "mcpServers": {
    "local-example": {
      "command": "node",
      "args": [
        "/absolute/path/to/server.js"
      ],
      "env": {
        "MODE": "read-only"
      }
    }
  }
}

Import JSON file

Choose servers to keep and optionally change their names. Unchecked servers are excluded; all input fields are still validated.

local-example

Source configuration 2Source clientConfiguration · strict JSON

{
  "mcpServers": {
    "second-local": {
      "command": "python",
      "args": [
        "/absolute/path/to/server.py"
      ],
      "env": {
        "MODE": "read-only"
      }
    }
  }
}

Import JSON file

Choose servers to keep and optionally change their names. Unchecked servers are excluded; all input fields are still validated.

second-local

Supported scope

Strict JSON only: 100 KB, depth 20, 5,000 nodes and 1–50 servers. stdio: command, args, env. Remote: url and string headers. Desktop uses local mcpServers; Cursor uses mcpServers and URL negotiation; VS Code uses servers with explicit type stdio/http.

Unknown fields (inputs, auth/oauth, envFile, cwd, sandbox, SSE type and others) block output. They may be valid client features. Cross-client variable expressions and numeric/null env values are blocked when semantics cannot be preserved. No connection or authentication is verified.

Conversion and merge exports retain your values and may contain credentials. Review them before sharing. The diff report masks values by default.

Official references checked 2026-11-03Claude Desktop · local MCP ↗Cursor · MCP ↗VS Code · MCP configuration ↗

Your JSON output

claude_desktop_config.json

Merge decisions

Addedconfig-1 · local-example → local-example
Addedconfig-2 · second-local → second-local

{
  "mcpServers": {
    "local-example": {
      "command": "node",
      "args": [
        "/absolute/path/to/server.js"
      ],
      "env": {
        "MODE": "read-only"
      }
    },
    "second-local": {
      "command": "python",
      "args": [
        "/absolute/path/to/server.py"
      ],
      "env": {
        "MODE": "read-only"
      }
    }
  }
}

Getting started

Import each source locally, choose its client and retained servers, set the target client and stop/replace/rename policy, then export JSON.

Before you use the result

Each input must fit the documented subset, including excluded servers. Later selected entries win in replace mode; renaming reserves names across all sources. No commands run.

Try an example

Keep two local server configs, rename one conflicting server and download a combined VS Code mcp.json.

How it works

Inputs are validated before merge; dangerous object keys are blocked. A stable name allocator avoids existing and future names, and a decision log lists retained, replaced, renamed and excluded entries.

Frequently asked questions

Merge 2–10 MCP JSON files with server selection, custom names and explicit conflict strategies.

How do I use MCP Config Merger?

Import each source locally, choose its client and retained servers, set the target client and stop/replace/rename policy, then export JSON.

Does this tool upload my data?

Inputs and files are processed in your browser. Page-view analytics do not contain your tool input.

What should I check before using the result?