YAMLTools
Server Details
MCP server for YAML: validate & lint, convert between 10 formats, visualize as diagrams, and create/edit your saved diagrams — from your AI editor.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 16 tools
The set splits into a config-analysis cluster and a saved-diagram CRUD cluster, and the descriptions explicitly route ambiguous pairs (analyze_config over validate_yaml, config_diagram vs visualize_yaml, convert_config vs convert_yaml). The only residual confusion is among the three diagram-producing tools (config_diagram, visualize_yaml, create_diagram), which differ in output target but sound similar at a glance.
Nearly every tool follows a snake_case verb_noun pattern (analyze_config, convert_yaml, list_diagrams, move_diagram, validate_yaml). The one deviation is config_diagram, a noun_noun name that should read as diagram_config or visualize_config to match the rest.
16 tools is at the upper edge of comfortable, but each has a defensible role: seven analysis/conversion utilities and nine account-storage operations. Nothing looks redundant, though bundling the hosted-storage API alongside local config utilities makes the surface feel larger than a single purpose.
Diagram CRUD is fully covered (create, get, list, search, update, move, delete) and the analysis side covers validation, linting, risk review, diagrams, and conversion. The gap is folder management: folders can be created and listed but not renamed, moved, or deleted, leaving an unfinished lifecycle.
Available Tools
16 toolsanalyze_configAnalyze a configuration fileAInspect
Review a configuration file the way a DevOps engineer would. Detects the technology (Docker Compose, Kubernetes manifests, Helm charts, GitHub Actions, GitLab CI, OpenAPI/Swagger and Ansible; otherwise generic YAML/JSON) and returns JSON with: the detected technology and alternatives, diagnostics validated against the official JSON Schema plus technology rules (line, column, severity, code, plain-English message, and a mechanical fix when one exists), security and reliability risks with their remediation (privileged containers, :latest images, plaintext secrets, missing limits or healthchecks, unpinned actions…), and a one-line summary. Use it before committing or reviewing a config, or when the user asks "what is wrong with this file" or "what are the risks". Prefer it over validate_yaml for any of these technologies.
Inputs: content (required), tech, filename.
config_diagramDiagram a configuration fileAInspect
Draw the architecture of a configuration file as Mermaid flowchart source, using the technology-specific model: Compose services, ports, volumes, networks and depends_on; Kubernetes Ingress → Service → workload → ConfigMap/Secret; CI jobs, stages and needs; OpenAPI endpoints and schemas; Ansible plays, hosts, tasks and handlers. Use it when the user wants to see or explain how the pieces connect. For generic YAML use visualize_yaml instead.
Inputs: content (required), tech, detail, filename.
convert_configConvert between configuration technologiesAInspect
Convert a configuration between technologies (not just data formats): docker-run-to-compose, compose-to-docker-run, compose-to-kubernetes, swagger2-to-openapi3. Returns JSON with the output and warnings about anything that could not be translated faithfully — read them back to the user. Call list_supported_technologies to see every conversion. For plain format changes (YAML ↔ JSON, TOML…) use convert_yaml.
Inputs: content (required), conversion (required).
convert_yamlConvert YAMLAInspect
Convert between data formats (YAML, JSON, XML, TOML, TOON, CSV, TSV, INI, Properties, ENV). Source format is auto-detected by default; set from to force it.
Inputs: to (required), input (required), from.
create_diagramCreate a diagramAInspect
Save a new diagram to the user's account. Returns its id and URL. May hit the free-plan limit (paywall). Requires a YAMLTools API key.
Inputs: yaml (required), title, diagramType.
create_folderCreate a folderCInspect
Create a Drive folder to organize diagrams. Requires a YAMLTools API key.
Inputs: name (required), parentFolderId.
delete_diagramDelete a diagramAInspect
Permanently delete one of the user's diagrams by id. Requires a YAMLTools API key.
Inputs: id (required).
get_diagramGet a diagramAInspect
Fetch one of the user's diagrams by id, returning its YAML source and metadata. Requires a YAMLTools API key.
Inputs: id (required).
list_diagramsList my diagramsAInspect
List the authenticated user's saved diagrams (id, title, type, visibility, updatedAt). Requires a YAMLTools API key.
Inputs: no named parameters.
list_foldersList my foldersAInspect
List the user's Drive folders (id, name, parentFolderId). Requires a YAMLTools API key.
Inputs: no named parameters.
list_supported_technologiesList supported configuration technologiesAInspect
List the configuration technologies YAMLTools understands, with what each supports (validation, diagram, risks, conversions) and its documentation link. Call it to decide whether analyze_config, config_diagram or convert_config can help with a file.
Inputs: no named parameters.
move_diagramMove a diagramAInspect
Move one of the user's diagrams into a folder, or to the Drive root (folderId = null). Requires a YAMLTools API key.
Inputs: id (required), folderId (required).
search_diagramsSearch my diagramsAInspect
Search the authenticated user's saved diagrams by title text. Returns matches with their folder. Requires a YAMLTools API key.
Inputs: query (required).
update_diagramUpdate a diagramBInspect
Update an existing diagram of the user (source, title and/or type) and save it. Requires a YAMLTools API key.
Inputs: id (required), yaml, title, diagramType.
validate_yamlValidate YAMLAInspect
Validate and lint a YAML document. Reports syntax errors with line/column, non-fatal lint warnings (tabs, implicit booleans, duplicate keys, dash-no-space) and document stats (documents, keys, max depth, bytes).
Inputs: yaml (required).
visualize_yamlVisualize YAMLAInspect
Turn YAML into a diagram. Returns Mermaid source; with an API key it also returns a public image hosted on yamltools.dev. Supports TREE (hierarchy) and FLOW (flowchart).
Inputs: yaml (required), format, diagramType.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs112 npm37 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.