Skip to content

MCP · MODEL CONTEXT PROTOCOL

Give your AI assistant a Minecraft mod generator

Add Mine Mod AI to Claude Desktop, Claude Code, Cursor or any MCP client and your assistant gains a tool that builds real, installable Minecraft content — Bedrock add-ons, Java datapacks, playable minigame maps, texture packs, custom items and blocks. Choose a supported edition and feature, then inspect the returned file inventory and installation requirements.

The model never writes the files. It only passes your sentence to deterministic engines that assemble supported files from bounded templates. Generated-file checks catch known structural problems; they do not run your request in Minecraft. Read the validation methodology and test the generated pack on its stated target. Unsupported requests return guidance.

Hosted — one URL, nothing to install

Create an API key on your dashboard, then drop this into your client’s MCP config:

HOSTED MCP CONFIG

{
  "mcpServers": {
    "mine-mod-ai": {
      "url": "https://www.minemodai.com/api/mcp",
      "headers": { "Authorization": "Bearer mma_YOUR_KEY" }
    }
  }
}

API keys are a paid-plan feature — successful builds spend one generation from that plan’s allowance, and throughput scales with it (Pro 30 · Studio 90 · Dragon 300 requests per 5 minutes). Discovery is open: a client can connect and list the tools before you have pasted a key.

Local — keyless with authorized source access

Authorized source holders can run the deterministic generator on their own machine after installing its dependencies. The repository is private; this setup requires repository access. It includes cli/mcp-server.mts. After setup, supported local generation does not need a Mine Mod AI API key:

LOCAL MCP CONFIG

{
  "mcpServers": {
    "mine-mod-ai": {
      "command": "npx",
      "args": ["tsx", "cli/mcp-server.mts"],
      "cwd": "/path/to/mine-mod-ai",
      "env": { "MMA_OUTPUT": "/path/to/save/packs" }
    }
  }
}

Outputs land in MMA_OUTPUT, and the tool result tells your assistant the path and installation guidance. Fabric source projects need compilation.

The tools your assistant gets

generate_minecraft_mod

Builds the pack. Takes a plain-English prompt plus optional edition (java/bedrock), mcVersion and category; returns the pack name, what it does, and the full file list.

list_capabilities

The honest coverage map — what the generator can and cannot build. Needs no API key, so your assistant can check before it promises a user something.

What it can build

Supported rule trigger/action combinations, ability items, custom items and blocks with new Bedrock ids, guns with real projectiles, drivable vehicles, custom creatures, boss fights, spells, x-ray packs, texture and skin packs, particle auras, shopkeepers, pixel-art murals, recipes, advancements, mob and block drop overhauls, world rules, and supported minigame presets. Features and game modes differ by edition; check the returned format and README. Skript server scripts and pinned Fabric .jar source projects require their stated build toolchain.

What it cannot: client rendering mods (shaders, OptiFine-class), new Java item ids without the Fabric path, custom 3D animation rigs beyond the creature engine, or mods for other games. Ask for one of those and the tool says so and offers the nearest real capability — it will not ship you a pack named after something it didn’t build.

Questions

What is MCP?

Model Context Protocol — an open standard for giving an AI assistant real tools. Adding our server means Claude, Cursor or any MCP client can call the Mine Mod AI generator directly, so “build me a bedwars map for my phone” produces an actual installable file instead of a description of one.

Do I need to pay?

The hosted server needs an eligible paid-plan API key; successful builds count toward that plan’s allowance. The local server runs keylessly after setup for people with authorized source access. The repository is private, so local setup is not an unrestricted public download.

Does the AI write the mod files?

The model supplies the prompt; bounded rule-based engines assemble the supported files. Generated-file checks catch known structural problems before delivery. Representative packs have separate server tests, but each request is not run in Minecraft and compatibility or gameplay is not guaranteed for every version, device or mod combination.

What if it can’t build what I asked for?

It says so. An unmappable prompt returns honest phrasing guidance instead of a junk pack named after your request — the tool result comes back flagged as an error with a list of shapes that do work. A wrong mod is worse than a clear no.

How do I get the actual file?

The tool returns the summary and file list; fetching the bytes is one POST to /api/v1/generate with the same Bearer key and format:"zip". The local server skips this — it writes the .mcpack, .mcaddon or .zip straight to the folder you point MMA_OUTPUT at.

Which clients work?

Anything that speaks MCP. The hosted server is stateless Streamable HTTP over POST (protocol versions 2024-11-05, 2025-03-26 and 2025-06-18); the local one is JSON-RPC over stdio. Claude Desktop, Claude Code and Cursor are the ones we use day to day.

Prefer plain HTTP? The same generator is a REST endpoint at POST /api/v1/generate, and there’s a chat studio if you just want to build something now.