engine-mcp-bridge

name	engine-mcp-bridge
description	How to use Remedy's optional MCP client bridge for game editors: the owner lists servers in config.toml mcp_servers (name=command), their tools show up as mcp_<name>_<tool>, and a decision table says when to use them versus native headless tools. Covers checking the server exists, trusting its output, and falling back when it is down. Use when the owner mentions MCP, a Godot/Unity/Unreal MCP server, an editor bridge, or live editor state.
version	1.0.0
author	Remedy
tags	["game","mcp","godot","editor","bridge","tools"]
requires	[]
tools	["mcp_status","local_discover","bash_exec","file_read","file_write","skill_activate","game_project_info","godot_check","godot_run","godot_export","game_playtest"]
triggers	["\\b(mcp|godot[- ]mcp|unity[- ]mcp|unreal[- ]mcp|editor bridge|live editor|mcp_servers)\\b"]

Engine MCP bridge (live editor via MCP)

Remedy can act as an MCP client: the owner lists stdio MCP servers in config.toml, Remedy spawns them, and each advertised tool becomes a native-looking tool named mcp_<server>_<tool>. For game work this is how you reach a running editor — the open scene tree, selected nodes, the Play button, the editor's error panel — which headless tools cannot see.

It is optional. Nothing here replaces the headless verify (godot_check, cargo check, batchmode tests, npm run build).

Configuration (owner-side; describe, do not wizard)

config.toml (under Remedy's home; default_home() on this machine):

mcp_servers = [
  "godot=npx -y <godot-mcp-package>",   # name=command form
  # or a bare command (name derived from it),
  # or a table: { name = "godot", command = "npx", args = ["-y", "<pkg>"], env = {}, cwd = "" }
]

• name becomes the tool prefix: mcp_godot_<tool>. Names are lowercased and non-alphanumerics collapsed to _.
• Servers are spawned lazily on first use; a 300 s timeout applies to every mcp_* call.
• Package choice is the owner's. Godot has several community MCP servers; ask which one they installed rather than guessing a package name. Notes on the usual shape and what tools they expose: references/godot-mcp-setup.md.

Confirm the server exists (before relying on it)

1. mcp_status — lists configured servers, connected/failed, tool names, last error. This is the authoritative check.
2. If it says "No MCP servers configured": tell the owner the config line above and carry on natively.
3. If it failed to connect: local_discover for the runtime (node, npx, python), then bash_exec the command with --help (or npx -y <pkg> --help) to see whether the package even resolves. Quote the error.
4. Most editor servers need the editor open with a plugin/addon enabled; a connected server with zero tools or errors like "editor not reachable" means the owner has to open the project in the editor first.