Skip to content
GodotIQ

Cursor

Cursor supports MCP servers through its configuration file. GodotIQ integrates with Cursor’s AI to give it spatial, code, and runtime understanding of your Godot project.

Running godotiq install-addon automatically creates .cursorrules with development rules for this client. No manual configuration needed.

Setup

Section titled “Setup”

  1. Install GodotIQ:

    Terminal window
    pip install godotiq

  2. Create the MCP config file. Toggle Community or Pro and copy:

    .cursor/mcp.json json 
    {
  "mcpServers": {
    "godotiq": {
      "command": "uvx",
      "args": ["godotiq"],
      "env": {
        "GODOTIQ_PROJECT_ROOT": "<REPLACE_WITH_YOUR_GODOT_PROJECT_PATH>"
      }
    }
  }
}

    macOS/Linux: pwd · Windows PowerShell: (Get-Location).Path

    Omit GODOTIQ_LICENSE_KEY to use Community. Add your license key to unlock the 14 Pro intelligence tools.

    Save the JSON to .cursor/mcp.json in your project root. Swap in your project path (placeholder: <REPLACE_WITH_YOUR_GODOT_PROJECT_PATH>). uvx auto-installs godotiq on first use.

  3. Restart Cursor to load the MCP server.

  4. Verify: Ask Cursor’s AI: “Ping GodotIQ”. It should confirm the connection.

Tips for Cursor

Section titled “Tips for Cursor”

Use Composer Mode

Section titled “Use Composer Mode”

Cursor’s Composer mode (Cmd+I / Ctrl+I) works best for GodotIQ workflows. It lets the AI call tools, read results, and make code changes in a single flow.

Context Files

Section titled “Context Files”

Add your .godotiq.json configuration file to Cursor’s context (drag it into the chat or use @file) so the AI understands your project’s conventions and settings.

GDScript Editing

Section titled “GDScript Editing”

When the AI suggests GDScript changes based on GodotIQ analysis, you can apply them directly in the editor. Common workflow:

  1. Ask about a problem: “Why does the enemy get stuck at the door?”
  2. GodotIQ analyzes the spatial layout and code flow
  3. Cursor suggests a fix in the relevant .gd file
  4. Review and apply with one click

Multi-File Operations

Section titled “Multi-File Operations”

Cursor excels at multi-file refactoring. Use GodotIQ’s godotiq_impact_check first to understand the blast radius, then let Cursor make the changes across all affected files.

Activate Pro

Section titled “Activate Pro”

Toggle Pro in the snippet above and paste your license key in place of GODOTIQ-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX. Save .cursor/mcp.json and restart Cursor.

If activation doesn’t take, see Manage or Troubleshooting.

Advanced Configuration

Section titled “Advanced Configuration”

Bridge Port

Section titled “Bridge Port”

The addon communicates via WebSocket on port 6007 by default. If that conflicts, update the addon_port in your .godotiq.json and the Godot addon settings to match.

Troubleshooting

Section titled “Troubleshooting”

MCP server not loading

Section titled “MCP server not loading”
  • Ensure .cursor/mcp.json is in the project root (same level as project.godot)
  • Check that the command path is correct and godotiq is installed
  • Restart Cursor completely (quit and reopen)

Tools not appearing

Section titled “Tools not appearing”

Cursor may need a moment to discover available tools after restart. If tools still don’t appear, check the MCP server logs in Cursor’s output panel.

Bought Pro?

Section titled “Bought Pro?”
  1. Toggle Pro in the snippet above and paste your license key.
  2. Save .cursor/mcp.json and restart Cursor.
  3. Run godotiq auth status — expected: license: pro (active).
  4. If activation fails, visit Manage or Troubleshooting. Or email [email protected].
Installation Full installation guide with all client options.
Workflows Common workflow patterns for AI-assisted game development.