Allows comparison of TOML data, generating diffs between TOML structures, and processing TOML content for difference analysis
Supports comparison of XML data, generating diffs between XML structures, and processing XML content for difference analysis
Enables comparison of YAML data, generating diffs between YAML structures, and processing YAML content for difference analysis
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@diff-mcp compare these two JSON configs and show me what changed"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
powered by jsondiffpatch
compare text (using text diff powered by google-diff-match-patch )
compare data (json, json5, yaml, toml, xml, html) and get a readable diff in multiple output formats (text, json, jsonpatch)
Related MCP server: Unified Diff MCP Server
compare text or data and get a readable diff.
Inputs:
left (string | unknown[] | Record<string, unknown>): left text or data
leftFormat (string, optional): text, json, json5 (default), yaml, toml, xml, html
right (string | unknown[] | Record<string, unknown>): right text or data (to compare with left)
rightFormat (string, optional): text, json, json5 (default), yaml, toml, xml, html
outputFormat (string, optional): text (default), json, jsonpatch
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"diff": {
"command": "npx",
"args": [
"-y",
"diff-mcp"
]
}
}
}This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
compare text or data and get a readable diff
Inputs: state (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly stated and distinct by default.
The single tool name 'diff' is concise, descriptive, and matches the server's purpose. There is no mixed convention or inconsistency since there is only one tool.
One tool is on the low end of typical server sizes, but for a narrowly scoped diff utility it is a reasonable and focused set. It doesn't feel trivial since diff is a meaningful operation.
The server's stated purpose is to compare text or data and produce a readable diff, which is exactly what the tool provides. There are no obvious gaps for this single-operation domain.
Compare two JSON files deeply, ignoring order, to surface every difference. Get a clear, structure…
Compare two JSON files deeply, regardless of order. Get a detailed difference report highlighting…
Compare two JSON files deeply without worrying about key or array order. Detect missing, extra, an…
Returns what was added, removed or changed between two Apify datasets, files, Google Sheets or...
