YAMLTools

從您的AI編輯器中驗證、轉換與視覺化YAML,並編輯已儲存的圖表。

文件

Use YAMLTools from your AI editor

Validate, review, convert and visualize YAML and configuration files without leaving your AI assistant. Connect your account and let the AI create and edit your diagrams just by asking.

Public tools — no account needed

claude mcp add --transport http yamltools https://yamltools.dev/api/mcp/mcp

With your API key — create and edit your diagrams

claude mcp add --transport http yamltools https://yamltools.dev/api/mcp/mcp \
  --header "Authorization: Bearer yt_your_key"
  1. 01

    Add the server

    Run the command below. The public tools work with no account.
  2. 02

    Connect your account

    Optional — add your API key to also create and edit your saved diagrams.
  3. 03

    Just ask

    Tell your AI to validate, convert, visualize or edit a diagram — it picks the right tool.

Config intelligence — no account needed

  • analyze_config Detects the technology (Compose, Kubernetes, Helm, GitHub Actions, GitLab CI, OpenAPI, Ansible), validates it against the official schema and reports risks with how to fix them.
  • config_diagram Draws the file's architecture as Mermaid: services and ports, Ingress → Service → Deployment, CI jobs and their needs, API endpoints.
  • convert_config Converts between technologies — docker run → Compose, Compose → Kubernetes, Swagger 2.0 → OpenAPI 3 — warning about anything that does not translate.
  • list_supported_technologies Lists the supported technologies and what each one can do.

Public — no account needed

  • validate_yaml Validate and lint YAML: syntax errors with line and column, plus warnings for tabs, implicit booleans and duplicate keys.
  • convert_yaml Convert between YAML, JSON, XML, TOML, CSV, INI, Properties and more — source format auto-detected.
  • visualize_yaml Turn YAML into a diagram: Mermaid source — plus a hosted image on yamltools.dev when you add an API key.

With your account (API key)

  • list_diagrams List your saved diagrams with their titles and types.
  • get_diagram Fetch one of your diagrams, returning its YAML source.
  • create_diagram Save a new diagram to your account from YAML.
  • update_diagram Edit an existing diagram's source, title or type and save it.

Config review

Ask your agent to review your docker-compose

Your agent sends the file to analyze_config and gets back what a reviewer would tell you: what is invalid, what is risky and how to fix it, with line numbers.

Messages arrive in plain English with their line, so the agent can fix the file and run the analysis again. Kubernetes manifests, workflows, pipelines, OpenAPI specs and playbooks work the same way.

You ask

“Check the risks in my docker-compose.yml before I deploy it.”

services:
  web:
    image: nginx:latest
    privileged: true
    ports:
      - "80:80"
    depends_on: [db]
  db:
    image: postgres:16
    environment:
      POSTGRES_PASSWORD: hunter2

Your agent gets (trimmed) · analyze_config

{
  "tech": "docker-compose",
  "summary": {
    "errors": 0,
    "warnings": 0,
    "risks": {
      "high": 2,
      "medium": 1,
      "low": 6
    },
    "text": "Docker Compose: 0 errors, 0 warnings, 9 risks (2 high, 1 medium, 6 low)."
  },
  "risks": [
    {
      "line": 4,
      "severity": "high",
      "code": "privileged",
      "message": "web runs in privileged mode: it has almost the same access to the host as root.",
      "remediation": "Remove privileged: true and add only the capabilities it really needs with cap_add."
    },
    {
      "line": 11,
      "severity": "high",
      "code": "secret-in-env",
      "message": "db has the secret POSTGRES_PASSWORD written in plain text (hu••••).",
      "remediation": "Move POSTGRES_PASSWORD to a .env file that is not committed and reference it as a variable, or use Compose secrets (secrets:) with a _FILE variable."
    },
    {
      "line": 3,
      "severity": "medium",
      "code": "image-latest",
      "message": "web uses nginx:latest: every pull can bring a different version.",
      "remediation": "Replace latest with a specific version (1.2.3) or a digest (@sha256:…) so that deployments are reproducible."
    },
    "… 6 more (no healthcheck, no resource limits, no restart policy)"
  ]
}

Live

Edit a diagram by talking to your AI

Open a diagram in the editor and ask your assistant for changes. It updates your diagram through the MCP and the editor refreshes on its own — no copy-paste, no reloading by hand.

  1. 1Open one of your diagrams in the YAMLTools editor.
  2. 2Ask your AI for a change — "add a redis cache and a worker".
  3. 3Watch the diagram update in place, saved to your account.