MCPtrove interactive resource
MCP Config Merger — Combine mcpServers JSON With Conflict Detection
Combine existing mcpServers files without silently overwriting duplicate server names.
The reusable resource
A local multi-config merger that blocks unresolved name conflicts and exports ready-to-paste JSON.
MCP Config Merger combines multiple mcpServers JSON documents locally and stops duplicate server names from being silently overwritten.
Contents
- What the tool does
- How to use it
- How the analysis works
- How to interpret the output
- Limitations and privacy
- Practical next steps
- Related MCPtrove resources
- FAQ
What the tool does
MCP Config Merger combines two to five existing JSON configurations into one document. It is useful when server definitions are distributed across files, clients, machines, projects, or setup notes and you need one mcpServers object.
Each panel accepts either a complete configuration containing a top-level mcpServers property or a bare server map. You do not need to convert every source into the same format first. The output always uses a top-level mcpServers object, giving the merged file a consistent structure.
The main purpose is safe duplicate handling. When a server name appears more than once with the same definition, the tool deduplicates it and reports the identical duplicate. When the same name has different definitions, the tool leaves the conflict unresolved instead of silently selecting one.
This distinction is important because a changed command, argument, environment setting, path, or nested property can change how a client starts or communicates with a server. A repeated name is not automatically harmless, and the merger keeps that decision visible.
How to use it
1. Gather the source configurations
Open the MCP Config Merger and prepare two to five JSON documents. Use one panel for each source. Keep the documents close to their original form so you can compare the result with the configurations you trust.
The merger combines existing definitions; it does not repair malformed JSON, design new server entries, or decide which environment-specific values are appropriate.
2. Paste one document into each panel
Paste each configuration into its own panel. If a panel contains invalid JSON, the tool identifies that panel so you can correct the source directly.
Fix invalid input before relying on the merge summary. A complete merge requires every participating document to be readable JSON.
3. Review the summary
After processing, review the analysis summary. It reports the number of source configurations, merged servers, identical duplicates, resolved conflicts, and unresolved conflicts.
The merged server count can be lower than the total number of entries because identical definitions are represented once. That reduction is expected when several sources contain the same server definition.
4. Resolve conflicts explicitly
For a duplicate name with different definitions, choose one of the available actions:
- Keep first preserves the definition from the first matching occurrence.
- Keep last preserves the definition from the last matching occurrence.
These actions document a selection; they do not determine which definition is correct. Base the choice on the source you trust, the target environment, and the behavior you intend to keep. Because input order matters, confirm the panel order before resolving several conflicts.
5. Copy or download the result
When all conflicts are resolved, copy the merged configuration or download it as mcp-merged-config.json. Open the result and review every duplicated or resolved server before placing it in a client configuration location.
The merge is ready for further review when the output has the expected mcpServers structure, no unresolved conflicts remain, and the selected definitions match your intended setup.
How the analysis works
The tool performs structural comparison in the browser. It does not run the configured commands or attempt to connect to the servers.
| Stage | What happens | Result |
|---|---|---|
| Input parsing | Each panel is read as JSON | Invalid panels are identified |
| Shape handling | Full objects and bare maps are normalized | Entries are placed under mcpServers |
| Name collection | Server names are compared exactly | Repeated names are identified |
| Definition comparison | Repeated entries are compared structurally | Duplicates and conflicts are separated |
| Conflict handling | Conflicts wait for your selection | No definition is silently chosen |
| Output generation | A normalized object is assembled | A merged file is produced |
Structural equality uses normalized JSON key order. Two definitions with the same content but different property ordering can therefore be treated as identical. Values and structure still matter: different commands, arguments, environment values, paths, or nested objects can create a conflict.
Names are matched exactly. filesystem, Filesystem, and filesystem-local are treated as separate names. The tool does not infer relationships, rename servers, or combine similarly named entries.
How to interpret the output
Start with invalid panels. Correct those sources before treating the summary as complete. The panel label shows where the problem was found, but the merger is not a general-purpose JSON syntax or schema validator.
Then review the merged server count and duplicate categories. Identical duplicates usually need no policy decision, but they confirm that the same definition appeared in multiple sources. Conflicting duplicates require comparison before you select a result.
| Finding | Review question |
|---|---|
| Identical duplicate | Are these sources expected to share one definition? |
| Different command | Which launcher suits the target environment? |
| Different arguments | Which paths, flags, or scopes are intended? |
| Different environment values | Which values belong in the final setup? |
| Different nested fields | Is one definition newer or environment-specific? |
Keep first and Keep last select a complete definition. They do not merge individual fields. If one entry has the preferred command and another has the preferred environment settings, inspect both and edit the chosen result deliberately after the merge.
Limitations and privacy
Processing takes place in the browser. Even so, treat configuration text as sensitive. Avoid pasting credentials, private keys, access tokens, or other secrets unless you understand the risks associated with the browser session and surrounding environment.
The tool does not execute commands, resolve environment variables, validate credentials, test paths, start MCP servers, or prove compatibility with a particular MCP client. A structurally valid output may still need changes for the machine, operating system, permissions, or client where it will be used.
It also does not determine whether a server is safe. An unfamiliar command, path, or environment entry should prompt a review of its source and intended behavior. A successful merge is not a security assessment.
Practical next steps
If a source is malformed or you need a dedicated syntax and shape check, use MCP Config Validator.
After merging, use MCP Config Doctor for a broader review of commands, paths, environment settings, and other configuration risks.
If you are creating a configuration from scratch, use MCP Config Generator. A practical workflow is to validate uncertain sources, merge them, resolve conflicts, inspect the result with Config Doctor, and then test it in the intended client and environment.
Related MCPtrove resources
- MCP Config Validator — Check JSON syntax and configuration shape.
- MCP Config Doctor — Review post-merge configuration risks.
- MCP Config Generator — Build a new configuration from MCPtrove listings.
FAQ
How many configurations can I merge?
You can merge two to five JSON configurations, using one panel for each input.
Can I paste a bare server map?
Yes. An input can be a complete object containing mcpServers or a bare server map. The output always uses a top-level mcpServers object.
What happens when duplicate definitions are identical?
The tool keeps one copy, reports the identical duplicate, and includes the server once in the merged output.
What happens when the same name has different definitions?
The conflict remains unresolved until you choose Keep first or Keep last. The tool does not silently select a definition.
Does the tool verify that the merged configuration will work?
No. It does not run commands, resolve environment variables, validate credentials, or prove MCP client compatibility. Review and test the merged file in its target environment.