- Home
- Skills
- Agents & Orchestration
- MC-Test (Minecraft Mod Tester)
Works with the AI Agents you already use
MC-Test (Minecraft Mod Tester)
Automate Minecraft mod QA by driving a live Fabric or NeoForge client to verify blocks, GUIs, and NBT state.
$5
/moSubscription · cancel anytime
Secure checkout via Stripe
- Always the latest version
- Delivered live to your agent via MCP
- Cancel anytime, access ends at period end
MC-Test (Minecraft Mod Tester)
Example session with this skill installed
Test the new 'grinder:industrial_crusher' block in my Fabric mod. Check if it turns cobblestone into gravel and verify the progress NBT increases over 200 ticks.
- Read your context and instructions
- Compiled the mc-test minecraft mod
I have completed the in-game test for the industrial_crusher. I launched the Fabric client, created a flat test world, and verified the block entity logic.
Test report: industrial_crusher (Fabric, MC 26.3)
| # | Case | Expected | Result | Evidence |
|---|---|---|---|---|
| 1 | Block Placement | Block exists at coordinates | PASS | mc_block confirmed grinder:industrial_crusher at 0, 64, 0 |
| 2 | Recipe Processing | Cobblestone in slot 0 turns to Gravel | PASS | Slot 1 contains 1x minecraft:gravel after 210 ticks |
| 3 | NBT Progression | Progress tag increases during work | PASS | NBT Progress:145 at 150 ticks, Progress:200 at completion |
| 4 | Visual/GUI | GUI opens and shows progress bar | PASS | mc_screenshot shows CrusherScreen with active progress sprite |
Failures
No functional failures detected. Observed a minor WARN in logs regarding a missing translation key for the GUI title (grinder.container.industrial_crusher), which should be added to en_us.json.
Next steps
- Call
mc_close_allto shut down the dev client and save the test world. - Add the missing translation key
grinder.container.industrial_crusherto your lang file. - Run a dedicated server test to verify the progress bar syncs to the client.
Subscription · always the latest version
- Secure checkout via Stripe
- Cancel anytime
- Delivered live via MCP
About this skill
Manual QA for Minecraft mods is slow, prone to human error, and difficult to reproduce. Testing how a block, GUI, or entity actually behaves in-game usually requires manual clicking and observation. This skill automates that process by driving a live Minecraft client through the MCTest MCP server, providing a Playwright-like experience for Java mod development.
What it does
- Automated Game Execution launches Fabric or NeoForge clients directly from your Gradle project and manages the lifecycle.
- In-Game Interaction performs player actions like breaking blocks, clicking GUI slots, using items, and pressing keybinds.
- State Verification reads real-time data including block NBT, inventory contents, entity properties, and tooltips to confirm behavior.
- Visual Auditing captures screenshots of textures, models, and GUI layouts for visual regression checking.
- Log Analysis monitors the dev console for stack traces and mod-specific errors during execution.
How it works
- Validation checks for the
mctest-mcpserver and verifies the project is a supported Gradle-based Fabric or NeoForge environment. - Planning generates a test plan based on your mod's registry IDs and classes, covering both happy paths and edge cases.
- Execution launches the game, creates a test world, and performs sequences of actions followed by state checks.
- Reporting delivers a structured Markdown report with NBT values, log excerpts, and pass/fail statuses for every case.
Frameworks & tools
Works with Minecraft Java Edition (26.x+), Fabric Loom, NeoForge ModDevGradle, and the MCTest MCP server.
Why this beats prompting it yourself
Generic AI agents cannot see or touch the game state; they only guess based on code. This skill uses a specialized bridge to read NBT and click widgets, turning "I think this works" into "here is the evidence from the heap."
Use cases
- Machine Logic Verification to ensure a furnace or grinder processes items and handles full output slots correctly.
- Sync Testing to check if data remains consistent between a dedicated server and a client.
- GUI Automation to test complex menu interactions and button behaviors without manual clicking.
- Bug Reproduction to script a specific sequence of actions that leads to a crash and capture the resulting stack trace.
Known limitations
Supports only Minecraft 26.x and higher. Requires the MCTest MCP server and a local Gradle environment. Does not support physical world interactions outside of the dev runtime.
Requires Minecraft 26.x+ and Fabric or NeoForge. Only works in Gradle-based projects. Requires local installation of mctest-mcp server.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 1 month ago
Requires
Permissions
Allowed Hosts
File Scopes
Shell: only to register the MCTest MCP server during setup (claude mcp add ... npx -y mctest-mcp), after the user approves. Write files: adds MCTest as a dev-only localRuntime dependency in build.gradle and writes the MCP config (.mcp.json / .cursor/mcp.json / .vscode/mcp.json), each shown to and approved by the user first. Mod source is only edited if the user asks for bugs to be fixed. Read files: the mod's source and gradle files, to find real item/block ids and expected behaviour before testing. Network: setup only. Gradle downloads the MCTest mod from maven.coolerpromc.com and npx downloads mctest-mcp from npm. During testing everything stays local: the game is controlled over 127.0.0.1 only. No data is sent anywhere.