Setting up Kiro for Godot(MCP server)

#kiro

Why do this?

If you let Kiro read your local Godot docs via an MCP filesystem server, your assistant will:

Use the exact docs for the engine version you downloaded (no hallucinations).
Work offline and fast (no network latency).
Require minimal CPU/RAM on your machine (indexing is small or optional).

This guide covers the MCP server portion — turning your downloaded HTML/MD files into a resource Kiro can query. Later parts of this post will add Kiro agent hooks and steering (placeholders are left for those sections).
Start here to download the docs and get Kiro reading the exact Godot version for your project.
GodotEngine Docs

Scroll down and click Stable (or Latest) to download the documentation — expect a ~300–400 MB zip. Extract it to a folder you control (for example Documents), and rename the top-level folder to GodotDocs so it’s easy to reference.

Example path used throughout this guide:

C:/Users/SNAP/Documents/GodotDocs

Prerequisites

You have the Godot docs downloaded and extracted (see top).
Node.js + npm installed.
The @modelcontextprotocol/server-filesystem package installed globally:

npm install -g @modelcontextprotocol/server-filesystem

Let Kiro spawn the server

Kiro expects MCP servers to be spawnable so it can attach via stdio. Open Kiro, go to the kiro tab and navigate to the mcp server part :

click on the small edit icon to open MCP config and add this making sure you use your own path to the docs:

{
  "mcpServers": {
    "godotDocs": {
      "command": "mcp-server-filesystem",
      "args": [
        "C:/Users/SNAP/Documents/GodotDocs"
      ],
      "env": {},
      "disabled": false,
      "autoApprove": []
    }
  }
}

Notes:

If your docs live under .../GodotDocs/en, update the args value accordingly.
Save the file and re-open the project in Kiro. Kiro should spawn godotDocs automatically and show it under Ghost → MCP servers.