convez.ai
MCP ServerProdutividadeIntermediário
satelliteoflove

Godot MCP Server

satelliteoflove/godot-mcp

Integração nativa entre Claude e Godot para desenvolvimento de jogos sem fricção

Ver no GitHub
BomPluginScore · de 0 a 100

Servidor MCP que conecta Claude diretamente ao editor Godot, eliminando a necessidade de copiar/colar código e mensagens de erro. Claude acessa a árvore de cenas, captura screenshots, lê erros e aplica mudanças diretamente no projeto.

Instalação

$npx convez-ai satelliteoflove/godot-mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
188
Forks
23
Acompanhando
1
Saúde
57%
Último commit
há 3 dias
Versão
godot-mcp-v4.3.0
Issues abertas
0
Contribuidores
6

Casos de uso

  • Desenvolvimento de jogos com assistência IA em tempo real
  • Depuração e correção automática de scripts GDScript
  • Iteração rápida de cenas e nós enquanto Claude visualiza o editor
  • Testes automatizados do jogo com injeção de input via IA
  • Consulta de documentação Godot durante o desenvolvimento

Veredito

Ferramenta madura e bem documentada que resolve um problema real do game dev com IA — elimina o overhead de comunicação entre Claude e Godot. Arquitetura sólida, funciona melhor quando complementada com minimal-godot-mcp para análise estática.

README

A tradução para o português deste README ainda está na fila.

godot-mcp

MCP server that connects Claude to your Godot editor. Less copy-paste, more creating.

Why This Exists

Using AI assistants for game dev means a lot of back-and-forth: copying error messages, describing what's on screen, pasting debug output, manually applying suggested changes. It works, but it's tedious.

This MCP gives Claude direct access to your Godot editor. It can see your scene tree, capture screenshots, read errors, and make changes directly. You stay focused on the creative work while the mechanical relay disappears. Faster iterations, less busywork, more time building the game you actually want to make.

Quick Start

1. Configure your AI assistant

Add godot-mcp to your MCP client. See the Installation Guide for config examples (Claude Desktop, Claude Code, VSCode/Copilot, and more).

While you're at it, add minimal-godot-mcp too — it's a complementary server that covers static GDScript diagnostics and the running game's console output. See Works Well With.

2. Install the Godot addon

npx @satelliteoflove/godot-mcp --install-addon /path/to/your/godot/project

Enable in Godot: Project Settings > Plugins > Godot MCP

3. Go

Open your Godot project, restart your AI assistant, and start building.

What Claude Can Do

  • See your editor, scenes, running game, editor errors, and performance
  • Inspect nodes, resources, animations, tilemaps, 3D spatial data
  • Modify scenes, nodes, scripts, animations, tilemaps directly
  • Test by running the game and injecting input
  • Learn by fetching Godot docs on demand

Works Well With

minimal-godot-mcp by @ryanmazzolini is another MCP server for Godot, and it's worth running alongside this one. This server drives the editor through an addon — scene and node manipulation, running the game, input injection, runtime state, screenshots, and editor-side errors (@tool, import, and addon failures). minimal-godot-mcp needs no addon and provides exactly the functionality this server does not implement: LSP diagnostics for fast static .gd checking, and the running game's console output and stderr over DAP.

Neither duplicates the other, and they don't conflict. Install both and you get static analysis and the live game console alongside full editor and runtime control.

One godot-mcp client at a time, though. A Godot editor bridge serves a single godot-mcp connection. If a second godot-mcp client connects - for example, a subagent that inherited the same MCP config - it is rejected while the first is active rather than displacing it, so the original session keeps working. The second client retries and connects automatically once the first disconnects. A client that crashes without closing its socket is taken over after a short idle timeout, so a dead session never permanently blocks new connections.

Documentation

Architecture

[Claude/AI Assistant/MCP Client] <--stdio--> [MCP Server] <--WebSocket:6550--> [Godot MCP Bridge Addon]

WSL2 is supported (auto-detection, host IP discovery, configurable bind modes). See the Installation Guide for setup details.

CLI smoke test (paste-ready JSON-RPC)

If you run the server manually via CLI (for example: npx -y @satelliteoflove/godot-mcp), you can paste these stdio JSON-RPC frames to verify it responds and can reach Godot:

  1. Write in CLI
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"cli-test","version":"0"}}}
  1. Response
{"result":{"protocolVersion":"2024-11-05","capabilities":{"tools":{},"resources":{},"logging":{}},"serverInfo":{"name":"godot-mcp","version":"2.11.0"}},"jsonrpc":"2.0","id":1}
  1. Call a tool
{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"godot_editor","arguments":{"action":"get_state"}}}
  1. Response
{"result":{"content":[{"type":"text","text":"{\n  \"current_scene\": null,\n  \"godot_version\": \"4.5.1-stable (official)\",\n  \"is_playing\": false,\n  \"main_screen\": \"unknown\",\n  \"open_scenes\": []\n}"}]},"jsonrpc":"2.0","id":2}

Tip: If you enabled Port override in the Godot MCP panel, start the server with matching env vars (or export as environment variable): GODOT_HOST=... GODOT_PORT=... npm run start or GODOT_HOST=... GODOT_PORT=... npx -y @satelliteoflove/godot-mcp

Development

cd server
npm install && npm run build
npm test
npm run generate-docs

Requirements

  • Node.js 20+
  • Godot 4.5+

License

MIT

Ver o original no GitHub

Bom para

Relacionados