Jsondiff

io.github.CloudCorpRecords由 GitHub 账号 CloudCorpRecords 发布v0.1.0更新于 Nov 3, 2026

深度比较两个JSON文档,忽略键和数组顺序,并标出每一处差异的路径。

AI 翻译由 AI 模型根据下方的原文描述翻译,可能有误。

原文描述

Compare two JSON documents deeply, ignoring key and array order, with every difference pathed.

已验证STDIO仅桌面

概览

Jsondiff 的本地 MCP 服务;无需登录;STDIO。

暂无 AI 概览:以下信息来自注册中心条目和服务本身。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Jsondiff,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

jsondiff

Compare two JSON documents deeply, without worrying about key or array order. jsondiff walks both documents at every level and reports each difference it finds — a key that exists on one side only, a value that differs, or a value whose JSON type differs — with the exact dotted path of the difference, a per-kind summary, and an overall identical / different status.

It is pure local computation: no upstream API, no account, no API key, no configuration.

CLI

bash
npx @reneturcios/jsondiff compare '<json1>' '<json2>'npx @reneturcios/jsondiff compare --file1 a.json --file2 b.jsonnpx @reneturcios/jsondiff --version

Both inputs are JSON strings; with --file1 / --file2 they are read from files instead. Output is the comparison report as JSON:

json
{  "status": "different",  "total_differences": 2,  "differences": [    {      "type": "missing_key",      "path": "root.user.settings.language",      "key": "language",      "file1_value": "tr",      "message": "Key 'language' exists in file1 but missing in file2"    },    {      "type": "value_mismatch",      "path": "root.user.name",      "file1_value": "Ahmet Yılmaz",      "file2_value": "Mehmet Demir",      "message": "Value mismatch at 'root.user.name'"    }  ],  "summary": {    "missing_keys": 1,    "extra_keys": 0,    "value_mismatches": 1,    "type_mismatches": 0  }}

Exit codes: 0 on success, 1 on a runtime error (including an input that is not valid JSON — the error names the input), 2 on a usage error.

MCP server

The same bin serves a stdio MCP server:

bash
npx -y @reneturcios/jsondiff mcp

MCP client config:

json
{  "mcpServers": {    "jsondiff": {      "command": "npx",      "args": ["-y", "@reneturcios/jsondiff", "mcp"]    }  }}

Tools

  • compare_json — Compare two JSON strings deeply and order-independently, and report every difference (missing keys, extra keys, value mismatches, type mismatches) with full path tracking.
    • json1 (string, required) — the first JSON document, as a JSON string
    • json2 (string, required) — the second JSON document, as a JSON string

Difference kinds: missing_key (in the first document only), extra_key (in the second only), value_mismatch (same JSON type, different content), type_mismatch (different JSON types). Arrays are compared order-independently: an element with no deep-equal partner on the other side is reported as a value mismatch.

Docker

bash
docker run -i ghcr.io/cloudcorprecords/jsondiff            # stdio MCP serverdocker run --rm ghcr.io/cloudcorprecords/jsondiff compare '{"a":1}' '{"a":2}'

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # tsx --test test/*.test.ts (pure local, no network)npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios

来源:README.md,提交 2983fa1

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.0最新Nov 3, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分