Godot MCP

Created By
bradyppa year ago
A Model Context Protocol (MCP) server for interacting with the Godot game engine.
Overview

What is Godot MCP?

Godot MCP is a Model Context Protocol (MCP) server designed to facilitate interaction between AI assistants and the Godot game engine, enabling seamless integration and management of game projects.

How to use Godot MCP?

To use Godot MCP, clone the repository from GitHub, install the necessary dependencies using npm, and configure your AI assistant to connect to the MCP server. You can then issue commands to manage Godot projects and scenes.

Key features of Godot MCP?

  • Direct integration with the Godot engine for project management.
  • Real-time feedback and error reporting from Godot.
  • Cross-platform compatibility (Windows, macOS, Linux).
  • Secure operations with an optional read-only mode.
  • Automatic detection of Godot installations.

Use cases of Godot MCP?

  1. Automating scene creation and management in Godot projects.
  2. Debugging and analyzing project behavior through AI commands.
  3. Integrating AI assistants for enhanced game development workflows.

FAQ from Godot MCP?

  • What versions of Godot are supported?

    Godot 3.5+ and all 4.x versions are supported.

  • Is it safe to use on production projects?

    Yes, especially with read-only mode enabled, which prevents modifications.

  • Can I run multiple instances of the server?

    Yes, each instance operates independently, allowing for simultaneous project management.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bradypp
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago