jsonloupe
Related Servers
Alternatives to jsonloupe
- AlicenseBqualityBmaintenanceEnables natural language interaction with JSON files, providing tools to load, query, aggregate, transform, and export data directly from AI editors.26240 PyPI3MIT
- AlicenseNot gradedqualityAmaintenanceLets agents and CLI users inspect the shape of large JSON and JSONL files and extract exactly the values they need using jq-like expressions, returning compact bounded results instead of flooding context.1MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables efficient reading, analyzing, and querying of Excel, CSV, and JSON files with support for chunked processing, column/field filtering, and streaming for large datasets. Supports multiple transport protocols (stdio, HTTP, SSE) for flexible integration.39 npm4ISC
- AlicenseNot gradedqualityCmaintenanceEnables exploring and querying structured data (JSON, JSONL, CSV, TSV) via shape, read, find, and diff operations, with bounded resource usage.4 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to explore and analyse local CSV, Parquet or JSON files through validated read-only SELECT queries, with schema discovery, profiling and query-plan tools. Results are capped, timed, PII-masked and audit-logged inside a locked DuckDB sandbox that cannot write, reach the network or read other files.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage plain .jsonl files as tables, offering tools to list libraries and tables, query data, and upsert rows while preserving byte-for-byte fidelity on unchanged rows.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to inspect and extract data from local CSV, TSV, JSONL and log files far larger than available RAM, using bounded memory, crash-resilient resumable runs, and streamed progress. All file access is confined to user-approved directories, keeping the data private to the machine.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to query Excel, CSV, Parquet, and NDJSON files as SQL tables, joining data across formats and sheets and exporting results to CSV or Excel.1Apache 2.0
TDQS
Scored across 12 tools
Most tools target distinct operations (load, query, checks, profile, sample, export, convert), and descriptions explicitly cross-reference alternatives. However, get_schema/inspect/profile/sample/run_query have some overlapping schema/value/statistics territory, and export_csv is a near-duplicate shortcut of export_result, so an agent must read carefully to choose.
All names use snake_case and are readable, with most following verb_noun (load_doc, run_query, get_schema, export_result). Occasional single-verb/noun names (inspect, convert, profile, sample) are minor deviations but still understandable.
12 tools is appropriate for a JSON analysis/query/conversion/export surface; each capability (load, schema, query, checks, profile, sample, export, diff, conversion) has a clear role. No excessive duplication or trivial single-tool thinness.
The surface covers loading, schema discovery, querying, validation checks, profiling, sampling, diffing, exporting, and table conversion. For an analysis-focused JSON tool, this provides complete lifecycle coverage without obvious dead ends.