Free · no signup · browser-local

MCP Configuration Diff with Redacted Credentials

Compare servers and fields in two MCP configs independent of JSON key order. Review added, removed and changed settings with sensitive values hidden by default.

Browse all tools →

Local document tools · no commands run · no endpoint requests

Compare MCP configurations

BeforeSource clientConfiguration · strict JSON

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

Import JSON file

AfterSource clientConfiguration · strict JSON

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

Import JSON file

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 ↗

Comparison report

mcp-diff-redacted.json

Added0

Removed0

Changed1

Unchanged0

Show actual values in this preview · may expose secrets

Default masking covers all env/header values, argument arrays and complete URLs, including path, userinfo, query and fragment. Names and commands remain visible. Secret changes still count as changes.

Show servers

local-exampleChanged

$.argsChanged

Before: "[REDACTED]"

After: "[REDACTED]"

$.commandChanged

Before: "node"

After: "python"

$.env.MODEUnchanged

Before: "[REDACTED]"

After: "[REDACTED]"

$.transportUnchanged

Before: "stdio"

After: "stdio"

Include actual private values in copy/download · explicit export choice

Copy and download remain redacted, even when the preview shows values.

{
  "format": "mcp-config-diff/v1",
  "referenceDate": "2026-11-03",
  "sourceClient": "desktop",
  "targetClient": "desktop",
  "redacted": true,
  "servers": [
    {
      "name": "local-example",
      "status": "changed",
      "fields": [
        {
          "path": "$.args",
          "status": "changed",
          "before": "[REDACTED]",
          "after": "[REDACTED]"
        },
        {
          "path": "$.command",
          "status": "changed",
          "before": "node",
          "after": "python"
        },
        {
          "path": "$.env.MODE",
          "status": "unchanged",
          "before": "[REDACTED]",
          "after": "[REDACTED]"
        },
        {
          "path": "$.transport",
          "status": "unchanged",
          "before": "stdio",
          "after": "stdio"
        }
      ]
    }
  ],
  "summary": {
    "added": 0,
    "removed": 0,
    "changed": 1,
    "unchanged": 0
  }
}

Getting started

Select each configuration’s client, paste or import the before and after JSON, filter statuses and expand field changes. Export a redacted JSON report by default.

Before you use the result

This compares the documented subset locally, not connection health. Names and commands remain visible; env/header values, arguments and complete URLs are masked. Private preview and export require separate choices.

Try an example

Compare a node-to-python command change, one removed server and a token rotation without exposing credential values.

How it works

Object-key order is ignored while array order and actual secret changes are preserved. Client transport markers are normalized; Cursor URL negotiation remains distinct from explicit VS Code HTTP.

Frequently asked questions

Compare MCP servers and fields with stable Added, Removed, Changed and Unchanged results and private values masked by default.

How do I use MCP Config Diff?

Select each configuration’s client, paste or import the before and after JSON, filter statuses and expand field changes. Export a redacted JSON report by default.

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?