How do I use JSON Analyser MCP?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@JSON Analyser MCP Show the schema and preview first 10 records of transactions.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.

JSON Analyser MCP

by contactakagrawal

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

JSON Analyser MCP

A specialized Model Context Protocol (MCP) server for analyzing large JSON files with memory-efficient streaming capabilities.

Features

Memory-Efficient Streaming: Process gigabyte-sized JSON files without loading them entirely into memory
Advanced Querying: Search JSON data with multiple operators and conditions
Schema Detection: Automatically analyze JSON structure and field types
Chunk Processing: Iterate through large datasets in manageable chunks
Multi-Field Queries: Complex queries with AND logic across multiple fields
Unique Value Analysis: Extract unique values for any field
Performance Tracking: Monitor processing times and memory usage

Related MCP server: mcp-json-yaml-toml

Installation

npm install -g json-analyser-mcp

Usage

As MCP Server

Add to your MCP client configuration:

{
  "mcpServers": {
    "JSON Analyser MCP": {
      "command": "npx",
      "args": ["-y", "json-analyser-mcp", "--stdio"]
    }
  }
}

Available Tools

1. `read_json`

Get an overview and preview of a JSON file.

{
  "filePath": "path/to/data.json",
  "fields": ["field1", "field2"], // optional
  "detectSchema": true // optional, analyzes field types
}

2. `query_json`

Search for specific data with various operators.

{
  "filePath": "path/to/data.json",
  "query": {
    "field": "trading_symbol",
    "operator": "contains", // contains, equals, startsWith, endsWith, regex, gt, lt, gte, lte
    "value": "TITAN",
    "caseSensitive": false // optional
  },
  "maxResults": 1000 // optional
}

3. `get_json_chunk`

Process JSON data in sequential chunks.

{
  "filePath": "path/to/data.json",
  "fields": ["field1", "field2"], // optional
  "start": 0,
  "limit": 1000
}

4. `multi_query_json`

Execute multiple queries with AND logic.

{
  "filePath": "path/to/data.json",
  "queries": [
    {
      "field": "category",
      "operator": "equals",
      "value": "technology"
    },
    {
      "field": "price",
      "operator": "gt",
      "value": 100
    }
  ],
  "maxResults": 500
}

5. `get_unique_values`

Extract unique values for a specific field.

{
  "filePath": "path/to/data.json",
  "field": "category",
  "maxValues": 1000
}

Query Operators

contains: Field value contains the search string
equals: Exact match
startsWith: Field value starts with the search string
endsWith: Field value ends with the search string
regex: Regular expression matching
gt: Greater than (numeric)
lt: Less than (numeric)
gte: Greater than or equal (numeric)
lte: Less than or equal (numeric)

Performance Benefits

Streaming Architecture: Uses stream-json for memory-efficient processing
Large File Support: Can handle multi-gigabyte JSON files
Fast Searches: Optimized for quick data retrieval
Minimal Memory Footprint: Processes data without loading entire files

Use Cases

Data Analysis: Explore large datasets without memory constraints
Log Processing: Search through application logs efficiently
API Response Analysis: Process large API response files
Data Migration: Extract and transform data from JSON exports
Research: Analyze research datasets and survey responses

Example Workflows

Analyzing Trading Data

// 1. First, get an overview
read_json({ filePath: "NSE.json", detectSchema: true })

// 2. Search for specific stocks
query_json({
  filePath: "NSE.json",
  query: { field: "trading_symbol", operator: "contains", value: "TITAN" }
})

// 3. Get unique sectors
get_unique_values({ filePath: "NSE.json", field: "sector" })

Processing Support Tickets

// 1. Get overview
read_json({ filePath: "tickets.json" })

// 2. Find high-priority open tickets
multi_query_json({
  filePath: "tickets.json",
  queries: [
    { field: "status", operator: "equals", value: "open" },
    { field: "priority", operator: "equals", value: "high" }
  ]
})

// 3. Process all tickets in chunks
get_json_chunk({ filePath: "tickets.json", start: 0, limit: 1000 })

Requirements

Node.js >= 18.0.0
Memory: Minimal (streams data)
Disk: Sufficient space for input JSON files

License

MIT

Contributing

Contributions welcome! Please open issues and pull requests on GitHub.

Support

For issues and questions, please use the GitHub issue tracker.

Available Tools

5 tools

get_json_chunkD

ParametersJSON Schema

Name	Required	Description
`limit`	No	Number of entries to return in the chunk (default 1000)
`start`	No	Entry index to start from (0-based)
`fields`	No	Fields to include in the output. If not specified, all fields are included.
`filePath`	Yes	Path to the JSON file on disk (.json)

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_unique_valuesD

ParametersJSON Schema

Name	Required	Description
`field`	Yes	The field to get unique values for
`filePath`	Yes	Path to the JSON file on disk (.json)
`maxValues`	No	Maximum number of unique values to return (default 1000)

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

multi_query_jsonD

ParametersJSON Schema

Name	Required	Description
`queries`	Yes	Array of queries to execute (AND logic)
`filePath`	Yes	Path to the JSON file on disk (.json)
`maxResults`	No	Maximum number of results to return (default 1000)

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

query_jsonD

ParametersJSON Schema

Name	Required	Description
`query`	Yes	The query to execute on the JSON data
`filePath`	Yes	Path to the JSON file on disk (.json)
`maxResults`	No	Maximum number of results to return (default 1000)

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

read_jsonD

ParametersJSON Schema

Name	Required	Description
`fields`	No	Fields to include in the output. If not specified, all fields are included.
`filePath`	Yes	Path to the JSON file on disk (.json)
`detectSchema`	No	Whether to analyze and return the JSON schema structure

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

5 tool updatesv1.0.0Sep 6, 2026
- First observedget_json_chunk
- First observedget_unique_values
- First observedmulti_query_json
- First observedquery_json
- First observedread_json

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.8/5.0

Scored 2026-09-06 13:15 across 5 tools

Disambiguation2/5

The boundaries between read_json, get_json_chunk, and query_json are unclear, especially since no descriptions are provided. multi_query_json also overlaps heavily with query_json, making tool selection ambiguous without additional context.

Naming Consistency3/5

Most tools use snake_case and a verb-first pattern, but the naming is not fully uniform: multi_query_json uses a modifier prefix, and get_unique_values lacks the _json suffix. The core pattern is readable but has notable deviations.

Tool Count5/5

Five tools is a reasonable, well-scoped count for a focused JSON analysis server. Each tool appears to cover a distinct aspect of reading or querying JSON without unnecessary bloat.

Completeness4/5

The set covers common JSON analysis needs: reading, chunked access, single queries, batch queries, and unique value extraction. Minor gaps like schema inspection or validation exist, but core analytical workflows are likely covered.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

mcpOAuth
com.bullpenstrategygroup.rotunda
An MCP server that provides congressional transcripts
Government Data Search Open Data
2
LemonadoOAuth
io.github.lemonadolabs
MCP server for querying and analyzing data from ad platforms, analytics tools, and spreadsheets
Marketing Research & Data Databases
3
thoughtsOAuth
ai.thoughtbox.api
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
Cloud Storage Finance
2
Motecloud MemoryOAuth
io.github.motecloud
Cloud-hosted MCP server for durable AI memory
Knowledge & Memory Cloud Platforms
2

Related MCP Servers

JSON Query MCP
Databases Search Developer Tools
mgraczyk
F
license
A
quality
D
maintenance
A Model Context Protocol server for querying large JSON files using JSONPath expressions, enabling LLMs to efficiently search and extract information from large JSON data.
Updated a year ago (2025-05-20 00:42 UTC)
3
11
-
mcp-json-yaml-toml
Developer Tools File Systems Code Analysis
bitflight-devops
A
license
A
quality
A
maintenance
A token-efficient, schema-aware MCP server that enables AI assistants to safely read, modify, query, and validate JSON, YAML, and TOML files with automatic schema detection and format conversion capabilities.
Updated 4 days ago (2026-09-18 21:53 UTC)
8
23 PyPI
9
MIT
log-mcp
Monitoring Observability
ascii766164696D
A
license
A
quality
D
maintenance
MCP server for log file analysis. Gives LLMs the ability to efficiently analyze large log files without loading them into context.
Updated 7 months ago (2026-02-28 20:40 UTC)
7
100
MIT
swagger-json-mcp
Developer Tools Documentation Access
LLM-MCP-Servers
F
license
A
quality
D
maintenance
A powerful MCP server for querying and processing large Swagger/OpenAPI JSON documents, enabling LLMs to efficiently access API documentation without loading entire files.
Updated a year ago (2025-11-04 07:10 UTC)
6
2
-

JSON Analyser MCP

Features

Installation

Usage

As MCP Server

Available Tools

1. read_json

2. query_json

3. get_json_chunk

4. multi_query_json

5. get_unique_values

Query Operators

Performance Benefits

Use Cases

Example Workflows

Analyzing Trading Data

Processing Support Tickets

Requirements

License

Contributing

Support

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

1. `read_json`

2. `query_json`

3. `get_json_chunk`

4. `multi_query_json`

5. `get_unique_values`