Contents
Getting started
- Install — Cargo, npm wrapper, and container
- Requirements — toolchain floor, platforms
- Quick Start — start a server over stdio or HTTP
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @sebastienrousseau/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add sebastienrousseau-noyalib-mcp-npm -- npx -y @sebastienrousseau/noyalib-mcp@0.0.58รันในเทอร์มินัล
{ "mcpServers": { "sebastienrousseau-noyalib-mcp-npm": { "command": "npx", "args": [ "-y", "@sebastienrousseau/[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Getting started
Model Context Protocol server for noyalib YAML tools — parse, format, get, set, validate over JSON-RPC stdio.
The noyalib-mcp ecosystem
Library reference
docs/COMPARISON.mddocs/BENCHMARKS.mdOperational
[dependencies]
noyalib-mcp = "0.0.58"
Install or run the server through the channel that fits the host:
cargo install noyalib-mcp --locked
docker 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.
noyalib at exactly =0.0.58 under the lockstep contract.Use stdio for a child-process integration:
noyalib-mcp
A stdio client begins with an MCP initialization request before sending the initialized notification or listing tools:
{
"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/:
noyalib-mcp --transport streamable-http --host 127.0.0.1 --port 8000
noyalib-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.
See docs/COMPARISON.md for scope and evidence.
The checked-in mcp_tools Criterion harness measures tool dispatch and YAML
operations without treating noisy timing values as correctness gates.
cargo bench --bench mcp_tools
See docs/BENCHMARKS.md for methodology.
outputSchema, structuredContent, annotations, and examples.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.
mcp_session.rs: SDK-backed in-memory session.handshake.sh: initialize and list tools.set-then-get.sh: lossless mutation and readback.Client configuration recipes are in
docs/agent-integration.md.
noyalib directly inside a Rust application that does not need MCP.noya-cli for shell pipelines and repository-wide validation.The detailed README reference retains client setup, tool detail, verification steps, and conformance discussion.
make
make test
make clippy
make fmt
cargo 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.
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.
0.0.x, the patch component is the breaking-change axis.Dual-licensed under either the Apache License, Version 2.0 or the MIT License, at your option.
Model Context Protocol server for noyalib YAML tools — parse, format, get, set, validate over JSON-RPC stdio.
{ "mcpServers": { "sebastienrousseau-noyalib-mcp-npm": { "command": "npx", "args": [ "-y", "@sebastienrousseau/[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
@sebastienrousseau/noyalib ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 Model Context Protocol server for noyalib YAML tools — parse, format, get, set, validate over JSON-RPC stdio.