mcdxai/minecraft-dev-mcp · Archived

minecraft-dev

Use this skill whenever the user wants to look up Minecraft source, mod source, mod loader source, mappings, registries, versions, version differences, access transformers, mixin information, documentation, or code search results with minecraft-dev-cli.

First seen Jul 25, 2026

Installation

$ npx skills add mcdxai/minecraft-dev-mcp --skill minecraft-dev

Summary

  • Use this skill whenever the user wants to look up Minecraft source, mod source, mod loader source, mappings, registries, versions, version differences, access transformers, mixin information, documentation, or code search results with minecraft-dev-cli.
  • Also use it for Fabric, Forge, Quilt, and NeoForge source lookups.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from mcdxai/minecraft-dev-mcp.

npx skills add mcdxai/minecraft-dev-mcp

Browse all from mcdxai/minecraft-dev-mcp

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 35
License LICENSE
Default branch main
Open issues 1
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,134 B
  • docs SUMMARY.md 341 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Minecraft Dev CLI Lookup

Use minecraft-dev-cli to inspect Minecraft code, mod and loader JARs, mappings, registries, versions, and docs.

Version format note

Use the actual Minecraft version the user is working with. Modern releases use the newer 26.1.x naming style, for example 26.1.2.

  • 1.14 through 1.21.11 support both yarn and mojmap.
  • 26.1+ uses mojmap only.
  • Yarn mappings stop at 1.21.11.

Workflow

  1. Identify whether the user needs Minecraft source, mod source, mod loader metadata, mappings, registries, docs, validation, or version diffing.
  2. Pick the narrowest tool that answers the request.
  3. Run minecraft-dev-cli <tool> --key value or minecraft-dev-cli <tool> --key=value.
  4. Parse the JSON response and return only the useful result.
  5. If the request is vague, ask for the class name, file path, symbol, JAR path, or Minecraft version.

Tool List

Core Minecraft source

  • getminecraftsource — get decompiled source for one Minecraft class.
  • decompileminecraftversion — decompile an entire Minecraft version into cache.
  • listminecraftversions — list available and cached Minecraft versions.
  • getregistrydata — extract block, item, entity, and other registry data.
  • searchminecraftcode — regex search through decompiled Minecraft source.
  • indexminecraftversion — build a fast full-text index for Minecraft source.
  • search_indexed — run fast indexed searches against Minecraft source.

Mappings and comparison

  • find_mapping — translate class, method, and field names between mapping systems.
  • remapmodjar — remap a Fabric mod JAR to readable names.
  • compare_versions — compare two Minecraft versions at a high level.
  • compareversionsdetailed — compare versions with AST-level API detail.

Validation and documentation

  • analyze_mixin — validate Mixin targets and injections against Minecraft source.
  • validateaccesswidener — validate access widener targets against Minecraft source.
  • validateaccesstransformer — validate a Forge/NeoForge access transformer (.cfg) against Minecraft source (mojmap-only); flags bad targets/signatures, record canonical-constructor crashes, inner-class accessibility, and conflicting modifiers.
  • get_documentation — fetch documentation hints for a Minecraft class or concept.
  • search_documentation — search known Minecraft and Fabric docs.

Mod source and mod loader source

  • analyzemodjar — inspect a mod or loader JAR for metadata, dependencies, entrypoints, mixins, and loader info.
  • decompilemodjar — decompile a mod or loader JAR into readable Java source.
  • searchmodcode — regex search through decompiled mod or loader source.
  • index_mod — build a fast full-text index for decompiled mod or loader source.
  • searchmodindexed — run fast indexed searches against mod or loader source.

Use minecraft-dev-cli list-tools or minecraft-dev-cli help when you need quick CLI usage.

Read references/tools.md only when you need parameter details or example commands.

Command Pattern

minecraft-dev-cli <tool> --key value --key2 value2

All commands return JSON with:

  • success
  • tool
  • result or error

Examples

List versions

minecraft-dev-cli list_minecraft_versions

List tool schemas

minecraft-dev-cli list-tools

Get Minecraft source

minecraft-dev-cli get_minecraft_source --version 26.1.2 --className net.minecraft.world.entity.Entity --mapping mojmap

Get mod or loader metadata

minecraft-dev-cli analyze_mod_jar --jarPath C:\mods\neoforge-26.1.2-universal.jar

Decompile mod or loader source

minecraft-dev-cli decompile_mod_jar --jarPath C:\mods\neoforge-26.1.2-universal.jar --mapping mojmap

Search mod or loader source

minecraft-dev-cli search_mod_code --modId neoforge --modVersion 26.1.2 --query DeferredRegister --searchType class --mapping mojmap

Find a mapping

minecraft-dev-cli find_mapping --symbol a --version 1.21.1 --sourceMapping official --targetMapping mojmap

Notes

  • Use analyzemodjar first when the user asks about a loader JAR, NeoForge internals, dependencies, entrypoints, or mixins.
  • Use decompilemodjar before searchmodcode or index_mod.
  • Use indexed search for broad or repeated searches.
  • decompileminecraftversion also supports --jarPath for local Forge/NeoForge patched Minecraft JARs. In that mode, use --mapping mojmap and a version cache key like 1.21.1-neoforge-21.1.72.
  • Registry examples should use singular names like block, item, and entity.
  • If a user asks about CLI usage, always show flags-only examples.