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. Ask for “a sword that shoots fireballs” and you get a .mcpack, not a paragraph about one.

The model never writes the files. It only passes your sentence to deterministic engines that assemble every pack from hand-verified templates, and every pack is load-simulated before it comes back. So there is no roll of the dice: the same prompt always builds the same working pack, and a prompt no engine can honour returns guidance instead of junk.

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 — every call spends one generation from that plan’s monthly quota, 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, offline, free forever

The generator has no cloud dependency, so it runs perfectly well on your own machine. Clone the repo (it ships cli/mcp-server.mts, hand-rolled and dependency-free) and point your client at it — no key, no account, no network:

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" }
    }
  }
}

Finished packs land in MMA_OUTPUT ready to install, and the tool result tells your assistant the exact path.

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

Rule mods (any “when X, do Y” chain), 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 playable minigames on both editions — bedwars, skywars, hide & seek, among us, spleef, parkour, dropper, FFA and composed modes like KOTH, CTF and TNT run. Also Skript server plugins and compile-ready Fabric .jar source projects.

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 local server is free, keyless and offline forever — clone the repo and it works. The hosted server needs a Mine Mod AI API key, and keys are part of the paid plans, because each call spends a generation from that plan’s monthly quota.

Does the AI write the mod files?

No, and this is the whole point. The model only supplies the prompt; deterministic rule-based engines assemble every file, and every pack is load-simulated before it is returned. The same prompt always builds the same valid pack — there is no roll of the dice where you get a mod that won’t load.

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.