blueprint-extractor-mcp 1.13.0 → 2.0.0

package/README.md

@@ -4,13 +4,17 @@ 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.
 
+The current v2 MCP contract exposes 80 tools, 13 resources, 2 resource templates, and 4 prompts.
+Public tools use canonical `snake_case` inputs and return structured JSON success or error envelopes.
+
 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, widget class-default routing, and classic material graph authoring for materials and MaterialFunction-family assets
+- explicit-save authoring tools for the supported editor-side asset families, including compact widget extraction, incremental widget-structure ops, widget class-default routing, composable material authoring (`set_material_settings`, `add_material_expression`, `connect_material_expressions`, `bind_material_property`), and the advanced `modify_material` escape hatch
+- dedicated Enhanced Input authoring tools for `InputAction` and `InputMappingContext` assets (`create_input_action`, `modify_input_action`, `create_input_mapping_context`, `modify_input_mapping_context`)
 - async import and reimport tools with polling for generic assets plus typed texture and mesh helpers
 - host-side project automation tools for external builds, Live Coding requests, restart/reconnect orchestration, and a thin window-polish helper
-- static guidance resources and resource templates for authoring conventions, selector rules, font roles, project automation, example payloads, widget patterns, and classic material graph guidance
+- static guidance resources, resource templates, and prompts for authoring conventions, selector rules, font roles, project automation, example payloads, widget patterns, unsupported surfaces, safe UI redesign, and classic material graph guidance
 
 ## Requirements
 
@@ -28,6 +32,8 @@ The 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.
 
+For workflow-oriented guidance, the server also exposes prompts such as `design_menu_screen`, `author_material_button_style`, `wire_hud_widget_classes`, and `debug_widget_compile_errors`.
+
 For host-side code automation, these optional env vars are supported:
 
 - `UE_ENGINE_ROOT`
@@ -66,9 +72,9 @@ For the gated live smoke test:
 BLUEPRINT_EXTRACTOR_LIVE_E2E=1 npm run test:live
 ```
 
-The 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 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, smoke-tests the composable material workflow plus material function and material instance authoring, and round-trips the dedicated Enhanced Input authoring tools before saving the returned asset paths.
 
-The default unit/stdio suites also cover resource-template registration, the narrowed widget surfaces (`extract_widget_blueprint`, `modify_widget`, `modify_widget_blueprint`), the host-side project-control tools (`compile_project_code`, `trigger_live_coding`, `restart_editor`, `sync_project_code`, `apply_window_ui_changes`), and the compact material graph surfaces (`extract_material`, `modify_material`).
+The default unit/stdio suites also cover prompt registration, resource-template registration, the narrowed widget surfaces (`extract_widget_blueprint`, `modify_widget`, `modify_widget_blueprint`), the host-side project-control tools (`compile_project_code`, `trigger_live_coding`, `restart_editor`, `sync_project_code`, `apply_window_ui_changes`), the compact material graph surfaces (`extract_material`, `modify_material`), and output-schema exposure for the specialized import and cascade tools.
 
 Repository and full documentation:
 

package/dist/index.d.ts

@@ -1,6 +1,26 @@
 #!/usr/bin/env node
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+import { z } from 'zod';
 import { UEClient } from './ue-client.js';
 import { type ProjectControllerLike } from './project-controller.js';
 export type UEClientLike = Pick<UEClient, 'callSubsystem'> & Partial<Pick<UEClient, 'checkConnection'>>;
+type ToolExample = {
+    title: string;
+    tool: string;
+    arguments: Record<string, unknown>;
+};
+type ExampleFamily = {
+    summary: string;
+    recommended_flow: string[];
+    examples: ToolExample[];
+};
+type PromptCatalogEntry = {
+    title: string;
+    description: string;
+    args: Record<string, z.ZodTypeAny>;
+    buildPrompt: (args: Record<string, unknown>) => string;
+};
+export declare const exampleCatalog: Record<string, ExampleFamily>;
+export declare const promptCatalog: Record<string, PromptCatalogEntry>;
 export declare function createBlueprintExtractorServer(client?: UEClientLike, projectController?: ProjectControllerLike): McpServer;
+export {};