Ffennaradocs

Home

MCP

Fennara MCP lets AI apps use Fennara's local Godot-aware tools: script edits, scene edits, diagnostics, validation, screenshots, node properties, class info, SemanticSearch, shader search, and project settings.

Use MCP when you want an external AI app to work on your Godot project with Fennara's tools instead of plain filesystem access.

For a higher-level explanation of how Fennara differs from command-style Godot MCP servers, see Godot MCP.

MCP tools require an active 14-day trial or Fennara Pro. The Godot plugin reads the local device identity created by the installer and asks Fennara whether the saved API key has trial or Pro access before running MCP tool calls.

Fennara MCP supports Godot 4.x projects only. Godot 3.x is not supported by either the Fennara MCP server or the Godot plugin.

Install Fennara MCP

Run the Fennara installer first. From the Fennara dashboard, copy the install command for your operating system and run it in your terminal. The installer creates the local device identity, lets you choose a Godot project, installs the plugin, copies the local MCP server, and can configure supported MCP apps for you.

If you have not run the installer yet, start with Get Started. That page includes the dashboard steps and setup videos.

After install, the MCP executable is usually here:

Windows: %LOCALAPPDATA%\Fennara\bin\fennara-mcp.exe
macOS:   ~/Library/Application Support/Fennara/bin/fennara-mcp
Linux:   ~/.local/share/fennara/bin/fennara-mcp

Use the exact path from your machine when editing another app's MCP config.

Supported apps

The installer can configure common MCP clients automatically when it can find their config files.

Supported installer targets include Codex, Cursor, Cline, VS Code, Claude Code, Claude Desktop, and Antigravity.

If your app is listed in the installer, use the installer button first. It creates a backup before changing the config.

Tool availability

MCP exposes the local tools that can safely run through a desktop MCP client:

  • script and file writes through write_or_update_file
  • one-off scene edit scripts
  • scene tree inspection
  • custom resource saving
  • GDScript diagnostics
  • runtime error capture with Debugger Errors stack traces
  • scene screenshots
  • node property inspection
  • Godot class info
  • scene validation
  • project settings
  • semantic_search for indexed project code search
  • search_shaders for shader examples

MCP does not expose broad filesystem-style tools like read_file or file_ops. External MCP apps can still use their own normal file/search features, but Fennara MCP keeps its own surface focused on Godot-aware operations and validation.

MCP also does not expose plugin-only account features such as billing usage, conversation history, context compaction controls, or dashboard actions.

Manual setup

Every MCP app has two details you need to know:

  • where its MCP config file lives
  • whether that config is JSON, TOML, or another format

After you know those two details, add Fennara as a local stdio MCP server named fennara.

For JSON configs that use mcpServers, the entry usually looks like this:

{
  "mcpServers": {
    "fennara": {
      "command": "C:\\Users\\you\\AppData\\Local\\Fennara\\bin\\fennara-mcp.exe",
      "args": [],
      "env": {}
    }
  }
}

For Cline, you can also give Fennara longer tool calls by adding timeout in seconds:

{
  "mcpServers": {
    "fennara": {
      "command": "C:\\Users\\you\\AppData\\Local\\Fennara\\bin\\fennara-mcp.exe",
      "args": [],
      "env": {},
      "timeout": 300
    }
  }
}

For VS Code-style JSON configs, the top-level key is usually servers:

{
  "servers": {
    "fennara": {
      "type": "stdio",
      "command": "C:\\Users\\you\\AppData\\Local\\Fennara\\bin\\fennara-mcp.exe",
      "args": [],
      "env": {}
    }
  }
}

For Codex-style TOML configs, the entry looks like this:

[mcp_servers.fennara]
command = "C:\\Users\\you\\AppData\\Local\\Fennara\\bin\\fennara-mcp.exe"
startup_timeout_sec = 30
tool_timeout_sec = 300

Claude Code does not currently use a per-server timeout field in the Fennara installer config. If Fennara MCP tools time out in Claude Code, launch Claude Code with a larger tool timeout environment variable:

MCP_TOOL_TIMEOUT=600000 claude

On Windows PowerShell:

$env:MCP_TOOL_TIMEOUT = "600000"; claude

Do not paste JSON into a TOML config or TOML into a JSON config. Match the app's existing format.

Common config locations

These are common locations. Apps can change them, and some apps support both global and project-specific config.

Codex:          ~/.codex/config.toml
Cursor:         ~/.cursor/mcp.json or <project>/.cursor/mcp.json
Cline:          ~/.cline/data/settings/cline_mcp_settings.json
VS Code:        user mcp.json or <project>/.vscode/mcp.json
Claude Code:    ~/.claude.json or <project>/.mcp.json
Claude Desktop: macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
                Windows: %APPDATA%\Claude\claude_desktop_config.json
Antigravity:    ~/.gemini/config/mcp_config.json

If an app has a command like Open MCP Config, prefer that over guessing a path.

If your app is not listed

If the installer does not support your MCP app yet, use this workflow.

  1. Search online for the app's official MCP config location.
  2. Confirm the config format: JSON, TOML, YAML, or something else.
  3. Find your Fennara MCP executable path from Install Fennara MCP.
  4. Ask an LLM to produce the exact config edit.

Use a prompt like this:

I have a local stdio MCP server executable at:
<paste the full path to fennara-mcp here>

I want to add it to <app name>.
The app's MCP config file is:
<paste config path here>

The config format is <JSON/TOML/etc>.

Please show the smallest safe edit to add a server named "fennara".
Preserve all existing config. If the app needs "mcpServers" or "servers",
use the key required by that app's official docs.

Then review the result before saving. Make a backup of the config file first.

Restart the app

Most MCP apps only load MCP servers on startup.

After editing the config, fully quit and reopen the app. If Fennara does not appear, check:

  • the executable path is absolute and exists
  • JSON or TOML syntax is valid
  • the server name is fennara
  • the app is looking at the config file you edited
  • your Godot project has the Fennara plugin installed and configured
  • your API key has an active trial or Pro subscription

Project routing

Fennara MCP sends tool calls to the Godot project marked as the MCP target.

Open the project in Godot, then use Set as MCP Target from the Fennara plugin menu/settings. The plugin will confirm with: This project is now the MCP target.

Use this whenever you have multiple Godot projects open, or when an MCP app is connected but seems to be acting on the wrong project.

← Previous
Tools
Next →
Pricing and credits