
Vrm Toolkit Mcp
io.github.dwarehouse1Published by GitHub account dwarehouse1v0.1.1Updated Oct 24, 2026
Inspect, validate and preview VRM / VRMA files from an AI agent (5 tools, local stdio server).
Overview
Lets an assistant inspect, validate and render previews of local VRM avatar and VRMA animation files.
- What you can do
- Provides five local tools for VRM/VRMA assets: vrm_inspect returns structured JSON on metadata, license and permission fields, humanoid bone mapping, expressions, and polygon/texture statistics; vrm_validate returns a finding list with stable codes for missing required bones, broken references, missing meta/license fields, unknown required extensions and configurable size budgets; vrma_inspect reports animation tracks, targeted bones, duration and estimated frame rate. Two rendering tools, vrm_snapshot and vrma_preview, produce a PNG still or a short WebM clip (max 10 s) using a locally installed Chromium-based browser.
- When to use it
- Useful when working with VRM avatars or VRMA motion files on your own machine and you want an assistant to check metadata and licensing, verify rigging and file integrity, or generate quick still or animated previews without opening a 3D editor.
- Requirements
- Node.js 20 or newer, run locally over stdio (npx -y vrm-toolkit-mcp). The rendering tools need a locally installed Chrome or Edge, auto-detected or set via the VRM_TOOLKIT_CHROME environment variable. Input size budget defaults to 512 MiB, overridable with VRM_TOOLKIT_MAX_BYTES. No accounts, keys or network access at runtime.
Installation
In SourceWeft
- Open Vrm Toolkit Mcp in the dashboard and add it to a workspace.
- 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
vrm-toolkit-mcp
An MCP (Model Context Protocol) server that lets an AI agent inspect, validate and preview VRM / VRMA files on your machine. Five tools, stdio transport, no network access at runtime.
VRM / VRMAファイルの検品・情報抽出・プレビューをAIエージェントから使えるようにする MCPサーバーです。ツールは5本、stdioトランスポート、実行時のネットワークアクセスなし。
Tools / ツール
Structural tools (vrm_inspect, vrm_validate, vrma_inspect) parse the GLB/glTF container
directly in Node and need no browser. Rendering tools (vrma_preview, vrm_snapshot) use an
already-installed Chromium-based browser via puppeteer-core; nothing is downloaded.
構造系3ツールはNode単体でGLB/glTFを直接パースし、ブラウザ不要。描画系2ツールは
インストール済みのChromium系ブラウザをpuppeteer-coreで使います(追加ダウンロードなし)。
Supported inputs: VRM 0.x (extensions.VRM), VRM 1.0 (extensions.VRMC_vrm),
VRMA (extensions.VRMC_vrm_animation), GLB container or plain glTF JSON.
Requirements / 動作条件
- Node.js 20+
- For
vrma_preview/vrm_snapshot: a local Chrome or Edge (auto-detected; override with theVRM_TOOLKIT_CHROMEenvironment variable) - Input size budget: 512 MiB by default (
VRM_TOOLKIT_MAX_BYTESto override)
Setup / セットアップ
Register with Claude Code / Claude Codeへの登録:
Other MCP hosts / その他のMCPホスト: command npx, args ["-y", "vrm-toolkit-mcp"] (stdio).
From source / ソースから:
Execution examples / 実行例
Real outputs from the local test run (2026-08-05, file paths shortened). ローカルテスト実行(2026-08-05)の実出力です(パスは短縮表記)。
vrm_inspect
Input: a VRoid Studio-exported VRM 1.0 avatar (15.7 MB).
(Output truncated for readability; the tool returns the full bone and image lists.)
vrma_inspect
vrm_validate
A finding list with stable codes and severities:
vrm_snapshot / vrma_preview
Error codes / エラーコード
Every failure is a structured tool error with one of:
FILE_NOT_FOUND, SIZE_BUDGET_EXCEEDED, NOT_A_GLB, NOT_A_VRM, NOT_A_VRMA,
BROWSER_NOT_FOUND, RENDER_FAILED, OUTPUT_WRITE_FAILED.
The server process never crashes on a bad input file.
Privacy / プライバシー
All processing is local. The server opens no network connection, sends no telemetry, and writes only the output files you name. / 処理はすべてローカルです。ネットワーク接続・テレメトリ送信は なく、書き込みは指定した出力ファイルのみです。
Development / 開発
Rendering tests skip with a notice when no local Chrome/Edge is found.
License / ライセンス
Source: README.md at commit 819630f
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% 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
- License10 pts