Pluggable MCP Server (in your game) - to allow AI Editor to test running game #20042
JeffGillin
started this conversation in
Ideas
Replies: 1 comment
-
well - this works from outside your game: https://crates.io/search?q=bevy_brp_mcp |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I think we all see the LLMs doing it all soon, crazy as it is.
So - we need a pluggable way to add MCP functionality for the LLM to be able to get in game data, and stuff.
Maybe a plugin?
App::build()
.add_plugins(DefaultPlugins)
.add_plugin(BevyMcpPlugin::default()) // Plug & play MCP server
.run();
1 List Entities - Return a structured list of all current ECS entities.
2 Query Components - Get component data for specified entities (e.g., position, health).
3 Modify Component Values - Update or mutate component fields on entities at runtime.
4 Spawn/Despawn Entities - Dynamically create or remove entities during runtime.
5 Control Game State - Start, pause, resume, or stop the game loop or systems.
6 Run Tests / Diagnostics - Trigger automated tests or diagnostic systems and report results.
7 Capture & Return Game Stats - Provide runtime metrics like FPS, memory usage, or entity counts.
8 Trigger Events or Commands - Inject custom events into the ECS event queue or command buffer.
9 Access Resource Data - Query and update global resources used by systems.
10 Log & Debug Output Access - Stream or retrieve runtime logs, warnings, and error messages.
11 Modify System Execution Order - Change the execution order or enable/disable systems dynamically.
12 Query Asset Information - Retrieve info about loaded assets (textures, models, sounds).
13 Hot Reload Scripts or Shaders - Reload Rust scripts, shaders, or config files at runtime.
14 Take and Return Screenshots - Capture current framebuffer or render output as image data.
15 Manage Input States - Query or simulate user input events (keyboard, mouse, gamepad).
16 Adjust Rendering Settings - Change graphics settings like resolution, quality, or effects.
17 Modify Physics Parameters - Change physics world settings or apply forces to entities.
18 Access Network State - Query network connection status or simulate network events.
19 Control Audio Playback - Play, pause, or adjust sounds/music during runtime.
20 Export Runtime Data - Save ECS or game state snapshots for debugging or replay.
Yes, I used ChatGPT to help me come up with this list - I'm admittedly not the smart one in this corners (see).
Just need to open up this real nice game engine for the big brained computers to take over.
Beta Was this translation helpful? Give feedback.
All reactions