mcpField
C
config

config

Local
github.com/rog0xDeveloper Tools0Updated 32w ago
Repository

About config

config is an MCP server for AI agents that work with JSON, YAML, TOML, and INI configuration. It combines parsing and validation with format conversion, merging, and cross-format comparison.

Key features

  1. 01Parse and validate JSON/JSONC, YAML, TOML, and INI
  2. 02Deep-merge and diff JSON configurations
  3. 03Convert between YAML and JSON
  4. 04Check YAML against supported schemas
  5. 05Compare files across formats with nested paths

Use cases

  1. 01Inspect or validate a configuration file
  2. 02Merge JSON settings and review conflicts
  3. 03Compare equivalent configurations in different formats

MCP support

Exposes configuration parsing, validation, conversion, merge, and diff tools to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "rog0x-config": {
      "command": "npx",
      "args": [
        "-y",
        "@rog0x/mcp-config-tools"
      ]
    }
  }
}
Run commandnpx -y @rog0x/mcp-config-tools

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@rog0x/mcp-config-tools1.0.2

Tools

5

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
actionenumYesAction to perform: parse (parse JSONC), validate (check validity), merge (deep merge two configs), diff (find differences)parse | validate | merge | diff
contentstringYesPrimary JSON/JSONC content
content2stringNoSecond JSON/JSONC content (for merge/diff actions)

Details

From the project 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

npm install
npm run build

MCP Configuration

{
  "mcpServers": {
    "config-tools": {
      "command": "node",
      "args": ["D:/products/mcp-servers/mcp-config-tools/dist/index.js"]
    }
  }
}

Dependencies

  • @modelcontextprotocol/sdk — MCP protocol SDK
  • yaml — YAML parser and serializer
  • Built-in TOML and INI parsers (zero extra dependencies)

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.