blueprint-extractor-mcp
v1.12.0
Published
MCP server for the Unreal Engine BlueprintExtractor plugin over Remote Control
Maintainers
Readme
blueprint-extractor-mcp
MCP server for the Unreal Engine BlueprintExtractor plugin.
This package exposes the blueprint-extractor server over stdio and talks to a running Unreal Editor through the Remote Control HTTP API.
Current surface area includes:
- read-only extraction tools for Blueprints, AI assets, data assets, curves, materials, and animation metadata
- explicit-save authoring tools for the supported editor-side asset families, including compact widget extraction, incremental widget-structure ops, and classic material graph authoring for materials and MaterialFunction-family assets
- async import and reimport tools with polling for generic assets plus typed texture and mesh helpers
- static guidance resources and resource templates for authoring conventions, selector rules, example payloads, widget patterns, and classic material graph guidance
Requirements
- Node.js 18+
- Unreal Editor with the
Remote Control APIplugin enabled - The
BlueprintExtractorUE plugin loaded in the editor
Run
npx blueprint-extractor-mcpThe server reads UE_REMOTE_CONTROL_PORT and defaults to 30010.
You can also set UE_BLUEPRINT_EXTRACTOR_SUBSYSTEM_PATH to force a specific subsystem object path instead of using the built-in probe list.
Install In MCP Clients
Claude Code:
claude mcp add -s user -t stdio blueprint-extractor -e UE_REMOTE_CONTROL_PORT=30010 -- npx -y blueprint-extractor-mcp@latestCodex:
codex mcp add --env UE_REMOTE_CONTROL_PORT=30010 blueprint-extractor -- npx -y blueprint-extractor-mcp@latestLocal Development
npm install
npm run build
npm test
npm run test:pack-smoke
npm publish --dry-runFor the gated live smoke test:
BLUEPRINT_EXTRACTOR_LIVE_E2E=1 npm run test:liveThe live suite imports a texture over a local HTTP fixture server, verifies request-header forwarding, imports a local mesh fixture, polls both jobs to completion, and also smoke-tests scratch material, material function, and material instance authoring before saving the returned asset paths.
The default unit/stdio suites also cover resource-template registration plus the compact widget and material graph surfaces (extract_widget_blueprint, modify_widget_blueprint, extract_material, and modify_material).
Repository and full documentation:
