Repository navigation
Document Rustic MCP local access and project selection - #29
Merged
Merged
Conversation
JamieW105
added
area:website
JamieW105
added a commit
to Rustic-Game-Engine/engine
that referenced
this pull request
Oct 12, 2026
The globally registered Rustic MCP command has no `--project` argument. When a desktop client starts it outside a game directory, the backend exits with code 2 before responding to `initialize`, so the client cannot discover its tools. Allow initialization, tool discovery, and ping without a selected game. `workspace_info` now accepts an absolute `project_root` to bind a game for the connection; subsequent project tools use that selection. Invalid replacement paths return tool errors and retain the prior game. Automatic discovery from a game directory or subdirectory still works. Project selection remains required for content tools. Local stdio registration does not expose a user's Rustic installation to a cloud Codex chat. The companion [documentation PR](Rustic-Game-Engine/docs#29) explains that distinction and setup/troubleshooting for the updated backend. Validation: reproduced the old exit from the engine checkout; the updated binary responds to initialization from the same directory. All 7 backend unit/stdio regression tests pass; targeted Clippy with warnings denied and workspace formatting pass. An official MCP SDK client also successfully initializes, lists tools, receives an actionable missing-project error, and pings from outside a game. Website lint, build, TypeScript, and dependency audit pass. Windows installer packaging passed on Windows via [this workflow](https://github.com/Rustic-Game-Engine/engine/actions/runs/38191143560), producing a fresh `RusticGameEngine-Setup-0.1.0-x64-20261012-012313.exe`. The artifact is available as `RusticGameEngine-Windows-Installer` on that run. Full Linux/Windows PR checks are tracked separately by CI.
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.
Rustic's stdio MCP runs on the agent client's computer; a locally registered server is unavailable to a cloud Codex chat. Explain that boundary and how a local MCP session selects its game with
workspace_info({"project_root": ...})when launched outside a game directory. Document actionable tool errors and the workaround for older backends that exit before the handshake.Validation: documentation lint with zero warnings, production build,
tsc --noEmit, andnpm audit --audit-level=moderateall passed.Companion backend change: Rustic-Game-Engine/engine#29.