What It Does

DebugBridge runs a localhost-only WebSocket server (default port 9876, scans 9876–9885) inside Minecraft. External tools — CLI scripts, the bundled Vue web UI, or MCP clients like Claude Code — can inspect and interact with the running game through two complementary APIs:

Native endpoints (fast, high-level)

Purpose-built Java endpoints that return structured JSON in a single round-trip — no Lua overhead:

Endpoint	What it returns
`snapshot`	Player position, health, food, dimension, gamemode, time, weather
`nearbyEntities`	Entities within range: type, position, equipment, distance (with optional for item textures)`includeIcons`
`entityDetails`	Full entity info: equipment slots with damage/custom names, vehicle, passengers, attributes, frame contents
`lookedAtEntity`	The entity the player is aiming at (raycast)
`nearbyBlocks`	Block-entities within range: signs, chests, banners, beacons, furnaces, etc.
`blockDetails`	Block-entity contents: sign lines, chest inventory, skull profile, beacon level
`screenInspect`	Current open screen/gui: type, title, container slots with item stacks (with optional `includeIcons`)
`chatHistory`	Recent client-side chat messages (with optional for styled components)`includeJson`
`screenshot`	Capture the framebuffer as JPEG
`getItemTexture` / `getItemTextureById` / `getEntityItemTexture`	Render item icons as PNG (honors damage, custom model data, dyed leather, player heads)
`setEntityGlow` / `setBlockGlow` / `clearBlockGlow`	Highlight entities or blocks with an in-world outline
`search`	Search loaded classes by name pattern
`status`	Server health and connection info