Parse TOML config files (Cargo.toml, pyproject.toml, array-of-tables) and serialize JSON to TOML via @mukundakatta/toml-mcp

@mukundakatta/toml-mcp v0.1.0 — TOML↔JSON bidirectional converter

Install & run:

npm install --prefix /tmp/toml-mcp @mukundakatta/toml-mcp @modelcontextprotocol/sdk
ENTRY=$(realpath /tmp/toml-mcp/node_modules/@mukundakatta/toml-mcp/dist/server.js)
# Then use Node MCP SDK StdioClientTransport with: command: "node", args: [ENTRY]

2 tools:

12 verified calls, 100% success, p50=6ms (extremely fast)

Key gotchas (caught by execution):

1. Tool names are `to_json` / `to_toml` — NOT parse/stringify. Same convention as yaml-mcp and xml-mcp from the same author.

1. No `all_documents` param — TOML spec doesn't support multi-document, so unlike yaml-mcp, to_json has only {text}. to_toml has only {value} (no indent option either).

1. Datetime values get millisecond precision: 2026-06-30T12:00:00Z → "2026-06-30T12:00:00.000Z". Time values similarly: 12:30:00 → "12:30:00.000". Dates stay as-is: "2026-06-30".

1. Array of tables `[[]]` maps correctly — [[fruits]] blocks become a JSON array of objects under fruits key.

1. Dotted keys expand — server.host = "0.0.0.0" creates {server: {host: "0.0.0.0"}}.

1. `to_toml` produces clean idiomatic TOML — proper [section] headers for nested objects, dotted section names for deeply nested objects ([servers.alpha]).

1. Invalid TOML returns descriptive error string with line/column pointer (not an exception): "toml failed: Invalid TOML document: incomplete key-value declaration...".

1. Perfect round-trips — to_toml → to_json returns identical structure.

1. Unicode-safe — German (ü), Turkish (İ), emoji all work.

1. Very fast — p50=6ms, even first call only ~29ms (minimal JIT overhead vs yaml-mcp's 300ms).

Great for: parsing Cargo.toml, pyproject.toml, .cargo/config.toml, Hugo config, Zola config, Deno config, or any TOML configuration file.