Conversation
Additive module exposing the active scene to an external MCP server, so a
level can be inspected and built programmatically: list objects, get/set
transforms, spawn and delete, create groups, scenes and worlds, generate
prefabs from FBX folders, instantiate prefabs, assign materials.
Nothing changes on a normal run. The plugin is only loaded when the
VG_MCP_BRIDGE environment variable is set, so g_mcpBridge stays nullptr
and every added call site is a dead branch. The engine does not link
against the module either: it only sees the pure-virtual IMCPBridge.h,
and the DLL is resolved at runtime through the existing Plugin::create
mechanism, exactly like renderer, physics, audio or editor.
Transport is file-based (mcp/commands.jsonl in, mcp/state.json out),
polled once per frame from Engine::RunOneFrame. No socket, no thread and
no network dependency is introduced in the engine. The module depends on
Core only.
Changes to existing files are one line each, plus five guarded blocks:
- vg.solution.sharpmake.cs adds the project to the solution
- vg.engine.sharpmake.cs defines VG_ENABLE_MCPBRIDGE (the kill switch:
remove this line and the bridge is gone)
- vg.data.sharpmake.cs keeps src/mcpbridge headers out of the
Version data project
- .gitignore ignores the mcp/ transport directory
- src/engine/Engine.cpp load, tick and unload, all under
#if VG_ENABLE_MCPBRIDGE
See docs/architecture.md for the design and docs/data-contract.md for the
wire format.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
Don't tell me @Benualdo is going to let this slide by allowing the AI to get in with that PR! 🫢 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Additive module exposing the active scene to an external MCP server, so a level can be inspected and built programmatically: list objects, get/set transforms, spawn and delete, create groups, scenes and worlds, generate prefabs from FBX folders, instantiate prefabs, assign materials.
Nothing changes on a normal run. The plugin is only loaded when the VG_MCP_BRIDGE environment variable is set, so g_mcpBridge stays nullptr and every added call site is a dead branch. The engine does not link against the module either: it only sees the pure-virtual IMCPBridge.h, and the DLL is resolved at runtime through the existing Plugin::create mechanism, exactly like renderer, physics, audio or editor.
Transport is file-based (mcp/commands.jsonl in, mcp/state.json out), polled once per frame from Engine::RunOneFrame. No socket, no thread and no network dependency is introduced in the engine. The module depends on Core only.
Changes to existing files are one line each, plus five guarded blocks:
remove this line and the bridge is gone)
Version data project
#if VG_ENABLE_MCPBRIDGE
See docs/architecture.md for the design and docs/data-contract.md for the wire format.