Noyalib Mcp

io.github.sebastienrousseau由 GitHub 账号 sebastienrousseau 发布v0.0.59更新于 Nov 11, 2026

MCP server for lossless YAML 1.2 parsing, formatting, and validation (pure Rust).

已验证STDIO仅桌面文件与存储开发者工具

概览

AI 生成的概览

本地 MCP 服务器,让助手无损地解析、读取、编辑和校验 YAML 1.2 文档,支持严格与标准两种配置档。

可以做什么
  • 解析 YAML 文档并返回带类型的结构化结果
  • 读取和设置 YAML 文件中的值,包括多文档设置与无损编辑
  • 按调用方提供的 schema,在严格或标准配置档下校验 YAML
  • 通过 stdio、streamable HTTP 或 HTTP+SSE 提供提示词与资源供智能体集成
适用场景
适合助手需要查看或修改 YAML 配置、清单文件或多文档文件且不希望丢失注释与格式时使用,也适合在提交改动前检查 YAML 是否有效。
运行要求
默认以 stdio 本地进程方式运行,也可在 /mcp 提供 streamable HTTP 或在 /sse 提供 HTTP+SSE。可通过 cargo install 或已发布的容器镜像安装;从源码构建需要 Rust 1.89.0 或更高版本。需要 MCP 客户端。npm 包装器目前因未发布各平台归档而拒绝运行。
安装前请注意
文件工具会写入 YAML 文件,应将 --root 指向客户端可访问的目录;解析到该目录之外的路径(包括通过符号链接)会被拒绝。HTTP 传输不做身份验证,不应暴露到不受信任的网络。服务器不获取远程 schema,schema 内容须自行确保可信。请将文件内容、YAML 与 schema 视为不受信任的输入。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Noyalib Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[noyalib-mcp logo]

noyalib-mcp

Model Context Protocol server for lossless YAML inspection, editing, and validation.

[Build] [Registry] [Docs] [OpenSSF Scorecard] [License: Apache-2.0 OR MIT] [MSRV 1.89.0] [Glama MCP server score]

[noyalib-mcp Demo]


Contents

Getting started

The noyalib-mcp ecosystem

Library reference

Operational


Install

As a Rust library

toml
[dependencies]noyalib-mcp = "0.0.60"

Install or run the server through the channel that fits the host:

bash
cargo install noyalib-mcp --lockeddocker run --rm -i ghcr.io/sebastienrousseau/noyalib-mcp:latest

The npm wrapper (npx @sebastienrousseau/noyalib-mcp) runs a binary only when its package carries a SHA-256 for your platform. Releases do not yet publish per-platform archives, so today it refuses to run and points to the two commands above.

Requirements

  • Rust 1.89.0 or newer when building from source.
  • Linux, macOS, and Windows are tested by CI.
  • The crate pins noyalib at exactly =0.0.60 under the lockstep contract.
  • An MCP client is required to drive the server.
SurfaceMinimum toolchainEnforcement
Server and libraryRust 1.89.0manifest and MSRV CI
Complete test surfaceRust 1.89.0all-target CI

Quick Start

Use stdio for a child-process integration:

bash
noyalib-mcp

A stdio client begins with an MCP initialization request before sending the initialized notification or listing tools:

json
{  "jsonrpc": "2.0",  "id": 1,  "method": "initialize",  "params": {    "protocolVersion": "2025-11-25",    "capabilities": {},    "clientInfo": {      "name": "example",      "version": "0.0.1"    }  }}

Serve streamable HTTP at /mcp, or the legacy HTTP+SSE bridge at /sse and /messages/:

bash
noyalib-mcp --transport streamable-http --host 127.0.0.1 --port 8000noyalib-mcp --transport sse --host 127.0.0.1 --port 8001

The server negotiates supported MCP revisions during initialize; clients should not send raw tool calls before completing that handshake.

The noyalib-mcp ecosystem

ComponentRole
noyalib-mcpMCP server, transports, tools, prompts, and resources
noyalibYAML parser, CST editor, and schema validator
noya-cliHuman-facing formatting and validation commands
rmcpOfficial Rust MCP SDK used for protocol handling

Capabilities at a glance

AreaCapabilityStatus
Transportstdio, streamable HTTP, and HTTP+SSESupported
ProtocolRevisions from 2024-11-05 through 2026-07-28Negotiated
ResultsText plus typed structuredContentSupported
YAMLParse, get, set, multidocument set, edit, and validateSupported
MetadataTool schemas, annotations, examples, prompts, and resourcesPublished

Ecosystem comparison

Delivery surfaceLossless YAML editsRemote transportTyped tool results
noyalib-mcpYesHTTP and SSEYes
noya-cliYesNoNot applicable
noyalibYesNoNative Rust types

See docs/COMPARISON.md for scope and evidence.

Benchmarks

The checked-in mcp_tools Criterion harness measures tool dispatch and YAML operations without treating noisy timing values as correctness gates.

bash
cargo bench --bench mcp_tools

See docs/BENCHMARKS.md for methodology.

Features

  • Six typed tools for YAML reads, edits, parsing, and validation.
  • Declared outputSchema, structuredContent, annotations, and examples.
  • stdio, streamable HTTP, and legacy HTTP+SSE transports.
  • Prompts and resources for agent integration.
  • Protocol revision negotiation and session-aware routing.

Configuration

OptionEffect
--transport stdioUse process stdin and stdout; this is the default
--transport streamable-httpServe MCP at /mcp
--transport sseServe /sse and /messages/
--host ADDRESSBind an HTTP transport to an address
--port PORTSelect the HTTP listening port
--root DIRConfine the file tools to DIR (default: the working directory, which may not be / or the home directory)
--profile strict|standardRules every tool parses under, the file tools and noyalib_edit included: noyalib's strict YAML 1.2 profile (the default: duplicate keys and odd indentation are errors, tighter limits) or the library defaults
--max-sessions NSessions an HTTP transport holds at once (default 64)

Bind remote transports deliberately. The default loopback host avoids exposing the server beyond the local machine. The file tools (noyalib_get, noyalib_set, noyalib_set_multidoc) refuse any path that resolves outside the root, symlinks included; start the server with --root on the directory a client may touch. The HTTP transports refuse a foreign Host or Origin and do not authenticate. SECURITY.md has the full trust model.

Examples

Client configuration recipes are in docs/agent-integration.md.

When not to use noyalib-mcp

  • Use noyalib directly inside a Rust application that does not need MCP.
  • Use noya-cli for shell pipelines and repository-wide validation.
  • Do not expose an HTTP transport to an untrusted network without an authentication and authorization layer in front of it.
  • The server does not fetch remote schemas; callers must supply trusted schema content.

The detailed README reference retains client setup, tool detail, verification steps, and conformance discussion.

Development

bash
makemake testmake clippymake fmtcargo fuzz run fuzz_tool_call

CI checks Rust formatting, linting, tests, documentation, dependency policy, fuzz regressions, protocol behaviour, and the shared YAML test suite. See DEVELOPMENT.md.

Security

Report vulnerabilities through SECURITY.md. The crate forbids unsafe code, audits dependencies, uses bounded noyalib operations, and emits release attestations and SBOMs. Treat file content, YAML, schemas, and MCP metadata as untrusted input.

Documentation

Stability guarantees

  • During 0.0.x, the patch component is the breaking-change axis.
  • Tool names, argument schemas, output schemas, and transport routes form the public compatibility surface.
  • Protocol revisions are negotiated rather than inferred.
  • The MSRV may rise only on the breaking axis with a changelog explanation.

License

Dual-licensed under either the Apache License, Version 2.0 or the MIT License, at your option.

来源:README.md,提交 aa3c9db

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

13
  1. v0.0.59最新Nov 11, 2026
  2. v0.0.58Oct 16, 2026
  3. v0.0.57Oct 9, 2026
  4. v0.0.56Oct 8, 2026
  5. v0.0.54Oct 7, 2026
  6. v0.0.53Oct 6, 2026
  7. v0.0.52Oct 4, 2026
  8. v0.0.51Sep 22, 2026
  9. v0.0.50Sep 22, 2026
  10. v0.0.47Sep 22, 2026
  11. v0.0.45Sep 19, 2026
  12. v0.0.44Sep 17, 2026
  13. v0.0.43Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分