Troubleshooting

If something’s broken, chances are it’s one of the errors below. Work through the matching section, and if the fix doesn’t stick, email [email protected] with the diagnostics at the bottom of this page.

Tier “community” despite paid license

You set the key but godotiq auth status still reports tier: community.

Usually one of:

• The env var didn’t make it into the MCP client’s process.
• The MCP client wasn’t fully restarted.
• The key is pasted with accidental quotes or whitespace.

Run this from a fresh shell to see what the server actually sees:

godotiq auth status --json

Then confirm the key is present in your client’s config:

Claude Code

Edit ~/.claude/claude_desktop_config.json (macOS/Linux) or %APPDATA%\Claude\claude_desktop_config.json (Windows). The env block of the godotiq server entry must contain GODOTIQ_LICENSE_KEY.

Codex

Edit the MCP server definition and confirm the env var is set verbatim — no quotes, no trailing spaces. Restart Codex after editing.

Cursor

Cursor settings → MCP → godotiq → Environment. GODOTIQ_LICENSE_KEY must be listed. Then quit Cursor fully (not just close the window) and reopen.

Windsurf

Check your Windsurf MCP config file for the env entry on the godotiq server. Fully quit and relaunch after any edit.

VS Code

If you’re using the MCP-compatible VS Code extension, open the extension’s settings and ensure GODOTIQ_LICENSE_KEY is present in the server’s env. Reload the window.

If the key looks right and the client was fully restarted, see /manage/?reason=missing.

Contact support: [email protected].

LIMIT_REACHED error

You’ve activated on more devices than the current cap allows.

1. Open the Polar customer portal at polar.sh/godotiq/portal and deactivate a seat on a machine you no longer use.
2. Restart your MCP client on the current machine.
3. Re-run godotiq auth status.

Deep-link to this in the reason matrix: /manage/?reason=limit_reached.

Contact support: [email protected].

KEY_REVOKED error

Your license key is no longer valid — usually because the Polar order was refunded or the key was manually revoked.

1. Check your email for a refund or cancellation notice from Polar.
2. If you didn’t initiate the cancellation, email [email protected] with your order ID so we can investigate.

Do not re-add the key until you’ve heard back — the error will reappear.

Deep-link: /manage/?reason=key_revoked.

Contact support: [email protected].

MIGRATION_REQUIRED error

You reinstalled your OS or moved to a new machine; GodotIQ needs a fresh activation handshake for this device.

1. If the CLI supports it, run:

   godotiq auth status --refresh

2. Otherwise, open polar.sh/godotiq/portal, deactivate the old machine, then restart the MCP client on this one.

3. Run godotiq auth status to confirm the tier is back to pro.

Deep-link: /manage/?reason=migration_required.

Contact support: [email protected].

BUNDLE_UNAVAILABLE / first Pro run offline

The first Pro activation needs a network connection to download the signed Pro bundle from pro.godotiq.com. After that, subsequent runs work offline until the receipt expires.

1. Check connectivity:

   curl -I https://pro.godotiq.com/health

2. If you’re behind a corporate firewall, ask IT to allow HTTPS to api.polar.sh and pro.godotiq.com.

3. Clear the local cache and retry:

   godotiq auth reset-bundle
   godotiq auth status

Contact support: [email protected].

CLOCK_ROLLBACK_DETECTED

Your system clock moved backwards. GodotIQ treats receipt timestamps as monotonic — if the clock jumps back, receipts look invalid.

Resync your system clock:

macOS

sudo sntp -sS time.apple.com

Windows

Open Settings → Time & Language → Date & Time and click Sync now.

Linux

sudo timedatectl set-ntp true

Then restart your MCP client and run godotiq auth status.

Contact support: [email protected].

Tool preview still shows after purchase

Some MCP clients cache the tool list between sessions. After activating Pro you may still see Pro tools marked as preview/locked until the cache is refreshed.

1. Fully quit the MCP client (close the app — do not just reload the project).
2. Reopen it.
3. Run godotiq auth status. You should see license: pro (active).

Contact support: [email protected].

Addon confusion vs Pro confusion

The Godot addon and the Pro license are separate things — they solve different problems.

• The Godot addon is a pure-GDScript addon for the Community tier. It enables the 18 bridge tools that talk to a running editor or game (scene ops, input, screenshots, etc.). The addon is free, MIT, optional, and has nothing to do with Pro.
• GodotIQ Pro unlocks 14 filesystem-only intelligence tools (project summary, dependency graph, scene map, flow traces, project memory, …). These run purely from your project files and do not require the addon.

If you installed the addon expecting Pro features, you likely want both the addon and a Pro license.

Contact support: [email protected].

How to collect a support report

When you email support, include as much of this as you can:

• Redacted godotiq auth status --json output (strip your license key).
• OS and version (macOS 14.x / Windows 11 / Ubuntu 22.04).
• Python version (python3 --version).
• godotiq version (pip show godotiq | grep Version).
• MCP client (Claude Code / Codex / Cursor / Windsurf / VS Code).
• Exact error message — copy-paste, don’t paraphrase.
• Redacted config block (replace the key with GODOTIQ-XXXX-XXXX).

Always redact the license key before sharing. The first few and last few characters are enough for us to identify it in our records.

Email: [email protected] · More options at /support/.