Yaml Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Parse, stringify, and validate YAML locally. No network and no key.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant parse, stringify and validate YAML files on the user's own machine, with no network access or API key.

What you can do
  • Parse YAML text into structured data the assistant can inspect or transform
  • Convert data back into YAML output
  • Validate YAML for correctness before it is used
  • All processing happens locally, with no network calls
When to use it
Useful when you work with YAML configuration, manifests or data files and want the assistant to read, rewrite or check them without sending content to an external service.
Requirements
Runs as a local stdio process installed from the npm package yaml-mcp, so a Node.js runtime is needed. Desktop-only; no environment variables, headers or credentials are declared.
Before you install
No credentials, payments or third-party data transfer are indicated. The manifest lists no tools, so confirm the exact operations before relying on it; review any file writes the assistant performs on your YAML files.

Installation

In SourceWeft

  1. Open Yaml Mcp in the dashboard and add it to a workspace.
  2. 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

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.