Toml Yaml Json Mcp
Parse, pretty-print, and convert project configs between TOML, YAML, and JSON via MCP.
Overview
io.github.MukundaKatta/toml-yaml-json-mcp is an MCP server for the Build phase that parses, formats, and converts configs across TOML, YAML, and JSON.
What is this MCP server?
- Round-trip parse, format, and convert across TOML, YAML, and JSON
- Stdio npm @mukundakatta/toml-yaml-json-mcp v0.1.0
- Reduces copy-paste errors when moving settings between ecosystems
- Lives in MukundaKatta mcp-stack alongside other small dev utilities
- Supports three config families: TOML, YAML, and JSON
- npm package version 0.1.0 with stdio transport
What problem does it solve?
Agents routinely mix up TOML, YAML, and JSON syntax when editing configs, breaking deploys with subtle formatting mistakes.
Who is it for?
Solo builders juggling multi-format repos (e.g. pyproject.toml plus docker-compose YAML plus JSON env files).
Skip if: Codebases standardized on a single config format with no cross-format edits.
What do I get? / Deliverables
After registration, your agent can use MCP tools for reliable cross-format config conversion instead of hallucinated structure.
- Validated parses and formatted config files in target formats
- Cross-format conversions suitable for commit-ready diffs
Recommended MCP Servers
Journey fit
How it compares
Config-format MCP utility, not an IaC planner or secret store.
Common Questions / FAQ
Who is io.github.MukundaKatta/toml-yaml-json-mcp for?
Developers using AI agents to edit deployment and project configs that span TOML, YAML, and JSON.
When should I use io.github.MukundaKatta/toml-yaml-json-mcp?
Use it when migrating settings between tools, normalizing manifests, or generating one format from another during builds.
How do I add io.github.MukundaKatta/toml-yaml-json-mcp to my agent?
Install @mukundakatta/toml-yaml-json-mcp via npm, add the stdio MCP entry in your host, and grant agents access to its parse and convert tools.