feat(asset): expose asset_delete / asset_move / asset_rename as MCP tools#244
feat(asset): expose asset_delete / asset_move / asset_rename as MCP tools#244zajalist wants to merge 1 commit into
Conversation
…ools The asset domain (delete/move/rename and more) is already implemented in the UE C++ HaybaMCPAssetHandler but was unreachable to the agent — hayba only exposes a UE command once it has a TS wrapper registered in index.ts (the ue_legacy route rejects anything not allow-listed). Adds the wrapper layer (mirroring the material_* tools) for the three mutating asset ops, with a source-check test. No C++ / plugin changes.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
More reviews will be available in 41 minutes and 46 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
The asset domain (delete/move/rename and more) is already implemented in the UE C++
HaybaMCPAssetHandlerbut was unreachable to the agent — hayba only exposes a UE command once it has a TS wrapper registered inindex.ts(theue_legacyroute rejects anything not allow-listed insidecar.json). This adds the missing wrapper layer for the three mutating asset ops, mirroring thematerial_*tools landed in #243.Tools added
asset_delete{path}→{deleted:true}asset_move{path, target_dir}→{ok, old_path, new_path}(keeps the asset name; references/redirectors handled by the C++ viaFAssetRenameData)asset_rename{path, new_name}→{old_path, new_path}Changes
src/tools/asset/asset-{delete,move,rename}.ts(copy thematerial-get-info.tsshape; param names verified against the C++TryGetStringFieldcalls).src/tools/index.ts:server.tool(...)+remember(...)+ eagerreg(...)for each.src/tools/asset/asset-tools.test.ts(12 assertions, green).Verification
vitest run src/tools/asset/asset-tools.test.ts→ 12/12 pass.tsc --noEmitclean (after building the@hayba/*workspace deps).No C++, plugin, or editor changes — the commands already ship in the plugin; this only makes them agent-callable after an MCP server reconnect.
🤖 Generated with Claude Code