
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
json-explorer-mcp
Advanced tools
An MCP (Model Context Protocol) server for efficiently exploring large JSON files without loading entire contents into context. Designed to help AI assistants navigate complex JSON data structures while minimizing token usage.
$ref resolutionnpm install -g json-explorer-mcp
Or use directly with npx:
npx json-explorer-mcp
Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"json-explorer": {
"command": "npx",
"args": ["-y", "json-explorer-mcp"]
}
}
}
Add to .mcp.json in your project:
{
"mcpServers": {
"json-explorer": {
"command": "npx",
"args": ["-y", "json-explorer-mcp"]
}
}
}
| Tool | Description |
|---|---|
json_inspect | Get file overview: size, structure type, depth-limited preview |
json_keys | List keys/indices at a path with types and previews |
json_get | Get value at path (auto-truncates large values) |
json_search | Search for keys or values matching a pattern (regex) |
json_sample | Sample items from arrays (first, last, random, range) |
json_stats | Aggregate statistics for arrays |
| Tool | Description |
|---|---|
json_schema | Infer JSON schema from data at a path |
json_validate | Validate against JSON Schema (file, URL, or inline) |
is_json | Check if a file contains valid JSON |
| Tool | Description |
|---|---|
json_set | Set value at path with optional schema validation |
json_format | Reformat with configurable indent and key sorting |
| Tool | Description |
|---|---|
list_templates | List available templates with metadata and schema URLs |
get_template | Get full template details including all examples |
create_json | Create file from template example |
create_template | Create a new user template definition |
add_template_example | Add example to existing user template |
Prompts are reusable workflow templates that guide the AI through common tasks.
| Prompt | Description |
|---|---|
explore-json | Get started exploring a JSON file with overview and suggestions |
validate-config | Validate a config file (tsconfig, package.json, etc.) against SchemaStore |
create-config | Create a new configuration file from a template with guidance |
Templates include metadata, usage instructions, multiple examples, and schema URLs for validation.
| Template | Schema | Examples |
|---|---|---|
tsconfig | tsconfig.json | minimal, strict, library |
package | package.json | minimal, typescript, library |
eslint | eslintrc.json | basic, typescript |
prettier | prettierrc.json | default, minimal |
mcp-config | - | basic, multiple |
vscode-launch | - | node, node-attach, jest |
vscode-tasks | - | npm |
vscode-settings | - | typescript |
// List available templates
list_templates()
// Get full template details
get_template(template: "tsconfig")
// Create a file from a template example
create_json(
template: "tsconfig",
example: "strict",
outputFile: "tsconfig.json"
)
// Create with overrides
create_json(
template: "package",
example: "typescript",
outputFile: "package.json",
overrides: { name: "my-project", version: "1.0.0" }
)
| Variable | Description |
|---|---|
JSON_EXPLORER_TEMPLATES | Directory path for user template definitions |
JSON_EXPLORER_NO_NETWORK | Set to 1 to disable all network requests |
JSON_EXPLORER_NETWORK_TIMEOUT | Network request timeout in seconds (default: 30) |
Create custom templates by setting JSON_EXPLORER_TEMPLATES to a directory path:
{
"mcpServers": {
"json-explorer": {
"command": "npx",
"args": ["-y", "json-explorer-mcp"],
"env": {
"JSON_EXPLORER_TEMPLATES": "/path/to/templates"
}
}
}
}
Create a JSON file in your templates directory (e.g., my-config.json):
{
"description": "My application configuration",
"usage": "Place in project root to configure the app",
"filePatterns": ["myconfig.json", ".myconfig"],
"schemaUrl": "https://example.com/schema.json",
"examples": [
{
"name": "basic",
"description": "Minimal configuration",
"content": {
"setting": "value"
}
},
{
"name": "advanced",
"description": "Full configuration with all options",
"content": {
"setting": "value",
"debug": true,
"options": {}
}
}
]
}
The filename (without .json) becomes the template name.
// Create a new template
create_template(
name: "my-config",
description: "My application configuration",
usage: "Place in project root",
filePatterns: ["myconfig.json"],
schemaUrl: "https://example.com/schema.json",
exampleName: "basic",
exampleDescription: "Minimal configuration",
exampleContent: { setting: "value" }
)
// Add another example to an existing template
add_template_example(
templateName: "my-config",
exampleName: "production",
exampleDescription: "Production configuration",
exampleContent: { setting: "value", debug: false }
)
Validate files against remote schemas from SchemaStore:
json_validate(
file: "package.json",
schema: "https://json.schemastore.org/package.json",
resolveNetworkRefs: true,
strict: false
)
Note: Very large schemas (like tsconfig) may timeout due to AJV compilation complexity.
Get an overview of a JSON file including size, structure type, and a depth-limited preview.
json_inspect(file: "/path/to/data.json")
Returns:
{
"file": "/path/to/data.json",
"size": "13.1 MB",
"type": "object",
"preview": {
"users": "[... 1000 items]",
"config": "{... 5 keys}"
},
"topLevelInfo": "Object with 2 keys: users, config"
}
List all keys (for objects) or indices (for arrays) at a given path with type info and previews.
json_keys(file: "/path/to/data.json", path: "$.users")
Retrieve the value at a specific path. Large values are automatically truncated.
json_get(file: "/path/to/data.json", path: "$.users[0]")
Set a value at a specific JSONPath with optional schema validation.
// Simple set
json_set(
file: "/path/to/data.json",
path: "$.users[0].name",
value: "New Name"
)
// With schema validation
json_set(
file: "/path/to/data.json",
path: "$.users[0]",
value: { id: 1, name: "Alice" },
schema: "/path/to/user-schema.json"
)
// With inferred schema (validates type matches existing)
json_set(
file: "/path/to/data.json",
path: "$.config.maxRetries",
value: 5,
inferSchema: true
)
// Dry run (validate without writing)
json_set(
file: "/path/to/data.json",
path: "$.config.enabled",
value: true,
dryRun: true
)
Reformat a JSON file with configurable indentation and optional key sorting.
json_format(
file: "/path/to/data.json",
indent: 2,
sortKeys: true,
outputFile: "/path/to/formatted.json"
)
Validate JSON data against a JSON Schema with support for $ref resolution.
// With inline schema
json_validate(
file: "/path/to/data.json",
schema: { type: "object", required: ["id"] },
path: "$.users[0]"
)
// With schema file (local $refs resolved automatically)
json_validate(
file: "/path/to/data.json",
schema: "/path/to/schema.json"
)
// With network schema
json_validate(
file: "/path/to/data.json",
schema: "https://json.schemastore.org/package.json",
resolveNetworkRefs: true,
strict: false
)
// With schema directory (loads all schemas by $id)
json_validate(
file: "/path/to/data.json",
schemaDir: "/path/to/schemas/",
schemaId: "main-schema"
)
Get aggregate statistics for array fields.
json_stats(file: "/path/to/data.json", path: "$.users")
Returns field-level statistics including counts, distributions, and numeric stats.
All path parameters support JSONPath syntax:
$ - Root object$.foo - Property access$.foo.bar - Nested property$.users[0] - Array index$.$id - Special keys with $ prefix$["special-key"] - Bracket notation for special charactersBy default, network resolution is disabled. Enable per-request with resolveNetworkRefs: true.
To completely disable network requests (overrides all options):
{
"mcpServers": {
"json-explorer": {
"command": "npx",
"args": ["-y", "json-explorer-mcp"],
"env": {
"JSON_EXPLORER_NO_NETWORK": "1"
}
}
}
}
All referenced schemas are validated to ensure they're actual JSON Schema objects before use.
# Install dependencies
npm install
# Build
npm run build
# Run tests
npm test
# Run in development mode
npm run dev
MIT
FAQs
MCP server for efficiently exploring large JSON files
We found that json-explorer-mcp demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.