Setup with agent

Better Godot MCP — Agent Setup Guide

Give this file to your AI agent to automatically set up better-godot-mcp.

Note: Plugin install (Option 1) uses stdio mode — no auth required for godot. The previous default of HTTP transport has been changed to stdio. If you relied on HTTP mode, set MCP_TRANSPORT=http or pass --http flag.

Method overview

This plugin supports 1 install method only: stdio via plugin install (uvx/npx). Reason: the plugin needs direct host access to your project files (Godot project / repo path) and doesn’t ship Docker or HTTP variants.

For comparison, the other 6 plugins in this stack (better-notion-mcp, better-email-mcp, better-telegram-mcp, wet-mcp, mnemo-mcp, imagine-mcp) support 3 methods:

1. Default — Plugin install (uvx/npx) stdio
2. Fallback — Docker stdio (Windows/macOS PATH issues)
3. Recommended — Docker HTTP (multi-device, OAuth/relay form, claude.ai web)

⚠️ Mutually exclusive — pick ONE per plugin (applies to those 6 plugins, not godot): For the 6 plugins above that offer Method 2 (Docker stdio) or Method 3 (HTTP), do NOT stack /plugin install AND a user mcpServers override — both would load simultaneously and create duplicate entries (plugin’s npx/uvx stdio + your override). Plugin matching is by endpoint (URL or command string) per CC docs, not by name — and npx/uvx ≠ docker ≠ HTTP URL, so all three are distinct endpoints. Choosing Method 2 or Method 3 means losing the plugin’s skills/agents/hooks/commands. better-godot-mcp only offers Method 1, so this note is informational only — there is no Docker stdio or HTTP variant to conflict with the plugin install here.

Option 1: Claude Code Plugin (Recommended)

Credential prompts at install

When you run /plugin install, Claude Code prompts you for the following credentials (declared in userConfig per CC docs). Sensitive values are stored in your system keychain and persist across /plugin update:

Field	Required	Where to obtain
GODOT_PATH	Optional	Absolute path to Godot 4.x binary; auto-detect from PATH if empty
GODOT_PROJECT_PATH	Optional	Default project root (can override per tool call)

Steps

/plugin marketplace add n24q02m/claude-plugins
/plugin install better-godot-mcp@n24q02m-plugins

This installs the server in stdio mode with skills: /build-scene, /debug-issue, /add-mechanic. No environment variables required — it just works.

Optionally set GODOT_PROJECT_PATH to point at your Godot project; otherwise pass project_path per tool call.

Environment Variables

Variable	Required	Default	Description
GODOT_PROJECT_PATH	No	—	Default project path. Tools also accept project_path parameter per call.
GODOT_PATH	No	Auto-detected	Path to Godot binary. Auto-detected from PATH and common install locations.
MCP_TRANSPORT	No	stdio	Set to http to run in HTTP mode (advanced; not in scope of this guide). The --http CLI flag is equivalent.
PORT	No	0 (auto)	HTTP port when MCP_TRANSPORT=http. Set explicitly when you need a stable port.

Authentication

No authentication required. This server operates on local files only.

Verification

After setup, verify the server is working by calling the config tool:

Use the config tool with action "check" to verify the server is connected and can find Godot.

Expected: the tool returns Godot binary path and project status.