
Config
io.github.rog0xPublished by GitHub account rog0xv1.0.2Updated Oct 24, 2026
JSON, YAML, TOML, INI config tools for AI agents
Overview
A local MCP server that lets an assistant parse, validate, merge, convert and diff JSON, YAML, TOML and INI configuration files.
- What you can do
- Parse, validate, deep merge and diff JSON/JSONC configuration content, including comments and trailing commas in JSONC input. Parse and validate YAML, convert between YAML and JSON, and check YAML against docker-compose, GitHub Actions or Kubernetes schemas. Parse TOML files such as Cargo.toml and pyproject.toml, extract sections by dot-path, list dependencies and compare semantic versions. Parse INI and properties files, list sections, read single values and convert to or from JSON. Compare two configuration files in any supported format, including cross-format comparisons, showing additions, removals and changes with nested paths.
- When to use it
- Useful when an assistant needs to inspect, clean up or reconcile configuration files across formats, for example checking a YAML file against a schema, merging an overlay config, or reviewing what changed between two config versions.
- Requirements
- Runs as a local process over stdio, installed from the npm package and built before use; the README's example configuration points at a local built entry file. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open Config in the dashboard and add it to a workspace.
- 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
mcp-config-tools
MCP server providing configuration file tools for AI agents. Parse, validate, merge, convert, and diff configuration files across all common formats.
Tools
json_config
Read, validate, deep merge, and diff JSON/JSONC configuration files.
- parse — Parse JSONC (JSON with comments and trailing commas)
- validate — Check if content is valid JSON/JSONC
- merge — Deep merge two JSON configs (overlay wins on conflicts)
- diff — Find structural differences between two JSON configs
yaml_config
Read, validate, and convert YAML configuration files.
- parse — Parse YAML content to structured data
- validate — Check if content is valid YAML
- to_json — Convert YAML to JSON
- from_json — Convert JSON to YAML
- validate_schema — Validate against docker-compose, GitHub Actions, or Kubernetes schemas
toml_parser
Parse TOML configuration files (Cargo.toml, pyproject.toml, etc.).
- parse — Parse TOML content to structured data
- extract_section — Extract a specific section by dot-path
- list_deps — List dependencies from Cargo.toml or pyproject.toml
- compare_versions — Compare two semantic version strings
ini_parser
Parse INI and properties configuration files.
- parse — Parse INI content into sections and key-value pairs
- get_sections — List all section names
- get_value — Get a specific key from a section
- to_json — Convert INI to JSON
- from_json — Convert JSON back to INI format
config_diff
Compare two configuration files in any supported format.
- Auto-detects file format (JSON, YAML, TOML, INI)
- Cross-format comparison (e.g., compare a YAML file against a JSON file)
- Shows additions, removals, and changes with full nested paths
Setup
MCP Configuration
Dependencies
@modelcontextprotocol/sdk— MCP protocol SDKyaml— YAML parser and serializer- Built-in TOML and INI parsers (zero extra dependencies)
Source: README.md at commit 98390a5
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
40% 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
Declare a license in the repository or the registry entry.