From vbot-mind-mcp
Create and control autonomous virtual robots (V-Bots) with perception, LLM-driven reasoning, episodic memory, and personality engines. Use when working with Godot, Unity3D, or Resonite V-Bots.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vbot-mind-mcp:vbot-mindThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
V-Bot Mind is the fleet's autonomous virtual robot brain runtime. It receives perception
V-Bot Mind is the fleet's autonomous virtual robot brain runtime. It receives perception data from a game engine (what the bot sees, hears, senses), runs LLM reasoning to decide what to do, maintains episodic memory of past interactions, and outputs motor commands back to the engine.
You use this server when you have V-Bots in Godot, Unity3D, or Resonite that need autonomous behavior — NPCs that think, remember, and act like characters.
Operations:
status — List all V-Bots or get one by idcreate — Create a new V-Bot with personality, role, and backstoryconfigure — Update a V-Bot's personality, goals, or roleperceive — Feed observations (what the bot sees/hears/senses)think — Run LLM reasoning on the current situationact — Execute a motor command (move, speak, interact, idle)chat — Direct conversation with a V-Botremember — Store or retrieve episodic memoriesdelete — Remove a V-Bot instanceRuns a multi-step perceive → think → act loop toward a goal. The V-Bot autonomously
pursues the goal for up to max_steps cycles.
V-Bot personalities are defined by trait keywords and a backstory:
The LLM uses the personality + backstory + episodic memory to generate consistent, in-character responses. A "shy, cautious" bot will behave differently from a "bold, aggressive" one in the same situation.
World Labs (generate world) → Godot (assemble scene) → V-Bot Mind (populate with NPCs)
│
MuJoCo (train locomotion) → V-Bot Mind (behavior) → Godot (render + physics)
│
Teleoperator-MCP (HMD interaction)
status) before creating duplicatesGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.
npx claudepluginhub sandraschi/vbot-mind-mcp