SkillAgentSearch skills...

materialpilot

Native, local-first MCP bridge for safe, editable procedural materials in Material Maker 1.7 and Godot 4.7.

Install / Use

claude mcp add SS-360 -- npx -y github:SS-360/materialpilot

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

81/100

Supported Platforms

Claude Code
Claude Desktop
OpenAI Codex

Our assessment of materialpilot

materialpilot scores 81/100 on our quality scale, 3431st of 4,698 Development & Engineering skills we index.

Its MCP Server is 21 KB long, well organised into 26 sections with 25 code examples: a thorough specification that gives an agent plenty to work with.

It has 10 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
4/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 31 days ago, so materialpilot is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 85/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-13. Automated pattern scan on 2026-11-13. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

materialpilot compared with similar skills

All 4 of these similar skills score higher than materialpilot; compare them before choosing.

SkillScoreStarsUpdatedFormat
materialpilot (this skill)by SS-360811031d agoMCP Server
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md

Frequently asked questions

How do I install materialpilot?
Run claude mcp add SS-360 -- npx -y github:SS-360/materialpilot. The install tabs above show the steps for each supported agent.
Which AI agents does materialpilot work with?
It is written for Claude Code, Claude Desktop and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
Is materialpilot safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 85/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is materialpilot still maintained?
The repository was last updated 31 days ago, so materialpilot is actively maintained.

MaterialPilot

A native, local-first MCP bridge for editable procedural materials in Material Maker

CI License: Apache-2.0 Material Maker Godot Node.js

MaterialPilot lets MCP-compatible AI agents inspect, create, organize, validate, preview, save, and export real Material Maker projects. It works through Material Maker's native graph and undo APIs, not UI coordinates, and keeps the procedural graph editable for artists.

The current 0.1.0 implementation preview exposes 143 typed MCP tools, a generated catalog of 392 Material Maker 1.7 node definitions, revision-safe graph transactions, deterministic validation, bounded rendering, named recovery snapshots, native undo/redo, and verified Blender-profile PBR export.

[!IMPORTANT] MaterialPilot is a tested implementation preview, not the complete 1.0 described in the long-range production plan. Unsupported and higher-risk operations are capability-gated instead of being simulated. See Current limitations.

Why MaterialPilot?

Procedural material graphs are valuable because they remain editable, reusable, and parameterized. Conventional text-to-texture workflows often stop at flattened images, while general desktop automation cannot reliably understand graph ports, project revisions, renderer state, or undo history.

MaterialPilot gives agents structured access to the underlying creative system:

  • Editable output: the primary artifact is a native .ptex graph, not only exported images.
  • Native integration: graph operations use Material Maker and Godot APIs rather than mouse coordinates.
  • Observation before mutation: agents inspect the project, revision, catalog, and capabilities before editing.
  • Atomic changes: a graph patch either commits as one undo step or restores its exact pre-state.
  • Deterministic safety: schemas, port compatibility, path policy, revisions, and validation are enforced outside the language model.
  • Visual evidence: live node outputs and sphere/plane previews provide bounded PNG evidence.
  • Verified delivery: Blender exports include dimensions, file sizes, and SHA-256 hashes.
  • Local-first operation: native communication is authenticated and bound to loopback.

How it works

flowchart LR
    Host["MCP host<br/>Codex · IDE · CLI"]
    Server["MaterialPilot MCP server<br/>TypeScript"]
    Bridge["Native bridge<br/>GDScript"]
    Maker["Material Maker 1.7<br/>Godot 4.7"]
    Core["Domain services<br/>schemas · graph engine · validator · security"]

    Host <-->|"MCP over STDIO or authenticated HTTP"| Server
    Server <-->|"Authenticated loopback WebSocket JSON-RPC"| Bridge
    Bridge <-->|"Native graph, renderer, save, export, undo"| Maker
    Server --- Core

Material Maker writes an authenticated discovery record while the native bridge is running. The MCP server reads that record, negotiates available capabilities, and connects locally. If no live bridge is available, the server can fall back to an offline reference engine for catalog, planning, schema, and transaction work; live-only capabilities remain false.

Every native graph mutation follows the same boundary:

inspect revision -> validate patch -> snapshot -> apply operations
                 -> structural validation -> commit one undo entry
                 -> emit revision, diff, diagnostics, and evidence

failure at any point -> restore serialized snapshot -> return a structured error

For the design rationale, see the architecture overview and architecture decision records.

Capabilities

| Area | Current support | | ----------- | ------------------------------------------------------------------------------------------------------------------- | | Application | Health, status, version, capability, limit, and live/offline-mode discovery | | Projects | List, inspect, create native material tabs, save .ptex, and create named recovery snapshots | | Catalog | Search and inspect 392 generated Material Maker 1.7 node descriptors, ports, parameters, aliases, and compatibility | | Graphs | Read canonical snapshots, plan patches, dry-run, apply atomically, diff, validate, undo, and redo | | Editing | Create, delete, connect, disconnect, move, parameterize, batch-edit, comment, and expose remote controls | | Layout | Semantic stages, comments, positions, selection, graph organization, and output-preserving repair workflows | | PBR | Albedo, roughness, metallic, normal, height/depth, ambient occlusion, emission, and related output inspection | | Preview | Bounded node-output PNGs and renderer-backed sphere/plane material previews | | Export | Policy-constrained Blender-profile PNG/EXR maps with temporary publication and hash verification | | Diagnostics | Deterministic validation, transaction history, performance inspection, structured errors, and correlation evidence | | Workflows | Cracked stone, basalt, sandstone, lava, oxidized metal, and a complete abandoned-industrial-floor workflow |

The authoritative schema and behavior for each tool are documented in the tool reference.

Safety model

MaterialPilot treats user projects, graph comments, downloaded metadata, file paths, and model output as untrusted data.

The default security controls include:

  • loopback-only native and HTTP listeners;
  • an ephemeral authenticated bridge token;
  • workspace read, write, and export roots;
  • canonical path checks and explicit overwrite policy;
  • optimistic concurrency through expectedRevision;
  • idempotency keys for mutations and exports;
  • snapshot-first transactions and rollback;
  • native undo/redo integration;
  • renderer-dependent capability negotiation;
  • custom shader writes and network operations disabled by default; and
  • stderr-only diagnostics for the STDIO MCP server.

Choose the narrowest permission mode that fits the workflow:

| Mode | Behavior | | ---------------------- | ------------------------------------------------------------------------------------- | | observe | Read-only inspection; mutations require an approval token | | assisted | Default; protected writes require single-use approval | | workspace-autonomous | Allows reversible graph editing inside approved workspace roots | | developer | Broader local development access; custom code and network permissions remain separate |

Read SECURITY.md and the threat model before enabling automation in a sensitive workspace.

Requirements

| Component | Supported version | Purpose | | -------------- | -------------------------- | ------------------------------------------------------- | | Node.js | 22.13.0 or newer | MCP server, CLI, packages, and tests | | pnpm | 11.9.0 | Source builds and development | | Material Maker | 1.7 | Live procedural material editing | | Godot | 4.7 stable | Running or exporting Material Maker from source | | MCP host | Current compatible release | Codex Desktop, Codex CLI, an IDE, or another MCP client |

The TypeScript workspace and CI target Windows, Linux, and macOS. The native compatibility suite is pinned to Material Maker 1.7 and Godot 4.7. Renderer-backed preview and export operations require a real Godot rendering device and are deliberately unavailable in headless sessions.

Quick start

1. Build MaterialPilot

git clone https://github.com/SS-360/materialpilot.git
cd materialpilot
corepack enable
corepack prepare pnpm@11.9.0 --activate
pnpm install --frozen-lockfile
pnpm build
pnpm check

Run the diagnostic CLI:

node packages/cli/dist/main.js doctor

2. Install the native addon

Close Material Maker before installing or updating the addon. Copy:

apps/material-maker-bridge/addon/materialpilot

into the Material Maker 1.7 source project as:

addons/materialpilot

For example, in PowerShell:

$materialPilot = 'D:\path\to\materialpilot'
$materialMaker = 'D:\path\to\material-maker-1.7'
$target = Join-Path $materialMaker 'addons\materialpilot'

New-Item -ItemType Directory -Force $target | Out-Null
Copy-Item -Path (Join-Path $materialPilot 'apps\material-maker-bridge\addon\materialpilot\*') `
  -Destination $target -Recurse -Force

Open the Material Maker project in Godot and enable MaterialPilot Native Bridge under Project → Project Settings → Plugins. The plugin installs this autoload:

[autoload]
MaterialPilotBridge="*res://addons/materialpilot/bridge/bridge_server.gd"

Launch Material Maker normally. While it is running, the default discovery record is:

  • Windows: %USERPROFILE%\.materialpilot\bridge.json
  • Linux/macOS: ~/.materialpilot/bridge.json

The record contains an ephemeral token. Do not publish, commit, or share it.

Verify the live bridge:

node packages/cli/dist/main.js bridge status

3. Connect an MCP client

STDIO is the recommended transport for one local client. Configure the client to launch Node with the absolute MCP server path:

node /absolute/path/to/materialpilot/apps/mcp-server/dist/main.js

For Codex CLI on Windows:

codex mcp add materialpilot `
  --env MATERIALPILOT_PERMISSION_MODE=workspace-autonomous `
  -- 'C:\Program Files\nodejs\node.exe' `
  'D:\absolute\path\to\materialpilot\apps\mcp-server\dist\main.js'

Or add a source checkout directly to ~/.codex/config.toml:

[mcp_servers.materialpilot]
enabled = true
command = 'C:\Program Files\nodejs\node.exe'
args = ['D:\absolute\path\to\materialpilot\apps\mcp-server\dist\main.js']
cwd = 'D:\absolute\path\to\materialpilot'
startup_timeout_sec = 10
tool_timeout_sec = 60

[mcp_servers.materialpilot.env]
MATERIALPILOT_PERMISSION_MODE = "workspace-autonomous"

Start Material Maker before the MCP client. If the client started first and entered offline mode, restart it after the bridge record appears.

For packaged releases, Linux/macOS configuration, authenticated HTTP transport, and runtime-path overrides, follow the complete installation and run guide.

Verify a live session

Ask the MCP host to inspect status before modifying anything:

Use MaterialPilot's app_get_status and app_get_capabilities tools. Report whether the native
Material Maker bridge is connected, whether offline mode is active, the Material Maker and Godot
versions, the active project ID, and whether graph.read, graph.write, graph.transactions,
preview.material3d, and export.write are available. Do not change the graph.

A renderer-backed live session should report values equivalent to:

{
  "bridgeConnected": 

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars10
CategoryDevelopment
Updated1mo ago
Forks1

Languages

TypeScript

Trust signals

85/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 info