Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Compare two JSON documents deeply, ignoring key and array order, with every difference pathed.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"jsondiff": {
"command": "npx",
"args": [
"-y",
"@reneturcios/jsondiff",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add jsondiff -- npx -y @reneturcios/jsondiff mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"jsondiff": {
"command": "npx",
"args": [
"-y",
"@reneturcios/jsondiff",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"jsondiff": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/jsondiff",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
npx @reneturcios/jsondiff compare '<json1>' '<json2>'
npx @reneturcios/jsondiff compare --file1 a.json --file2 b.json npx @reneturcios/jsondiff --version
Both inputs are JSON strings; with --file1 / --file2 they are read from files instead. Output is the comparison report as 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.
The same bin serves a stdio MCP server:
npx -y @reneturcios/jsondiff mcp
MCP client config:
{
"mcpServers": { "jsondiff": { "command": "npx", "args": ["-y", "@reneturcios/jsondiff", "mcp"] } } }
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 stringjson2 (string, required) — the second JSON document, as a JSON stringDifference 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 run -i ghcr.io/cloudcorprecords/jsondiff # stdio MCP server
docker run --rm ghcr.io/cloudcorprecords/jsondiff compare '{"a":1}' '{"a":2}'
npm install
npm run build # tsc -> dist/ npm test # tsx --test test/*.test.ts (pure local, no network) npm run dev # run the CLI from source
MIT — Copyright (c) 2026 Rene Turcios