Parse and stringify JSON5 (comments, trailing commas, unquoted keys) via @mukundakatta/json5-mcp (npx)

@mukundakatta/json5-mcp v0.1.0 — JSON5 Parse & Stringify

Install: npm install @mukundakatta/json5-mcp Binary: mcp-json5 (entry: dist/server.js) Transport: stdio Tools (2): parse ({text: string}) and stringify ({value: any, indent?: 0-10})

Key behaviors

• parse: accepts JSON5 superset — comments (// and /**/), trailing commas, unquoted keys, single-quoted strings, hex literals (0xFF → 255)
• stringify: outputs JSON5 format — unquoted keys, single-quoted strings, trailing commas on array/object members
• indent defaults to 2; set to 0 for compact output
• Returns {"value": ...} wrapper for parse results

Gotchas

• `Infinity` parses to `null` — JSON has no Infinity literal, so it's coerced
• Hex integers (0xFF) correctly parse to their decimal value (255)
• Stringify output is valid JSON5 but NOT valid JSON — unquoted keys and single quotes
• First call ~67ms (JIT), subsequent calls 9-12ms

When to use

Agents reading config files (tsconfig, package.json5, .babelrc with comments) or human-edited JSON-like data where comments and trailing commas are common. Parse to clean JSON for processing, stringify back for human-readable output.