Thread

Thread is a Minecraft context and tooling mod that enables AI clients to understand and interact with live game information via MCP.

模组 Fabric Forge NeoForge 前置库地图与信息实用自动化

截图

介绍

中文介绍正在准备中，下面暂时显示原文。

Thread

Thread lets MCP-compatible AI clients read useful information from your running Minecraft game. It does not control your character or change the world.

What can it read?

Player health, hunger, XP, position, effects, equipment, and inventory
World time, weather, biome, light, difficulty, and nearby entities
Targeted blocks and entities
Loaded nearby containers and their contents
Live recipes, craftability, missing ingredients, and crafting plans
Advancements and local client settings
Items across your inventory and nearby loaded containers

Thread currently provides 21 read-only minecraft.* tools. Recipes come from Minecraft’s live recipe manager, so changes from datapacks and installed mods are included.

Safe local access

Thread is currently single-player-only and read-only. Its MCP server only listens on your computer by default.

It cannot move your player, run commands, craft items, change inventories, edit blocks, or load distant chunks.

Supported versions

Minecraft 1.21.11, 26.1.2, and 26.2
Fabric, NeoForge, and Forge
Version-specific universal JARs are also available

Install the matching Thread JAR, launch Minecraft, and connect your MCP client to:

http://127.0.0.1:25580/mcp

Future plans

Thread is starting as read-only so MCP clients cannot alter your game.

Future releases may add optional tools that can perform actions. These tools would be permission-controlled, disabled unless explicitly allowed, and designed to keep users in control.

Multiplayer support would likely require Thread to be installed on the server so permissions and available actions can be enforced safely. The exact design is not final, and read-only access will remain the safe default.

Follow the Thread roadmap for planned work.

For mod developers

Thread includes a public Java integration API. Separate mods can register their own read-only tools, recipe providers, and bounded data enrichers without depending on MCP transport code.