jsonDiff
执行json对比
LABSCO SUMMARY
The README names the three failure modes precisely, and anyone who has asked a model to diff JSON has seen all three.
A model comparing two large JSON documents will confidently report keys as identical when they are not, will sometimes answer by writing a comparison script rather than comparing, and when it does compare will return a wall of output where the one meaningful difference is buried. Moving the comparison to deterministic code removes all three at once. It is a small tool aimed at a specific and real weakness, which is the best argument a single-tool server can make. Documentation and tool text are in Chinese.
What it is
A single-tool JSON comparison service, written specifically because models handle this badly: they misjudge equality, generate comparison code instead of comparing, and produce output too verbose to act on.
What you get
- jsonDiff performs the comparison and returns the differences directly.
Requirements
Nothing to supply.
Setup effort
One command — uvx mcp-jsondiff-kel@latest
USE CASES
01
Finding what actually differs between two JSON documents
Compare them deterministically and get the differences back, instead of a model judging equality or writing a script to do it.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
- uvx on PATH
- Python 3.13+
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-jsondiff-kel": {
"command": "uvx",
"args": [
"mcp-jsondiff-kel@latest"
]
}
}
}uvx
TERMINAL
uvx mcp-jsondiff-kel@latest
