# JSON Diff Visualizer MCP for AI Agents AI Agent Connect > JSON Diff Visualizer MCP generates human-readable visual diffs between two JSON objects. It highlights additions in green and removals in red, making it easy to see what changed in your configuration files or data structures at a glance. It works like a git diff but specifically understands JSON hierarchies, so reordered keys don't trigger false positives. Use it to quickly review deployment manifests, database schemas, or any other complex JSON data. ## Overview - **Category:** productivity - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_PjogYuSo0eUsN0io0gSr8mpblTI9yU0xaPCv8dub/ai-agent-connect - **Tags:** json-diff, version-control, data-comparison, visualization, config-management ## Description Your deployment pipeline just updated a config file, and you need to know exactly what changed before you hit approve. Standard diff tools often treat JSON as plain text, which means a simple change in key order can clutter your view with hundreds of false positives. This Connector solves that by understanding the actual structure of your data. It generates a visual, colorized diff with plus and minus markers that any developer can read instantly. You get a clean summary of what was added, what was removed, and what stayed the same. It's built for high-stakes environments where you need to verify changes in deployment manifests, database schemas, or API configurations without squinting at raw text. If you're already using a deep-diff engine for programmatic checks, you can use this Connector to provide the human-readable proof your team needs. You'll find it's a lot easier to spot a single incorrect replica count when it's highlighted in green against a sea of gray. It's one of the many specialized tools you can find in the Vinkius catalog to bridge the gap between machine-readable data and human-readable reports. This means your agent can act as a reviewer, presenting you with a clear picture of the changes rather than dumping a wall of text. It turns a tedious review process into a quick glance. ## Tools ### diff_json Pass two JSON strings to get a machine-readable structural diff and a human-readable visual diff with plus and minus markers. ## Prompt Examples **Prompt:** ``` Show me a visual diff between our staging and production API configs so I can review before approving the deploy. ``` **Response:** ``` I've compared the staging and production configurations. Here is the visual diff of the changes: ```diff - "replicas": 2 + "replicas": 3 - "timeout": "30s" + "timeout": "60s" ``` **Summary:** * **Added:** Increased replica count and timeout. * **Removed:** Old timeout settings. * **Unchanged:** All other 42 configuration keys remain the same. ``` **Prompt:** ``` Compare the old and new Terraform state files and show me what infrastructure changed. ``` **Response:** ``` I've analyzed the Terraform state changes. Here are the modifications: **Infrastructure Changes:** * **Modified:** `aws_instance.web_server` (Instance type updated) * **Added:** `aws_s3_bucket.assets_storage` (New bucket created) * **Deleted:** `aws_security_group.temp_rules` (Removed) Visual diff for `aws_instance.web_server`: ```diff - "instance_type": "t3.medium" + "instance_type": "m5.large" ``` ``` **Prompt:** ``` Post the JSON config changes to our Slack #deployments channel for team review. ``` **Response:** ``` Here is the formatted diff for the #deployments channel: ```diff - "memory_limit": "512Mi" + "memory_limit": "1Gi" - "max_connections": 100 + "max_connections": 200 ``` Ready to copy and paste into Slack. ``` ## Capabilities ### Highlight additions in green New fields in your JSON objects appear with green plus markers for easy identification. ### Mark removals in red Deleted fields are clearly shown with red minus markers so you don't miss them. ### Ignore key reordering The tool recognizes structural changes only, so moving keys around won't trigger false diffs. ### Provide structural diffs Get a machine-readable map of every change made to the data structure. ### Create Slack-ready summaries The output is formatted perfectly for pasting into communication tools or PR comments. ## Use Cases ### Staging vs Production Config Review An engineer asks their agent to show the difference between the staging and production API configs to ensure no secrets were leaked. ### Terraform State Verification A DevOps lead compares old and new Terraform state files to see exactly which infrastructure resources were modified. ### Database Schema Migration Check A developer verifies that a database schema snapshot only contains the intended new columns without affecting existing data. ### Deployment Manifest Approval A reviewer uses the agent to summarize changes in a large JSON deployment manifest before approving a production push. ## Benefits - Eliminate false positives by using diff_json to ignore key order during comparisons. - Spot errors faster in large deployment manifests with clear green and red markers. - Share clean, readable change logs in Slack or PR comments with a single prompt. - Verify database schema snapshots with exact path markers for high accuracy. - Reduce human error during high-stakes config approvals with instant visual feedback. ## How It Works The bottom line is you get a human-readable summary of exactly what changed in your JSON data without the noise of plain text comparisons. 1. Provide the old and new JSON objects to your agent. 2. The Connector compares the structures and identifies specific additions, removals, and modifications. 3. You receive a colorized visual diff and a structural map of the changes. ## Frequently Asked Questions **Can the JSON Diff Visualizer MCP show me what changed in my config?** Yes. It compares two JSON objects and highlights exactly what was added, removed, or changed. It presents this in a colorized format that is easy for humans to read quickly. **Does the JSON Diff Visualizer MCP handle reordered keys?** Yes, it does. Unlike standard text diffs, this Connector understands JSON structure. If your keys are in a different order but the data is the same, it won't flag them as changes. **Can I use the JSON Diff Visualizer MCP for deployment manifests?** That is one of its primary uses. It's perfect for reviewing Kubernetes manifests, Terraform states, and other deployment configurations to ensure only the intended changes are made. **How does the JSON Diff Visualizer MCP handle large JSON files?** It identifies the specific paths of changes within large files, allowing you to see the modifications without having to scroll through hundreds of lines of unchanged data. **Can the JSON Diff Visualizer MCP output a diff for Slack?** Yes. The output is designed to be human-readable and easy to copy-paste into Slack or other team communication tools for quick peer review. **Is the JSON Diff Visualizer MCP good for database schema snapshots?** Yes. It's highly effective for comparing database schema snapshots, helping you verify that your migrations only affect the fields you intended to change. **How is this different from deep-diff-engine?** deep-diff-engine returns structured change objects for programmatic processing (CI/CD pipelines, automated alerts). json-diff-visualizer returns human-readable text with +/- markers for visual review (Slack, PR comments, approval workflows). Use both together. **Does reordering keys show as a change?** No. The diff is structural — {a:1,b:2} and {b:2,a:1} show zero differences because the data is semantically identical. **Can I use the output in Slack or GitHub PR comments?** Yes. The output is plain text with +/- markers — paste directly into code blocks in Slack, GitHub, or any markdown-compatible platform.