Toml Yaml Json Mcp

io.github.MukundaKattaPublished by GitHub account MukundaKattav0.1.0Updated Oct 24, 2026

Parse, format, and convert configs across TOML, YAML, and JSON.

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant parse, format and convert configuration files between TOML, YAML and JSON using real parsers.

What you can do
Parse a config string in TOML, YAML or JSON into a structured value, avoiding guesswork on datetimes, arrays of tables and implicit types. Format a structured value back into a config string in the chosen format. Convert a config document from one of TOML, YAML or JSON to another in a round trip.
When to use it
Useful when an assistant needs to read, rewrite or translate configuration files and hand-editing risks errors such as YAML indentation traps or TOML array-of-tables mistakes.
Requirements
Runs as a local process over stdio, installed from the npm package @mukundakatta/toml-yaml-json-mcp, typically launched with npx. Node.js is needed. No authentication, environment variables or headers are declared.
Before you install
It only transforms text passed to it; no credentials, network access or write actions are declared. Review converted output before saving it over real configuration files, since formatting and type coercion can change meaning.

Installation

In SourceWeft

  1. Open Toml Yaml Json Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@mukundakatta/toml-yaml-json-mcp

MCP server for round-tripping config formats. Parse, format, or convert between TOML, YAML, and JSON.

Tools

  • parse(text, format) — config string in, JS value out
  • format(value, format) — JS value in, config string out
  • convert(text, from, to) — TOML ↔ YAML ↔ JSON round trip

Why this exists

LLMs reliably mishandle:

  • TOML datetime literals
  • TOML array-of-tables ([[server]])
  • TOML inline arrays vs nested keys
  • YAML indentation traps
  • YAML implicit type coercion (yes → true, etc.)

Routing through proper parsers (@iarna/toml, js-yaml, the built-in JSON) avoids guessing.

Install — Claude Desktop

json
{  "mcpServers": {    "toml-yaml-json": { "command": "npx", "args": ["-y", "@mukundakatta/toml-yaml-json-mcp"] }  }}

Same shape for Cursor / Cline / Windsurf / Zed.

License

MIT OR Apache-2.0.

Source: packages/toml-yaml-json-mcp/README.md at commit 6fad5bb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts