json-tools
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., "@json-tools validate data.json against schema.json"
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.
@mcpx-digital/json-tools
MCP server for everyday JSON/JSONC work on local files and strings.
Validate JSON or JSONC, get/set values with jq-like paths, pretty-print or minify, validate against JSON Schema (Ajv), and diff two documents — from Cursor or any MCP client.
Local only. Tools accept file paths or inline strings. They do not fetch URLs, scrape the web, or call external APIs.
Install (MCPX / npx)
npx -y @mcpx-digital/json-toolsPrepared for npm as
@mcpx-digital/json-tools. Until published, run from a local clone.
Related MCP server: Universal JSON Agent MCP
Cursor mcp.json example
{
"mcpServers": {
"json-tools": {
"command": "npx",
"args": ["-y", "@mcpx-digital/json-tools"]
}
}
}Local clone:
{
"mcpServers": {
"json-tools": {
"command": "node",
"args": ["/absolute/path/to/json-tools-mcp/index.js"]
}
}
}Tools
Tool | What it does |
| Strict JSON parse/validate |
| JSONC (comments + trailing commas) |
| Get value at |
| Set value at path (optional write) |
| Pretty-print |
| Minify |
| Ajv JSON Schema validation |
| Line-oriented diff of two JSON docs |
Example prompts
“Validate this JSONC config and pretty-print it”
“Get
.dependencies.reactfrom package.json”“Diff these two API response fixtures”
“Validate data.json against schema.json”
Development
git clone https://github.com/TheoryofShadows/json-tools-mcp.git
cd json-tools-mcp
npm install
npm test
node index.jsSell / list on MCPX
Suggested listing price: $7.
Install command: npx -y @mcpx-digital/json-tools
License
MIT © TheoryofShadows
Available Tools
8 toolsdiff_jsonB
Diff two JSON documents (canonical key-sorted stringify, line-oriented). Local files/strings only. Does not fetch URLs or contact external services.
Inputs: jsonc, leftText, maxDiffs, rightText, +2 more.
json_getA
Get a value at a jq-like path (e.g. .foo.bar[0]). Local files/strings only. Does not fetch URLs or contact external services.
Inputs: path (required), text, filePath.
json_setA
Set a value at a jq-like path; returns updated JSON (optionally write file). Local files/strings only. Does not fetch URLs or contact external services.
Inputs: path (required), text, value, indent, +4 more.
minify_jsonA
Minify JSON to one line. Local files/strings only. Does not fetch URLs or contact external services.
Inputs: text, filePath, outputPath.
pretty_jsonB
Pretty-print JSON with indentation. Local files/strings only. Does not fetch URLs or contact external services.
Inputs: text, indent, filePath, outputPath.
schema_validateA
Validate JSON data against a JSON Schema using Ajv. Local files/strings only. Does not fetch URLs or contact external services.
Inputs: jsonc, dataText, schemaText, dataFilePath, +1 more.
validate_jsonA
Parse and validate strict JSON. Local files/strings only. Does not fetch URLs or contact external services.
Inputs: text, filePath.
validate_jsoncA
Parse JSONC (comments + trailing commas) and validate. Local files/strings only. Does not fetch URLs or contact external services.
Inputs: text, filePath.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: validation (strict vs JSONC), get/set by path, formatting (pretty/minify), schema validation, and diffing. No two tools overlap in functionality.
Most tools follow a verb_noun pattern (validate_json, pretty_json, minify_json, diff_json), but json_get and json_set reverse the order to noun_verb, creating a minor inconsistency. Overall the pattern is readable and predictable.
Eight tools cover a focused domain of JSON utilities without redundancy. This count is well-scoped for the server's purpose.
The tool surface covers the core lifecycle of JSON manipulation: validation, access, modification, formatting, schema checking, and comparison. No obvious gaps for the stated domain.
Maintenance
Related MCP Connectors
Repair broken JSON without changing values, find the exact error, outline or query big payloads.
Compare two JSON files deeply, regardless of order. Get a detailed difference report highlighting…
Remote MCP: JSON repair, JSON Schema validation, JSON to TypeScript, CSV to JSON and JSON to CSV.
Compare two JSON files deeply without worrying about key or array order. Detect missing, extra, an…
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables efficient JSON file editing with targeted read, write, delete, and deep merge operations using dot notation paths, optimized for managing multilingual projects and large configuration files.430 npm1MIT
- AlicenseBqualityBmaintenanceEnables natural language interaction with JSON files, providing tools to load, query, aggregate, transform, and export data directly from AI editors.263MIT
- AlicenseNot gradedqualityDmaintenanceEnables reading, writing, and deleting JSON values using dot-notation paths, with automatic creation of files and nested objects.1MIT
- AlicenseNot gradedqualityCmaintenanceProvides tools to validate, format, and query JSON strings via MCP. Enables AI agents to work with JSON data without needing keys or internet.131 npmMIT