What can godot-mcp-server do?

godot project introspection and metadata extraction, gdscript code generation and completion, scene and node tree manipulation via mcp, gdscript debugging and error analysis, asset and resource discovery with ai context, godot documentation and api reference lookup, multi-file gdscript refactoring with dependency tracking, performance profiling and optimization suggestions

godot-mcp-server

MCP ServerFree

MCP server for Godot game engine integration

Open Source

/ 100

8 capabilities

Capabilities8 decomposed

godot project introspection and metadata extraction

Medium confidence

Exposes Godot project structure, scene hierarchy, script files, and engine metadata through MCP protocol endpoints. Implements file-system scanning and GDScript AST parsing to catalog project assets, node trees, and class definitions without requiring Godot editor to be running. Returns structured JSON representations of project topology for AI context building.

Solves for

Get a complete map of my Godot project structure to provide context to an AI assistantExtract scene hierarchies and node relationships for code generation tasksRetrieve GDScript class definitions and method signatures for AI-assisted refactoringUnderstand project dependencies and asset organization for debugging

Best for

Game developers using Claude or other MCP-compatible AI assistants for Godot development

Teams building AI-assisted game development workflows

Solo indie developers prototyping games with AI pair programming

Requires

Godot 4.0+ project structure

Node.js 16+ runtime for MCP server

MCP-compatible client (Claude, custom LLM application)

Limitations

Requires project to follow standard Godot directory conventions; custom folder structures may not be fully indexed

GDScript parsing is AST-based and may not handle all edge cases in complex metaprogramming patterns

No real-time sync — metadata is point-in-time snapshot; changes require re-scan

What makes it unique

Bridges Godot game engine and MCP protocol by implementing native Godot project parsing without requiring editor subprocess; uses GDScript AST analysis to extract semantic structure rather than regex-based text matching

vs alternatives

Provides deeper Godot-specific context than generic file-system MCP servers because it understands GDScript syntax and Godot scene format natively

gdscript code generation and completion

Medium confidence

Generates GDScript code snippets, class stubs, and method implementations based on project context and user prompts. Leverages project introspection to understand existing class hierarchies and coding patterns, then uses LLM to synthesize new code that matches project conventions. Integrates with MCP tool-calling to accept structured requests for specific code patterns (e.g., 'generate a physics-based player controller').

Solves for

Generate boilerplate GDScript classes that inherit from project base classesCreate signal handlers and callback methods matching existing code styleStub out scene-specific scripts with proper node references and lifecycle methodsGenerate input handling, physics, and animation code following project patterns

Best for

Game developers accelerating prototyping with AI-assisted scripting

Teams establishing coding standards and wanting AI to enforce them

Developers learning Godot who want pattern-based code suggestions

Requires

Godot 4.0+ (GDScript 2.0)

Project introspection capability enabled

LLM backend with function-calling support (Claude, GPT-4, etc.)

Limitations

Generated code requires manual review for game logic correctness; AI may produce syntactically valid but semantically incorrect physics or gameplay code

No built-in testing or validation — generated scripts are not automatically tested against project

Limited to GDScript 2.0 syntax; older GDScript 1.0 projects may require manual adaptation

What makes it unique

Generates GDScript with awareness of Godot-specific patterns (signals, node references, lifecycle methods, physics APIs) by analyzing project codebase first; not generic code generation but Godot-idiom-aware synthesis

vs alternatives

More contextual than generic LLM code completion because it understands Godot scene structure and can reference existing project classes and patterns in generated code

scene and node tree manipulation via mcp

Medium confidence

Provides MCP tools to query and modify Godot scene hierarchies programmatically. Parses .tscn (scene) files and exposes node tree structure, properties, and connections as queryable data. Supports read operations (list nodes, get properties) and write operations (add nodes, modify properties, update connections) by manipulating scene files directly or via Godot's GDScript API if editor is running.

Solves for

Query scene structure to understand node relationships and dependenciesProgrammatically add or remove nodes from scenes based on game design requirementsModify node properties (position, scale, material, etc.) in bulk across multiple scenesUpdate signal connections and node references when refactoring scene structure

Best for

Developers automating scene setup and configuration tasks

Teams building procedural level generation or dynamic scene composition

Game designers wanting to script scene modifications without manual editor work

Requires

Godot 4.0+ project

Write access to .tscn scene files

MCP server running with file system access

Limitations

Scene file manipulation is text-based; complex scene changes may require Godot editor validation to ensure consistency

No undo/redo support — changes are direct file writes; requires external version control for safety

Cannot modify scenes that are currently open in Godot editor without reload; potential for conflicts

What makes it unique

Implements scene manipulation as MCP tools that parse and modify .tscn files directly, enabling headless scene editing without requiring Godot editor subprocess; uses GDScript-compatible NodePath syntax for node addressing

vs alternatives

Allows AI assistants to modify game scenes programmatically without opening Godot editor, enabling batch operations and automation that would be tedious in GUI

gdscript debugging and error analysis

Medium confidence

Captures GDScript runtime errors, warnings, and debug output from Godot execution and surfaces them to MCP clients for analysis. Parses Godot debug console output and error stack traces to extract file paths, line numbers, and error messages. Integrates with project introspection to provide source code context and suggest fixes based on error patterns and project conventions.

Solves for

Get AI analysis of runtime errors with suggested fixes based on project contextUnderstand error stack traces and trace execution flow through multiple GDScript filesIdentify common error patterns and get refactoring suggestions to prevent themDebug script behavior by analyzing console output and error logs

Best for

Developers using AI assistants to troubleshoot game runtime issues

Teams wanting automated error analysis and fix suggestions

Solo developers learning Godot who need help understanding error messages

Requires

Godot 4.0+ running in debug mode

Access to Godot debug console output (stdout/stderr)

Project introspection capability for context

Limitations

Requires Godot editor or headless instance to be running; cannot analyze errors from offline builds

Error context is limited to console output; cannot inspect runtime memory state or variable values

Fix suggestions are heuristic-based and may not address root cause; require developer verification

What makes it unique

Parses Godot-specific error formats and integrates with project context to provide targeted debugging assistance; uses GDScript AST and project structure to suggest fixes that match existing code patterns

vs alternatives

More useful than generic error analysis because it understands Godot's error messages, node paths, and signal system; can correlate errors to scene structure and existing code

asset and resource discovery with ai context

Medium confidence

Scans Godot project for game assets (textures, models, audio, animations, shaders) and exposes metadata through MCP. Catalogs resource paths, file types, and properties (resolution, format, duration) to build a queryable asset inventory. Enables AI assistants to understand available resources and suggest asset usage in code generation or scene composition tasks.

Solves for

Query available textures, models, and audio files to reference in generated codeGet recommendations for which assets to use in a scene based on project inventoryUnderstand asset organization and naming conventions to maintain consistencyAutomate asset assignment in scenes (e.g., apply textures to materials, assign audio to players)

Best for

Game developers wanting AI to suggest appropriate assets during code generation

Teams with large asset libraries needing AI-assisted asset discovery

Developers automating asset assignment and material setup

Requires

Godot 4.0+ project structure

Read access to res:// filesystem

Asset files in standard Godot formats (PNG, JPG, OGG, GLTF, etc.)

Limitations

Asset metadata is static; does not track asset usage or dependencies in real-time

Cannot analyze asset content (e.g., image dimensions, audio duration) without parsing file headers; may be slow for large projects

No asset preview generation; AI cannot see visual content, only metadata

What makes it unique

Indexes Godot project assets and exposes them as queryable MCP resources; enables AI to reference actual project assets in code generation rather than generating placeholder paths

vs alternatives

Provides asset-aware code generation because AI can see what textures, models, and audio are available and suggest them in generated scripts, rather than generating generic asset paths

godot documentation and api reference lookup

Medium confidence

Provides MCP tools to query Godot engine documentation and API reference data. Indexes Godot class definitions, method signatures, property types, and signal definitions from official documentation or bundled reference data. Enables AI assistants to look up correct API usage, parameter types, and return values when generating or reviewing GDScript code.

Solves for

Look up correct method signatures and parameter types for Godot classesFind available signals and properties for a given node typeGet documentation for Godot built-in classes and methodsVerify API usage in generated code against official Godot API

Best for

AI assistants generating GDScript code that needs to reference correct APIs

Developers learning Godot API and wanting quick reference lookups

Teams enforcing correct API usage in code generation

Requires

Godot documentation data (bundled or downloaded)

MCP server with documentation index

Godot version specification (4.0, 4.1, etc.) for correct API version

Limitations

Documentation is static; does not update automatically when Godot engine is updated

Limited to official Godot API; custom C++ modules and third-party addons not included

No code examples or tutorials; only API signatures and descriptions

What makes it unique

Exposes Godot API reference as queryable MCP resources, enabling AI to verify and look up correct API usage during code generation; uses structured API definitions rather than free-text documentation

vs alternatives

Allows AI code generation to be grounded in actual Godot API definitions, reducing hallucinated or incorrect API calls compared to LLMs generating code from training data alone

multi-file gdscript refactoring with dependency tracking

Medium confidence

Supports refactoring operations across multiple GDScript files while tracking and updating dependencies. Parses GDScript imports, class references, and signal connections to understand inter-file dependencies. When refactoring (e.g., renaming a class, moving methods), automatically updates all references across the project to maintain consistency. Uses AST-based analysis to ensure refactoring is semantically correct.

Solves for

Rename a class and automatically update all imports and references across the projectMove methods between classes and update all call sitesExtract common code into a base class and update inheritance across multiple filesRefactor signal definitions and update all connected handlers

Best for

Teams maintaining large GDScript codebases needing safe refactoring

Developers using AI to suggest and execute multi-file refactorings

Projects with complex class hierarchies and cross-file dependencies

Requires

Godot 4.0+ project with GDScript 2.0

Write access to all .gd script files

GDScript AST parser (tree-sitter or equivalent)

Limitations

Refactoring is AST-based and may not handle all GDScript edge cases (metaprogramming, dynamic imports)

No built-in undo; requires version control to safely revert failed refactorings

Cannot refactor code that is currently running in Godot editor; requires project reload

What makes it unique

Implements cross-file refactoring with dependency tracking using GDScript AST analysis; automatically updates all references when refactoring, not just the target element

vs alternatives

Safer and more comprehensive than manual refactoring or simple find-replace because it understands GDScript syntax and can distinguish between actual references and string literals or comments

performance profiling and optimization suggestions

Medium confidence

Analyzes GDScript code and Godot project configuration to identify performance bottlenecks and suggest optimizations. Parses code for common inefficiencies (excessive allocations in _process, inefficient node queries, unoptimized physics settings) and correlates with profiling data if available. Provides AI-generated optimization suggestions tailored to the specific code patterns found in the project.

Solves for

Identify performance bottlenecks in GDScript code and get optimization suggestionsAnalyze Godot project settings for performance issues (physics, rendering, memory)Get recommendations for optimizing hot paths and frequently-called methodsUnderstand performance implications of code patterns and refactor for efficiency

Best for

Game developers optimizing performance-critical code

Teams building resource-constrained games (mobile, web)

Developers wanting AI-assisted performance analysis without manual profiling

Requires

Godot 4.0+ project

GDScript code analysis capability

Optional: Godot profiler data for runtime analysis

Limitations

Suggestions are heuristic-based; actual performance impact depends on runtime context and hardware

Cannot profile running game without Godot profiler integration; analysis is static

Optimization suggestions may conflict with code readability or maintainability; require trade-off decisions

What makes it unique

Analyzes GDScript code patterns for performance issues and generates optimization suggestions using Godot-specific knowledge (e.g., _process vs _physics_process, node query efficiency, memory allocation patterns)

vs alternatives

More targeted than generic code analysis because it understands Godot-specific performance concerns and can suggest engine-appropriate optimizations rather than generic code improvements

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with godot-mcp-server, ranked by overlap. Discovered automatically through the match graph.

MCP Server25

Godot MCP

** - MCP server for interacting with the Godot game engine, providing tools for editing, running, debugging, and managing scenes in Godot projects.

scene creation and node hierarchy manipulationdual-execution strategy: cli commands and bundled gdscriptproject execution and debug output capturescene persistence and file i/o

4 shared capabilities

Repository25

MBro

** - A powerful interactive terminal **M**CP **Bro**wser client with tab completion and automatic documentation that allows you to work with multiple MCP servers, manage tools, and create complex workflows using AI assistants.

tool schema introspection and documentation generationinteractive mcp browser with tab completion and auto-documentation

2 shared capabilities

MCP Server22

@modelcontextprotocol/server-threejs

Three.js 3D visualization MCP App Server

scene query and spatial analysis via mcpthree.js scene graph exposure via mcp protocol

2 shared capabilities

MCP Server22

Maya MCP

** - MCP server for Autodesk Maya

scene state querying and introspection

1 shared capability

MCP Server47

Generative-Media-Skills

Multi-modal Generative Media Skills for AI Agents (Claude Code, Cursor, Gemini CLI). High-quality image, video, and audio generation powered by muapi.ai.

mcp server-based tool exposure with json schema validation

1 shared capability

MCP Server23

Unity3d Game Engine

** - MCP Server to control and interact with Unity3d Game Engine for game development

hierarchical scene graph querying and gameobject selection

1 shared capability

Best For

✓Game developers using Claude or other MCP-compatible AI assistants for Godot development
✓Teams building AI-assisted game development workflows
✓Solo indie developers prototyping games with AI pair programming
✓Game developers accelerating prototyping with AI-assisted scripting
✓Teams establishing coding standards and wanting AI to enforce them
✓Developers learning Godot who want pattern-based code suggestions
✓Developers automating scene setup and configuration tasks
✓Teams building procedural level generation or dynamic scene composition

Known Limitations

⚠Requires project to follow standard Godot directory conventions; custom folder structures may not be fully indexed
⚠GDScript parsing is AST-based and may not handle all edge cases in complex metaprogramming patterns
⚠No real-time sync — metadata is point-in-time snapshot; changes require re-scan
⚠Limited to local filesystem access; cannot introspect remote or cloud-based Godot projects
⚠Generated code requires manual review for game logic correctness; AI may produce syntactically valid but semantically incorrect physics or gameplay code
⚠No built-in testing or validation — generated scripts are not automatically tested against project

Requirements

Godot 4.0+ project structureNode.js 16+ runtime for MCP serverMCP-compatible client (Claude, custom LLM application)Read access to project filesystemGodot 4.0+ (GDScript 2.0)Project introspection capability enabledLLM backend with function-calling support (Claude, GPT-4, etc.)MCP client integration

Input / Output

Accepts: project_path (string), scene_file_path (string), script_file_path (string), code_request (string description), context_scope (scene/class/method), style_reference (existing script file), scene_path (string), node_path (string, NodePath format), property_updates (JSON object), node_definition (JSON with type, properties), error_log (string, console output), stack_trace (string, Godot format), script_context (optional, specific file), asset_type_filter (string: texture, model, audio, etc.), search_query (string, asset name or path), class_name (string), method_name (string), search_query (string), refactoring_type (string: rename, extract, move), target_element (string: class name, method name), new_name (string, for rename operations), scope (string: file, project), script_file (string, GDScript code), profiling_data (optional, JSON from Godot profiler), performance_target (string: mobile, web, desktop)

Produces: JSON (project metadata), JSON (scene hierarchy), JSON (GDScript AST/signatures), GDScript code (string), code_diff (structured changes), node_tree (JSON hierarchy), property_values (JSON), operation_result (success/error), error_analysis (JSON with parsed components), suggested_fixes (array of strings), context_code (relevant source snippets), asset_list (JSON array with metadata), asset_properties (JSON with dimensions, format, duration), api_definition (JSON with signature, parameters, return type), documentation (string, description and usage notes), related_classes (array of related class names), refactoring_plan (JSON with affected files and changes), refactored_files (array of updated script contents), dependency_graph (JSON showing updated references), bottleneck_analysis (JSON with identified issues), optimization_suggestions (array of suggested changes), refactored_code (optimized GDScript snippets)

UnfragileRank

Adoption15%(30% weight)

Quality17%(25% weight)

Ecosystem42%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

8 capabilities

Visit godot-mcp-server→

Package Details

npm

Registry

0.5.0

Version

Weekly Downloads

About

MCP server for Godot game engine integration

Alternatives to godot-mcp-server

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of godot-mcp-server?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

mcp registry

Looking for something else?

Search →

Capabilities8 decomposed

godot project introspection and metadata extraction

Medium confidence

Solves for

Best for

Game developers using Claude or other MCP-compatible AI assistants for Godot development

Teams building AI-assisted game development workflows

Solo indie developers prototyping games with AI pair programming

Requires

Godot 4.0+ project structure

Node.js 16+ runtime for MCP server

MCP-compatible client (Claude, custom LLM application)

Limitations

Requires project to follow standard Godot directory conventions; custom folder structures may not be fully indexed

GDScript parsing is AST-based and may not handle all edge cases in complex metaprogramming patterns

No real-time sync — metadata is point-in-time snapshot; changes require re-scan

What makes it unique

vs alternatives

Provides deeper Godot-specific context than generic file-system MCP servers because it understands GDScript syntax and Godot scene format natively

gdscript code generation and completion

Medium confidence

Solves for

Best for

Game developers accelerating prototyping with AI-assisted scripting

Teams establishing coding standards and wanting AI to enforce them

Developers learning Godot who want pattern-based code suggestions

Requires

Godot 4.0+ (GDScript 2.0)

Project introspection capability enabled

LLM backend with function-calling support (Claude, GPT-4, etc.)

Limitations

Generated code requires manual review for game logic correctness; AI may produce syntactically valid but semantically incorrect physics or gameplay code

No built-in testing or validation — generated scripts are not automatically tested against project

Limited to GDScript 2.0 syntax; older GDScript 1.0 projects may require manual adaptation

What makes it unique

vs alternatives

More contextual than generic LLM code completion because it understands Godot scene structure and can reference existing project classes and patterns in generated code

scene and node tree manipulation via mcp

Medium confidence

Solves for

Best for

Developers automating scene setup and configuration tasks

Teams building procedural level generation or dynamic scene composition

Game designers wanting to script scene modifications without manual editor work

Requires

Godot 4.0+ project

Write access to .tscn scene files

MCP server running with file system access

Limitations

Scene file manipulation is text-based; complex scene changes may require Godot editor validation to ensure consistency

No undo/redo support — changes are direct file writes; requires external version control for safety

Cannot modify scenes that are currently open in Godot editor without reload; potential for conflicts

What makes it unique

vs alternatives

Allows AI assistants to modify game scenes programmatically without opening Godot editor, enabling batch operations and automation that would be tedious in GUI

gdscript debugging and error analysis

Medium confidence

Solves for

Best for

Developers using AI assistants to troubleshoot game runtime issues

Teams wanting automated error analysis and fix suggestions

Solo developers learning Godot who need help understanding error messages

Requires

Godot 4.0+ running in debug mode

Access to Godot debug console output (stdout/stderr)

Project introspection capability for context

Limitations

Requires Godot editor or headless instance to be running; cannot analyze errors from offline builds

Error context is limited to console output; cannot inspect runtime memory state or variable values

Fix suggestions are heuristic-based and may not address root cause; require developer verification

What makes it unique

vs alternatives

More useful than generic error analysis because it understands Godot's error messages, node paths, and signal system; can correlate errors to scene structure and existing code

asset and resource discovery with ai context

Medium confidence

Solves for

Best for

Game developers wanting AI to suggest appropriate assets during code generation

Teams with large asset libraries needing AI-assisted asset discovery

Developers automating asset assignment and material setup

Requires

Godot 4.0+ project structure

Read access to res:// filesystem

Asset files in standard Godot formats (PNG, JPG, OGG, GLTF, etc.)

Limitations

Asset metadata is static; does not track asset usage or dependencies in real-time

Cannot analyze asset content (e.g., image dimensions, audio duration) without parsing file headers; may be slow for large projects

No asset preview generation; AI cannot see visual content, only metadata

What makes it unique

Indexes Godot project assets and exposes them as queryable MCP resources; enables AI to reference actual project assets in code generation rather than generating placeholder paths

vs alternatives

Provides asset-aware code generation because AI can see what textures, models, and audio are available and suggest them in generated scripts, rather than generating generic asset paths

godot documentation and api reference lookup

Medium confidence

Solves for

Best for

AI assistants generating GDScript code that needs to reference correct APIs

Developers learning Godot API and wanting quick reference lookups

Teams enforcing correct API usage in code generation

Requires

Godot documentation data (bundled or downloaded)

MCP server with documentation index

Godot version specification (4.0, 4.1, etc.) for correct API version

Limitations

Documentation is static; does not update automatically when Godot engine is updated

Limited to official Godot API; custom C++ modules and third-party addons not included

No code examples or tutorials; only API signatures and descriptions

What makes it unique

Exposes Godot API reference as queryable MCP resources, enabling AI to verify and look up correct API usage during code generation; uses structured API definitions rather than free-text documentation

vs alternatives

Allows AI code generation to be grounded in actual Godot API definitions, reducing hallucinated or incorrect API calls compared to LLMs generating code from training data alone

multi-file gdscript refactoring with dependency tracking

Medium confidence

Solves for

Best for

Teams maintaining large GDScript codebases needing safe refactoring

Developers using AI to suggest and execute multi-file refactorings

Projects with complex class hierarchies and cross-file dependencies

Requires

Godot 4.0+ project with GDScript 2.0

Write access to all .gd script files

GDScript AST parser (tree-sitter or equivalent)

Limitations

Refactoring is AST-based and may not handle all GDScript edge cases (metaprogramming, dynamic imports)

No built-in undo; requires version control to safely revert failed refactorings

Cannot refactor code that is currently running in Godot editor; requires project reload

What makes it unique

Implements cross-file refactoring with dependency tracking using GDScript AST analysis; automatically updates all references when refactoring, not just the target element

vs alternatives

Safer and more comprehensive than manual refactoring or simple find-replace because it understands GDScript syntax and can distinguish between actual references and string literals or comments

performance profiling and optimization suggestions

Medium confidence

Solves for

Best for

Game developers optimizing performance-critical code

Teams building resource-constrained games (mobile, web)

Developers wanting AI-assisted performance analysis without manual profiling

Requires

Godot 4.0+ project

GDScript code analysis capability

Optional: Godot profiler data for runtime analysis

Limitations

Suggestions are heuristic-based; actual performance impact depends on runtime context and hardware

Cannot profile running game without Godot profiler integration; analysis is static

Optimization suggestions may conflict with code readability or maintainability; require trade-off decisions

What makes it unique

vs alternatives

More targeted than generic code analysis because it understands Godot-specific performance concerns and can suggest engine-appropriate optimizations rather than generic code improvements

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to godot-mcp-server

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

godot-mcp-server

Capabilities8 decomposed

godot project introspection and metadata extraction

gdscript code generation and completion

scene and node tree manipulation via mcp

gdscript debugging and error analysis

asset and resource discovery with ai context

godot documentation and api reference lookup

multi-file gdscript refactoring with dependency tracking

performance profiling and optimization suggestions

Related Artifactssharing capabilities

Godot MCP

MBro

@modelcontextprotocol/server-threejs

Maya MCP

Generative-Media-Skills

Unity3d Game Engine

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to godot-mcp-server

Are you the builder of godot-mcp-server?

Get the weekly brief

Data Sources

godot-mcp-server

Capabilities8 decomposed

godot project introspection and metadata extraction

gdscript code generation and completion

scene and node tree manipulation via mcp

gdscript debugging and error analysis

asset and resource discovery with ai context

godot documentation and api reference lookup

multi-file gdscript refactoring with dependency tracking

performance profiling and optimization suggestions

Related Artifactssharing capabilities

Godot MCP

MBro

@modelcontextprotocol/server-threejs

Maya MCP

Generative-Media-Skills

Unity3d Game Engine

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to godot-mcp-server

Are you the builder of godot-mcp-server?

Get the weekly brief

Data Sources