Parse and serialize INI config files (sections, comments, dot-notation nesting) via @mukundakatta/ini-mcp

Verified recipe: @mukundakatta/ini-mcp v0.1.0

Surface: @mukundakatta/ini-mcp — 2 tools, credential-free, stdio transport Install: npm install @mukundakatta/ini-mcp Entry: dist/server.js

Tool 1: to_json

Response shape: {value: {...}} — the parsed JSON is wrapped in a value key.

Tool 2: to_ini

Response: raw INI text (not JSON — don't JSON.parse it).

Key gotchas

• `to_json` wraps result in `{value: ...}` — extract .value to get the actual parsed object
• `to_ini` returns raw INI text — not JSON, just the INI string directly
• Dot-notation sections become nested objects — [section.subsection] → {section: {subsection: {...}}}
• Boolean `true`/`false` coerced — debug=true becomes JSON boolean true, NOT string
• Numbers stay as strings — port=5432 becomes "5432" not 5432 (only booleans coerced)
• Comments stripped — both ; and # style comments removed cleanly
• Quoted values unquoted — both single and double quotes handled
• Duplicate keys: last wins — host=first then host=second → "host": "second"
• Empty sections preserved in parse — [empty] → "empty": {}
• Empty sections DROPPED in serialize — {empty: {}} produces no [empty] section
• Empty string parses to `{}` — no error on empty input
• Whitespace around `=` stripped — host = 0.0.0.0 works correctly
• Round-trip lossy for numbers — INI port=3000 → JSON "port":"3000" → INI port=3000 (survives, but type changes)
• Sub-millisecond after JIT — first call ~10ms, subsequent 0.2-2ms

14 calls, 14 OK (100% success)

Round-trip tested: INI [server]\nhost=0.0.0.0\nport=3000 → JSON → INI produces identical output.