Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 13 hours ago
All versions
0.10.0+26.3
Release
mcpfabric 0.10.0+26.313 hours ago 34
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Server-side
Required content
Any compatible version
Changes
Fabric and NeoForge. 0.9.1 was never published; its fix ships here.
Added
- Block states in build results:
get_blocks_regiontakesincludeStateand then returns each block with its properties (minecraft:oak_stairs[facing=east,half=bottom,...]),set_blockreads the block back and returns it asstate, andplace_blockreturns the placed block astarget.serverState. A block facing the wrong way is now visible without aget_blockper block. place_block_at(interact.placeAt, needsenablePlayerControl): place the held block into a cell with the properties asked for (facing, half, axis, hinge...). The mod tries every click within reach against the block's own placement rules, turns the player to one that gives that state and waits until the server has the new rotation; it reports when no click from here can.- Building from a plan in the agent runtime:
build_plansaves a palette-and-layers plan with must-stay-empty cells and spots that must be reachable, and lists materials and warnings (a door opening into a wall, a torch hanging on nothing, a stair without facing);build_verifycompares it with the world, including whether each spot can be walked to and which blocks are in the way; thebuild_structurejob builds or repairs it and verifies the result. perception.blocksreturns each block's full state, collision height and whether it is climbable.
Fixed
npx -y mcpfabric-mcp-serverfrom the README failed with "could not determine executable to run": the package now has amcpfabric-mcp-servercommand next tomcpfabric.open_dashboard: a long job line wraps instead of being cut off.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:eA63YgUh:7CFkrsmI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eA63YgUh:7CFkrsmI"
}

