No image available

Obssidian Godot MCP — Verified AI Bridge for Godot 4

Let your AI build in Godot while Obssidian verifies the result, runs regressions and rolls back broken changes. Windows, Linux & macOS.” BUILD WITH AI. VERIFY IN GODOT. ROLLBACK WHEN IT BREAKS. Obssidian Godot MCP is a safety-first AI bridge for Godot 4 — now supporting Windows, Linux and macOS. Connect Claude Desktop, OpenCode, Codex and compatible MCP clients to real Godot projects while adding something ordinary AI coding workflows are missing: proof that the change actually works. Your AI agent still writes the code and builds the feature. Obssidian protects the working state, runs the real project, checks the result, captures evidence, executes gameplay regressions and can automatically restore protected files when verification fails. Build. Test. Debug. Verify. Ship. YOUR AI CAN CHANGE CODE. OBSSIDIAN MAKES IT PROVE THE CHANGE WORKS. A successful file edit does not mean a successful game. Scripts can parse but fail at runtime. A scene can load while gameplay is broken. A “fix” can introduce a regression somewhere else. An agent can confidently report success before Godot has even executed the result. Obssidian is built specifically around that verification gap. Before a risky change, it can establish a baseline and protect the working state. After the agent edits the project, Obssidian can launch Godot, reproduce the relevant workflow, inspect runtime output, execute regression scenarios, capture screenshot evidence, check performance and evaluate the result. If a protected verification is BLOCKED, the transaction can automatically restore the previous working files. That means failure becomes recoverable instead of destructive. A SAFETY LAYER FOR AGENTIC GODOT DEVELOPMENT Obssidian provides protected change transactions, real Godot preflight, runtime execution, gameplay regression workflows, screenshot evidence, runtime/debug reproduction, performance checks, release quality gates, audit history and automatic rollback. For AI clients with normal filesystem access, the agent uses its own coding tools while Obssidian wraps the work in a protected verification transaction. For sandboxed agents, Obssidian can expose a secure project-scoped read/apply-patch bridge instead of unrestricted filesystem access. All protected writes use project confinement and stale-write protection so the agent cannot silently overwrite a file that changed after it was inspected. BUILT FOR AGENTS — NOT FOR TOOL-COUNT MARKETING Obssidian does not try to expose hundreds of tiny commands to the model at once. The coding agent already knows how to write code. Instead, Obssidian gives it a compact surface focused on the operations that matter around the edit: inspect → baseline → protect → run → reproduce → verify → regress → measure → keep or rollback This keeps the AI flexible while Obssidian concentrates on safety, runtime access and evidence. You do not need a dedicated MCP command for every enemy, inventory system, UI panel or gameplay mechanic you might create. The agent develops. Obssidian protects and verifies. VERIFIED FAILURE RECOVERY — NOT JUST THE HAPPY PATH Our qualification workflow deliberately tested both successful and broken changes. A valid gameplay modification was applied and kept after verification. Gameplay regressions were executed against the real project. Performance validation was performed. Then a deliberate GDScript parser failure was introduced. Obssidian detected the broken state as BLOCKED, restored the protected files automatically and ran recovery verification. The final working project state was preserved. That failure path matters. A safety system should not only demonstrate that it works when everything goes right. CROSS-PLATFORM Windows • Linux • macOS The Obssidian runtime is built on a portable Node.js architecture without Windows-only native runtime dependencies. Windows: native workflow qualification completed. Linux: runtime qualification completed against Godot 4.7.1 Stable. macOS: supported by the cross-platform runtime architecture and packaged for macOS. Native macOS qualification is still pending, so we do not claim a native macOS VERIFIED badge yet. This distinction is intentional: supported and verified on native hardware are not treated as the same claim. WORKS WITH YOUR AI CODING WORKFLOW Use Obssidian with Claude Desktop, OpenCode, Codex and other compatible MCP clients. On supported clients, setup packages and configuration helpers are included to reduce manual MCP configuration. Obssidian runs locally. There is no Obssidian cloud account required for the runtime. Your AI provider remains separate: Obssidian is the bridge and verification layer, not the AI model itself. REAL GODOT, REAL RUNTIME EVIDENCE Obssidian is designed to go beyond static file inspection. It can work against the actual Godot project and runtime to establish whether the result behaves as expected. That includes project preflight, runtime/debug output, gameplay regression scenarios, screenshots, performance instrumentation and protected verification transactions. The goal is simple: Do not trust “the code looks correct” when Godot can test it. INCLUDED The package includes the Obssidian Godot MCP runtime, platform-specific setup files, Claude Desktop MCPB packages where applicable, OpenCode setup, Codex setup, Quick Start documentation and the Orbit Breaker qualification/demo project used to demonstrate the verification workflow. A single-user commercial license is included. REQUIREMENTS Godot 4.x Our current qualification baseline is Godot 4.7.1 Stable. Node.js 20+ is required for clients/installations that do not provide an embedded Node runtime. You also need an MCP-compatible AI client such as Claude Desktop, OpenCode or Codex. CURRENT RELEASE v0.5.2-alpha.2 Obssidian Godot MCP is an actively developed commercial alpha. The core protected-change, runtime verification, regression and rollback workflows have already undergone real qualification, but unusual project structures, client configurations and operating-system-specific edge cases may still exist. Alpha does not mean the safety claims are theoretical. It means we are still expanding compatibility and qualification coverage. PRIVACY & LOCAL OPERATION The Obssidian runtime operates locally between your MCP client and your Godot project. No Obssidian cloud account is required. Obssidian does not replace your AI provider or IDE. It gives your existing agent a controlled bridge into Godot and a verification layer around the work it performs. SUPPORT & FEEDBACK If you have difficulty installing, connecting or using Obssidian Godot MCP, leave a comment on this itch.io page. For technical reports, please include your operating system, AI client, Godot version and the exact error message or screenshot when possible. Compatibility reports and real-world workflow feedback are especially valuable during the alpha. Your agent writes the change. Obssidian protects the project, runs the game and checks the result. Build. Test. Debug. Verify. Ship.