New users hit predictable friction (no npm install, Remote Control / Python plugin not enabled, C++ not built). This makes onboarding self-service: - src/doctor.js — shared diagnostics (project & engine detection, Node deps, Remote Control reachability, Python plugin, C++ module built, optional Voxel). Zero-dependency top-level imports so it runs before `npm install`. Runnable as `npm run doctor`, reused by the wizard and the server first-run hook. - src/setup.js — interactive `npm run setup` wizard: offers to install deps, confirms/pins project & engine (and RC URL) overrides, re-checks the editor until reachable, then prints the MCP-client config snippet. - projectPaths.js — persisted config (mcp.config.json, git-ignored) with precedence env > config > auto-detect; remoteControlUrl(); first-run marker helpers (isFirstRun/markRun under Saved/). - server.js — `doctor` MCP tool (so a client/assistant can run the checks in a session) + a one-time first-run diagnostic printed to stderr pointing at `npm run setup`. - ueBridge.js honors the config-driven Remote Control URL. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
21 lines
540 B
JSON
21 lines
540 B
JSON
{
|
|
"name": "ue-blueprint-mcp",
|
|
"version": "0.1.0",
|
|
"description": "MCP server for spawning Unreal Engine 5 Blueprint nodes via a universal NodeSpec primitive.",
|
|
"type": "module",
|
|
"main": "src/server.js",
|
|
"bin": {
|
|
"ue-blueprint-mcp": "src/server.js"
|
|
},
|
|
"scripts": {
|
|
"start": "node src/server.js",
|
|
"setup": "node src/setup.js",
|
|
"doctor": "node src/doctor.js",
|
|
"test": "node --test \"test/*.test.js\""
|
|
},
|
|
"dependencies": {
|
|
"@modelcontextprotocol/sdk": "^1.0.4",
|
|
"better-sqlite3": "^11.5.0"
|
|
}
|
|
}
|