Security & privacy

Godot MCP Studio is local-first by design. The parts that touch your code run on your machine, not our servers.

Project work runs locally

The MCP server runs on your computer as a local process. Your AI client talks to it directly. Reading and editing your project happens on your machine. Your AI client may send the context it reads to its own service; check that client's privacy settings and policies.

Image Studio's editing tools and permanent asset library are local too. A hosted generation job uploads only the source images and masks you explicitly select after the desktop app shows the operation and credit cost. It never uploads your Godot project, scenes, or scripts.

Control your editor connection

The connection to Godot is restricted to your own computer and requires pairing with the project. Revoke connections in the Godot dock disconnects existing clients and requires them to pair again.

The addon is readable on purpose

The Godot editor addon installs as plain GDScript into your project, so you can audit every line of the code that touches your scenes and files. Nothing that runs inside your editor is hidden. The MCP server and desktop app are compiled, licensed binaries; the addon they install is open for inspection.

Agent feedback and usage insights

In Pro, the AI agent sends us a short feedback note when an MCP tool fails or misbehaves, when a tool it needed is missing, or with an idea or praise. Feedback is always on, because it is how we find and fix broken tools. A note is a short, generic message tied to a tool or skill name; it never includes your code, prompts, project details, file content, paths, credentials, usernames, or URLs. Agents are instructed to leave them out, and both the MCP server and our API reject messages that look like private data.

Share skill usage insights in Settings is on by default and records which bundled skill guided a task. Turn it off at any time to stop those reports.

Both include skill, bundle, app, edition, and AI-client versions plus an opaque project ID. Lite sends neither.

What we don't collect

• No general desktop or MCP analytics beyond the privacy-limited Pro feedback and usage insights described above.
• We never read, upload, or store your Godot projects. Code stays with you.
• Image generation uses only the selected images, masks, and prompt needed for that request. Temporary hosted files are private and removed within seven days.
• We don't sell or share your data. See the full Privacy Policy.

What we do store

Only what's needed to run your account: your email and name, authentication details, and your license and device activations. A payment processor handles payments, so we never see your card details.

Permission modes are enforced server-side

The permission mode you choose is enforced by the MCP server, not just the UI. In Safe Edit, destructive or command-running actions require confirmation in Godot MCP Studio, so the question does not depend on which AI client you use. If the app is not running, the connected MCP client is asked instead, and the action is refused when that client cannot show the prompt. Full Control allows these actions without asking, except for installing an add-on that ships native code, which always asks. See Permission modes.

Redacted diagnostics

Pro can export a Diagnostics Bundle for support from Settings, under Support. It contains app, add-on, server, Godot, and rules versions; bridge state; AI client setup status; health-check summaries; and recent errors. It never includes bridge tokens, license tokens, the project path, or project source files.

Your responsibility

Keep your license code and account private, and use version control on your projects. As with any tool that can edit code, a clean git history is your best undo.